Machalot

Not because it looks true. It's very well established in the field of aerodynamics that bluff bodies with aft flow separation have higher drag than streamlined bodies. You can find this in many textbooks and published papers. While I agree we don't have quantitative data specific to the P-51 canopy, but I'm surprised you would call this an unproven theory.

What leads you to conclude they changed in the jet? Did the LOLA values change? Or are they the same LOLA but they have apparently moved to a different place on the Earth?

New, highly advanced, smokeless, flameless propellant.

The kneeboard will change instantly. The jet's data will change when you load 9099. No need to actually replace the cartridge though, it magically aquires the new data.

My car tells me to close my windows to reduce drag if I go fast with them open. I presume there's some data behind that.

The comment I replied to said VIP/VRP are not relevant or not trained anymore in the era of GPS aided navigation. There was a pre-GPS era and there may well be a post-GPS era too.

My point was about pilot training in peacetime for GPS-denied operations, in preparation for a hypothetical war between the US and a near peer. I have no specific knowledge about what's going on with GPS in Ukraine, but would you be surprised if Russia is jamming it?

All these Viper pilots discovering their inner Viggen driver!

Does anyone believe we'll still have GPS on Day 2 of any war with a near peer?

Have you tried the 3rd party DTC program? https://github.com/the-paid-actor/dcs-dtc

Lasing increases accuracy by providing a range measurement. Are you entering the correct altitude when you type in the steerpoint coordinates? Instead of manually typing in the TGP coords on the DED, why not create a mark point directly from the TGP?

I have reproduce the non-spinning right main gear and added it to the bug tracker. I see the floating too, and submitted it to the bug tracker. Can you elaborate on the rudder moving the wrong direction?

Confirmed and added to the bug tracker. Thanks for the report.

There's an optimal height that depends on your speed. If you are too far above or below this height, the HUD symbols will drop lower. It takes practice. I spent time just flying around flat ground on a training mission with the trigger safety open, testing how the HUD symbols behave at different flight conditions and getting a feel for it.

Any chance you're accidentally cycling to another cartridge with a stray keybind?

I have submitted this as a suggestion on the official issue tracker.

A trigger on your stick or a mission event trigger, it something else?

You can improve the drift over water by flipping the Doppler mode switch on the left console from LAND to SJÖ.

This is getting beyond my wheelhouse, but you want to activate it other than by clicking the keybound button or hatswitch?

I was just browsing the manual and found this paragraph on p. 162. Could this explain what you're seeing?

Strangely there's no English Wikipedia page, but the German page says the overall frequency range is 2-20 GHz. It doesn't specify the sub-bands, but a zero order guess might be to divide up that range into 5 equal geometrical bins. For example, 2-3.2 GHz 3.2-5 GHz 5-8 GHz 8-12.5 GHz 12.5-20 GHz https://de.m.wikipedia.org/wiki/AN/ALQ-131

Yep. With an initial reentry speed on the order of 20,000 ft/s, it takes only a few tens of seconds to descend from the edge of space, say 400,000 ft, to its burst altitude or ground level. And in the handful of seconds when it's in the engagement altitudes of a Phoenix it's decelerating at possibly tens of Gs. Yep, there's also a reason why ballistic missile interceptors use direct kinetic impact aka Hit-to-Kill, because blast frag warheads are ineffective. The chance that a Tomcat would ever be flying within intercept range near an ICBM's target is remote.

I think you've misunderstood something here. Maybe it could engage low flying cruise missiles, but definitely not ICBMs.

As it turns out, this is already a tracked issue based on the same request from this post: Hopefully the community fix can work for you until it gets implemented in the module.

I'll take a look at it and submit a suggestion to HB if necessary. As a workaround, is this video helpful?