Swift.

When adjusting QNH below the preset altimeter setting, there is a behaviour where the setting will jump 2 places making it impossible to select the desired QNH setting. The location of this jump appears inconsistently 'below' the original pressure setting. 2984.trk 2992.trk

When at Nellis AFB the Grid Square IDs for the areas south of Nellis are missing from the ODU. All 9 of these are within the 11S Grid Zone Designator NB PB QB NA PA QA NV PV QV HarrierGridEntryBug.trk

Currently in DCS Harrier, entering data into a waypoint, or for the AC initial position, requires the POS ODU button to be pressed between entry of Northings and Entry of Eastings, ie: EHSD DATA POS N12 34 56 ENTER POS E012 34 56 ENTER Where the expected behaviour as described in NATOPS is: EHSD DATA POS N12 34 56 ENTER E012 34 56 ENTER HarrierWPdata.trk

To my knowledge, they are threat rings for AAA units.

Looks like we have SUU-25 with LUU-2 already, but things like LUU-19 and mounting them on ITER will rely on ED to add those I guess. Fortunately, for ED, Hornet should also be able to carry these. So all the more reason for them to add it.

I believe it should be capable of carrying LUU-2 and LUU-19 flares. Both in SUU-25 dispensers or directly mounted onto the pylon or ITER. I don't think we have this in DCS though.

Its not a launcher used on hornet IRL

How fascinating, I imagine it's something to do with all their runways being short enough to warrant needing that extra deceleration.

So, fun fact. Speedbrakes in hornet affect yaw stability. So its advised to not use them on landing unless its 100% needed. And dont confuse aerobraking with flaring. Hornet can flare before landing too, between 34000lbs and 39000lbs landing weight. Aerobraking however is not allowed in hornet because of risk of striking the stabs on the ground.

It might help to start out with, but Ball-Lineup-AOA is the scan you need to be doing. Don't factor VV placement into that other than maybe at the very very start as you describe.

Not very helpful I know, but Ball-Lineup-AOA If you see one of them drifting, fix it. In this case Lineup, if you are drifting to the left, you know how to move the jet to the right so just do it. And keep doing it until you are lined up again. Repeat until touchdown

Energy Manoeuvrability

There is a limit though, I think if you try and enter a waypoint beyond 250NM from initial position it doesnt take the elevation automatically.

I thought it answered the OP pretty well. Why is Link 16 updating so slowly? Because the "Link 16" we have is vastly simplified. Obviously IRL it depends

Nothing more to add, Link 16 in DCS is heavily simplified, theres no argument there.

Is your external lights master switch set to ON?

This is probably the most common system failure in DCS right now. Its similar conditions to MC 1 failure, but it lacks a lot of the degraded operation modes that such a failure should have. Basically, its a random failure, but its WIP

NWS low gain is on all the time, other than when the parking brake is activated.

Where are you getting that gouge from? Thats not the IRL way

Needless to say its a PITA to pin it down, hence why I haven't actually reported it yet.

As the first thing done. Like I said, it's fine in single player

I normally use a winwing taurus, but to isolate the axis from the press I just used my keyboard. If you look at the video I posted above you will see what I am seeing. The GZID is being selected but promptly deselected. What's most interesting is that a few minutes of spamming like shown in the video will eventually make it stick, and then after that it works fine for all the other waypoints.

I'd just like to isolate that there is a separate issue going around, MGRS wont accept the GZID even when you have a deadzone of something crazy like 20 and use a separate button for the TDC depress. Its not a controller issue, there is just a bug with the MGRS entry.

Oh yes! You finally managed to reproduce this? I've been having this bug for ages without being able to report it I also thought it was a TDC slew deadzone issue, but it presented when just pressing enter on the keyboard and also with a huge deadzone to the TDC axis

Not sure about that one, the real manual is very specific eg: 'Depress/Release then forward (within 1 second)'