LorenLuke

Unlikely, though this was said back before the patch was moved to April 10th. (Timestamped video.)

Currently, there's no synchronization for multicrew, though depending on updates and what's included, that may change. Given that there's no synchronization at this time in game, only targets you have personally scanned will show up. However, if you're the only human player in the aircraft, scanning vehicles from the back seat, and then moving to the front seat will still have them present on your FCR and TSD until you start another scan.

Piggybacking off of this, though you can't have the radar scanning while you use the TADS, you can still bring up the FCR page with the icons for the detected vehicles still shown. In this page, you can use the cursor to select a particular target (or place it over the NTS text) while the TADS is slaved to the FCR acquisition source in order to look at targets on the FCR. Note that this data will degrade and become inaccurate over time (especially for moving targets) and you'll need to switch to the FCR and rescan in order to refresh target locations (which I believe will require you to reset your acquisition source back to FCR when you switch back to TADS).

IIRC, it'll try and move to face forward any time it's not active, but it'll still maintain its initial scan heading during a scanburst, or during a continuous scan.

SRS only seems to be able to detect the position of the cockpit you started in. So while it may follow adequate rocker position from the pilot seat, I believe the only way to detect the positions in the CP/G seat is to be slotted into it (rather than start as pilot and then swapping seats).

FCR range only goes out to 8km for moving targets. Stationary targets show up only within 6km.

Closer to eight. (video with timestamp) https://youtu.be/tG-aV0Nx1UQ?t=1695

I had a friend run into something similar, and though my solution didn't work in his case, his solution was to hop in the gunner seat, go to the Weapons -> Util page, and turn the TADS off and then back on, and that fixed his issue. Again, if this helps, great; if not, hope a solution is forthcoming.

I know I've run into this one before (though this may not be the cause in your case)- If you use the night vision system (not the goggles, but the Apache FLIR) as the pilot, and you have the night vision source as 'TADS' (selected on the Mission Grip/'lower' part of the Collective handle), George will report 'No TEDAC Available' when trying to search for targets. If this is unrelated to your problem, I hope you find a solution, else hope this helps.

To be fair, rarely is a module dropped as feature-complete and full price with no early access period, too.

They mentioned that it would cost 69.99 USD.

Are these people in the room with us right now?

Three ways- 1) The CPG can do it, as the aircraft can use the laser in the TADS to cue the radar Hellfires, so you can toggle between the two types. 2) If another AH-64 with an FCR data-links you a target, using the RFHO function, receiving the data will enable the FCR as a selectable sight even without an FCR (don't know if the real life platform still enables the FCR sight select without it, but in DCS, you can sight select FCR without a radar only after receiving an RFHO). From there, the Hellfire can be launched towards the target within parameters, much like a LOAL shot vs an acquisition source point. 3) Don't take radar Hellfires without a radar, and the you won't have to worry about stepping through them. I've found it only lets you after receiving an RFHO.

Your sight is in HMD. This only allows selection of SAL/AGM-114Kilo laser-guided Hellfires, which your helicopter has exactly zero of. You need your sight to be in FCR (or possibly LINK, which isn't modeled yet, so I don't know if that's true for switchology or not,) in order to select the RF/AGM-114Lima radar-guided Hellfires.

To be fair, their employee availability was cut in half when the nation with those employees was invaded by another a month after that announcement.

While not a bad assumption to make, 'most likely' is doing far too much heavy lifting in this sentence for it to be something up to ED's standards.

You'd have to had included the shirt with your order. It was just an add-on option that you could get.

For the rearming panel, are there plans to allow it to include weapon customization beyond just fuze and laser code functions? Particularly rocket zone loadouts for the AH-64 and hellfire rails (to carry a symmetrical load of say, 6 Illum, 8 smoke, & 24 HE rockets, with 4 Kilo and 2 limas)?

The other thing to consider is whose hands final release is in. HB might have a release candidate that they could push out the door (and have it be a version that is worthy of first release), and ED still would have to pick it up and test and verify everything before final final release. So even if they complete it within their Winter 23/24 window, have it shipped to ED and in the same state as what the consumer ultimately grabs, I can already hear the cavalcade of comments saying THEY LIED!!! about releasing in winter, even if it were to drop on something like the 26th of March. They gave us a timeline, let's give them some faith (and some reasonable assumptions of wiggle room on that, too).

I think making a concession for people who either don't have the VR to move hands or don't like playing while using a pilot model for whatever reason, shouldn't be excluded on that front. Plus if I'm using my hand to move the mouse around and shield an MFD, one of my hands is off the controls to use it. The realism of it denies that even the Wags says it's a 'game', and if the realism/sim argument has to be called in, I'll contend that it's clearly unrealistic that my hands are pinned to my HOTAS, that I can have sunlight come through the literal back of my Ka-50 with zero windows to glare up my shkval, and that me having my face in front of the glass of an MFD doesn't seem to block the light with the back of my head, despite me having my nose pressed against it like I'm a kindergartener watching their mac & cheese cook in the microwave. Any of these in a truly 'realistic' scenario wouldn't occur, but here we are.

H/T to @jaylw314 from this comment- I think this would be a fantastic addition to the game, since we can't use a hand to shield the screens from sun glare and flying a different direction might not be an option for CPGs/RIOs/WSOs; just having the ability for sun glare be 'blacked out' in a small radius around the cursor would be great.

This suggestion as a UNIVERSAL thing for all modules would be absolutely wonderful. A+ suggestion.

Check your axis controls and make sure pitch, roll, rudder, etc. doesn't have more than one device giving it inputs.

One of these things is not like the other~

The primary issue of using this track is (though while I've not given it a real crack) that had only seemed to have run into it on a multiplayer environment, and thus was able to reproduce the effect here, readily. I'll see if I can't get it to happen in singleplayer over the next few days, but also if the newest patch releases as advertised (at time of writing), it may no longer be an issue. If I can get it to reproduce over the next few days (either in SP or MP), I'll update the post with a track when it does happen to... happen.