ShuRugal

If there is still ongoing litigation, they probably legally cannot discuss the subject.

I'm just guessing here, but my guess would be that the systems which handle ACQ data and generate the ACQ symbology do not talk to the system which monitors whether the missile is in launch parameters, and therefore selecting the seeker as ACQ before the missile locks the laser would result in the ACQ cross running all over the display as the missile scans for a laser?

man, i clicked on this thinking it was going to be focused on contrast visibility options for the color-blind. But what's shown here with other sims converting visual cues to audio cues is wild. i never would have even imagined this.

another possible fix i think would work well and be realistic to crew procedures would be that if George is set to "free fire" and you bug a target he identified as friendly, he should switch back to weapons tight and say something like "please confirm, that target looks friendly".

an issue i keep running into with George is he will ignore a mission target to lock onto a SAM battery 20 miles behind the target. I'm really looking forward to the "search in PFZ" function just announced to help solve this.

does the "invisible" flag on a unit not hide it from George? haven't tested, but i would expect it to.

it's also worth keeping in mind that the Longbow radar does not display raw radar returns, but attempts to identify and classify targets against an internal database. If the return doesn't match anything in the database, it will not be displayed to the crew. While something like a shahed drone SHOULD come back classified as a fixed-wing aircraft, something that small is pushing the boundary of what the designers anticipated the system being used for.

1. are your radios turned on? 2. is the mic switch set to one of the radios? 3. are you pushing the keybind for the microphone?

the yellow light indicates that you are in EFFECTIVE range, not MAXIMUM range. effective range is determined by the spread of the weapon vs the programmed target size. as you can see from the salvo you fired here, even with the light on, you still have a spread large enough for a tank to fit comfortably between even the closest rockets in a salvo. yes, 900 meters is a reasonable max effective range for unguided rockets fired from a helicopter. If you want a longer effective range, use ATGMs, that's why they were invented: because rockets kinda suck.

using aircraft rockets for indirect fire is really only useful for attacking a pre-planned target like a factory or an entire airport. As you have discovered, managing any semblance of accuracy with indirect fire requires flying extremely precise delivery profiles. IRL, planning an indirect fire profile for a helicopter would look something like: identify target position on map identify desired approach direction identify minimum acceptable range to close with target area compute required airspeed, release angle, altitude, and heading for firing. get weather data and correct release parameters for projected atmospheric conditions (air density, wind) adjust for coriolis effects identify two visiual landmarks along the required firing line brief pilots on visual landmarks, required airspeed, release angle, release altitude, and "do not cross" line/altitude basically, everything you have to do for a regular rocket artillery strike, plus accounting for the fact that the launcher is flying.

you did not select FCR as your sight, as indicated by "P-HMD" in the lower left of the IHADSS.

you might try clicking on the power lever without moving it? in some DCS modules, that toggles between off an idle position, but i don't know if it works in the AH64

check your axis bindings. throttle axis probably got bound to something you didn't expect. this is nearly always the culprit with analog axii jumping around.

alongside this, it would be REALLY nice if we could get a callsign plate in the cockpit of every module which refelcts the unit name entered in mission editor.

I know this doesn't achieve the solution you are looking for, but have you tried using the IHADDs on your right eye? You may actually find that having the display on your non-dominant eye improves your "stick and pedals" flying, as it makes paying attention to the display a much more deliberate action, and getting over-focused on the display is something that gives a lot of people trouble (unconsciously trying to fly the HUD instead of the aircraft). I overcome this problem myself by keeping the "hide HMD" binding on my HOTAS so i can kick it out of my vision when i'm not doing something that NEEDS it. If you've already tried this, then feel free to tell me to eff off.