Tholozor

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/

To my knowledge, HGU-68/P helmets in USN service did have the elephant ears, but not the visor rest protrusions on top (these are more in-line with HGU-55/P helmets). The helmet had a fixed track for the visor, however many helmets ended up unofficially modified to retain the NVG clips while swapping to the single-bungee visor strap. Additional information and examples on helmets used in U.S. Navy service can be found here: https://www.salimbeti.com/aviation/helmets4.htm Here's some examples of the modified -68/P: Actual -68/P helmets would look more like this:

Already reported:

Autopilot modes are disengaged with the paddle switch.

Are you using the default cockpit livery or a custom one?

The F-16's AN/APN-232 Combined Altitude Radar Altimeter (CARA) is rated for 50,000 ft, it's correct as-is.

The FCR cannot determine the difference between something that is alive versus something that is dead, as in either state it would look like roughly like the same thing. Using the ATK Phase on the TSD, you can see your SHOT marks for Hellfires to determine which targets have already been engaged. However, it will be up to you to determine if the target was actually destroyed.

PP has always been there. What isn't there, is the ability to make PP missions loadable from the data card, they can currently only be made in the cockpit.

G-overshoot is entirely possible. The FCS may not be able to keep pace with rapid pilot inputs.

Pre-Planned mode was one of the first modes the JDAM came with, it's been in for years. AUTO/LOFT modes are what aren't implemented yet.

For context, this is only correct for OFP 19C, but appears this was reported before:

Ensure you have 'Game Flight Mode' mode turned off in the DCS Gameplay Settings.

Do you have any examples that aren't of Super Hornets though?

Current 2.9.3 build, default cockpit livery as-seen in the ModelViewer. Both left and right side consoles appear to have a glossy, almost wet appearance with a noticeable partition towards the outboard walls when viewed in shadow.

Per title, 'TRIM' no longer appears on the ADV line while the T/O TRIM button is held and the stabs reach 12° NU. TRIM_ADV_not_present.trk

Partially fixed after today's update. The bearing and range is shifted over, but the AACQ legend still overlaps with the symbol denoting the Bullseye is out of the scope of the tactical region.

For some additional context, the following example (VFA-136, 2004 on CVN-72) shows the console backlighting is definitely green when the cockpit lighting is not in the DAY position (evidenced by the IFEI lighting being green). I am unaware whether or not the console backlighting is capable of more than one color, or simply has on/off states.

In addition, the same is also true for HARMs.

TACAN will show DME information for VOR/DME (or DME-only) stations on their paired frequency. Most notably, the VOR/DME station at Beirut (KAD) on the Syria map is paired to 73X. A track will help see if the behavior you're describing is intentional.

A track would be helpful here. TWS has restrictions in place depending on the bar scan and azimuth setting. - 6B: Only 20­° azimuth is available. - 4B: 20° or 40° in azimuth are available. - 2B: 20°, 40°, 60° or 80° in azimuth are available.

@SickSidewinder9 Full explanation here:

TMS Down will only perform CZ if the TGP is SOI and is in SLAVE mode.

Looking at the track and testing it myself I've boiled it down to a simple description: - A/A weapon SET parameters cannot be invoked in RWS if L&S is present. STT/RSET logic doesn't matter either, a track can be designated L&S in RWS and it will prevent SET parameters from being invoked with WSS. If the trackfile ages out (e.g. removing the L&S), WSS parameter invoking returns. I can't find relevant information in the manual that definitively explains the logic to support one way or the other, so if it's a bug or correct is outside my knowledge unless an SME chimes in with more info.