LorenLuke

This is what it shows for me at the download link (https://www.digitalcombatsimulator.com/upload/iblock/99d/eo2rpbefcggjpaxtalj3v9s8ln46ois7/DCS AH-64D Early Access Guide EN.pdf), and it seems the information is somewhat outdated. If there's a new version available, I'm not sure where to find it.

Just so you know, this is NOT what's happening. It doesn't indicate that an object was found by the FCR, nor that any particular object it does detect is destroyed. The 'X' indicators merely show 'a hellfire from this helicopter was shot at this location', whether that be a Kilo Hellfire LOBL shot with a laser or a Radar hellfire shot at a target found by the FCR.

Title FCR Show Track.trk

The indicated targets (C97, C98, and SA8 points) appear to be on the farther reaches of the FCR arc, judging from the TSD. Non-moving targets will not be detected at ranges greater than six kilometers. The total range of the FCR in GTM is eight kilometers, therefore it will pick up only moving targets in the final quarter of its total scan distance. Additionally, it may also have trouble distinguishing targets with some ground clutter at these maximum theoretical ranges. If the enemies are located at the target points as shown in the TSD, you are likely too far and should move closer until they're in range. EDIT: Your FCR also does not appear to be emitting, from your screenshot.

If you WAS the Lima Hellfires, and you have no targets on the FCR, you will get the 'LOS invalid' error. Ensure you have targets on the FCR to avoid this message when using the FCR as a sight with the radar Hellfire.

How does one switch between these modes? And how does one uncage the seeker?

Yes. All LOAL means is 'not LOBL', where it's lofted in the direction of the target and then sent looking as it flies out. For a radar hellfire to be LOBL, the target must be either moving or within 2.5km of the launch platform. At this point, the radar in the missile nose will attempt to acquire the target via its own radar emitter. It'll continue to track the target (giving an 'RF TRACK' message and a big box, showing it as being a LOBL launch). If it cannot track, you'll have a 'No Acquire' message and need to re-WAS the missile to give it new data. TL;DR: Yes; small box for LOAL, big box for LOBL (targets less than 2.5km or are moving). EDIT: And you don't necessarily need the FCR to use these for either mode.

What appears to be happening (correct to real life or not, IDK), is that the symbology is tied to how the symbology would display on the HMD, e.g. if you slave the TADS to FXD forward, and look forward, you should be able to make the acquisition source cross appear, and if not, the aiming dots appear on the crosshair arms of the TADS display to direct where to point your head to look at the acquisition source. Again, I don't know if this behavior is a bug, or true to real life, but that seems to be how it's currently implemented.

A guess: 'While in the front seat with George flying, the aircraft oscillates left and right when hovering, but is fine in forward flight.'

I mean, I wouldn't be so quick to suggest it's potentially fake. To me, it looks similar, gameplay-wise, to the door gunners you see in some of the other helos, just with a moving pivot point (left hand) compared to something like the KORD in the Hind.

While true, I think they're trying to point out that you're basically saying 'Gosh, I hope they'll implement it exactly like the way they demonstrated in the video.' While we can certainly take nothing for granted here, I imagine that them implementing it with VR hand controllers (given that they showed it being used by what appear to be VR hand controllers) is a pretty safe bet.

Ask ye to the void, and it shall answer.

See if either of these tracks work for you. FCR 1.trk FCR 2.trk

Have you tried using a modifier key for that? I use a hat switch for tads zoom, and just use modifier + hat switch for FCR zoom.

My understanding is that the control measures that point out targets and allies are loaded at the start of the mission and do not move automatically. Therefore, they'll either be right where they should be to compare with actual unit positions if the units never move, or just should not be used to determine friendly/enemy status. (Plus, the scope in the DTV mode at max zoom is decent enough for looking at targets under 8km away with a clear LOS)

I mean, if the sensors can see the UV/IR heat bloom from a missile/rocket motor when it launches, and if the CMWS it thinks it's a missile launch, it'll give a missile launch warning. That's basically all there is to it.

Only Tail# 010 has bombs set to 1686. F16 LGB.trk

Both shaky bars and completely closed bars indicate a target lock. Shaky bars is the lock you'll get 99 percent of the time on some unit and is a typical point lock on a target like a tank. The solid bars are a 'Forced Correlate' lock, which uses the whole picture/scene to generate a lock, rather than the tiny bit of contrast at the center of the crosshairs, (e.g. a vehicle or bunker), allowing it to lock onto locations it otherwise would not be able to lock onto. That said, because it locks onto a larger picture, it won't be able to track any sort of moving targets in the scene, and it's a feature only available to non-IR mavericks.

Trajectory is unaffected if launched in LOBL (designated/target detected before the missile comes off the rail) mode. Only LOAL launches are affected.

Unless it's something they've added in that's not on the real jet, it should be there. But it's half action and TDC depress together. https://youtu.be/KOKPMYwcIYE?t=85

One of the issues is that Steam DLC needs an exact release date to be purchasable. So once they confirm a release date, it should be available to buy on steam.

No. The Datalink pod in question is more like the AN/AWW-13 on the Hornet. This pod enables it to communicate, control, and receive video from certain weapons while those weapons are in flight. https://youtu.be/--nFNQQU1y4?t=173

Has this been fixed?

Will the back seat have an option for toggling the feed bag/glare cover?