Tholozor

Yaw instability in the rotor model has been reported and is being worked on, is this thread similar to what you're experiencing?

AFAIK this is basically correct, as the FMU-152 has different arming times based on high or low drag configurations. (Of course these are based on the backup settings on the faceplate).

Like this?

These are referred to as Geographic Lines, and utilized on steerpoints 31 through 55, divided into 4 groups of 6 points (visibility controlled via the LINE1 through LINE4 options on the HSD's CNTL page). These are already planned for later:

You'd have to spend the time to transfer the fuel from the external tanks to the internal ones. It also affects the CG to some degree.

What would the general procedure be then for any CAS platform responding to TIC if the codes don't match? I know PEQ-1s have PRF code wheels, and JP 3-09.1 specifically mentions that the aircrew passes their codes to the FAC.

Realistically speaking, the entire JTAC system is a bit antiquated by this point, as normally the ground unit providing the lase would be able to set their designator to the code provided by the pilot, not the other way around. There's ways in the scripting environment to change JTAC laser codes via commands, but none that currently exist natively to the normal radio command menu. I personally don't know the commands myself, only that it's possible (and again, would require scripting). For the time being I think you're right to presume that your client slots should expect to utilize the same code, or have multiple JTACs available to split the load (assuming they don't end up cross-targeting the same unit at the same time and wasting ordnance).

More info on this subject here:

You can use it to adjust the TGP zoom level (independent of the FOV setting).

If the HARM is going after EWRs, that's a bug.

There is none. The FPS-117 operates at too low a frequency to be detected by the HTS or engaged with the HARM. The full ALIC table can be found in the Early Access Guide, Appendix B, starting on page 568.

Seems to be a correction of this specific issue: Personally I prefer it the way it is now, as I can turn the HMD brightness knob down to reduce the glow, whereas previously it wasn't bright enough.

Is making an accurate LANTIRN no longer the case after the addition of Sniper?

This has also been reported here:

Is there wind?