Tholozor

Enabling the AUTO INT option from the AZ/EL page will command the CIT to automatically interrogate the L&S or the entire scan volume every 10 seconds. Manual IFF interrogation on any trackfile can be performed by depressing the sensor control switch and bumping it towards the ATTK format.

Data Cartridge functionality is being worked on as a global function.

Not implemented.

Not fully implemented for multicrew yet:

This is generally normal in nose-to-tail trim (winds depending as well). Since the anti-torque rotor (pedal position) is so far to the side, it wants to induce a roll due to its high-mounted position on the tail. This requires cyclic movement to counter and maintain the nose with the velocity vector.

Depressing the SCS and then bumping it towards the ATTK format should still command manual IFF interrogation.

That's what it says in the Legacy manual: - 5 nm should show the 250k:1 map - 10 nm should show the 500k:1 map - 20 or 40 nm should show the 2M:1 map - 80 and 160, no map.

That's a problem with the map, where it's missing the map graphics for that scale.

This is not a bug; no map should be displayed at 80 or 160.

Can you be more specific?

There's a few open reports regarding problems that sound related to this, but without a track it's hard to tell if your scenario matches these same conditions:

Are you selecting the gun from the CPG's cyclic stick or the TEDAC?

The TGT diamond should move with tgr FLIR when FLIR becomes the driving source of the designation.

This version of the F-16 uses the ALR-56.

Alternatively, you can hold Shift, and scroll the mouse wheel to accelerate the movement of the knob.

This is normal. When in CCIP or STRF modes, the TGP points at the predicted impact point.

This isn't exactly true. While normal, WYPT-based coupled steering cannot be performed while a TGT designation exists (which is not exclusive to the use of a targeting pod), the Hornet's autopilot is capable of coupled steering to a TGT designation if the selected weapon provides an azimuth steering line (CPL ASL). Primarily, free-fall munitions such as the Mark 80 series general purpose bombs, Rockeye-series cluster bombs, and Paveway-series LGBs can all utilize CPL ASL.

CZ should also be on the HSD:

Already reported:

Putting that switch to the NITE position will switch the IFEI lighting to green and enable dimmer control (this is the only difference from the DAY position). NVG position does the same thing but also alters the entire cockpit lighting to green floods for the console lights.

Are you talking about R/BL or BOL? Those are two completely different modes.

Make sure your custom cockpit livery has this line of code: {"Pilot_F18_FP_Map", 0, "mfd3", true};

Did you add the bombs into the PACS? Non-smart weapons will not self-identify to the aircraft, you need to add them manually.

The problem is that you never changed the Grid Zone Designator (GZD), it's still 30N, which is the corresponding GZD for N0° E0°. The 30N GZD has no Grid Square ID for 'WV,' so it throws an error. The GZD you're looking for (assuming this is the Sinai map) is 36R. JTACs in DCS currently don't provide the GZD in their callouts.

Except it's been explicitly stated that the non-JHMCS helmet is supposed to be a U.S. Navy HGU-68/P, which did not have the protrusions. But yes, the elephant ears are definitely missing. https://www.digitalcombatsimulator.com/en/news/2023-09-08/