Machalot

When altitude hold autopilot is engaged, the altitude can be adjusted using the trim switch up and down. The reference symbology on the HUD slides up and down when the trim switch is held, but it moves much faster than the altitude reference value tracked by the autopilot. So after releasing the trim switch, the autopilot holds the new reference altitude, but the HUD symbols are aligned to a much different altitude. Pressing the Reference button or momentarily turning the autopilot off and back on with realign the HUD symbols with the current altitude. I'm posting on my phone so I don't have a track at the moment. It's easy to reproduce, but if a track is requested I can make one tonight.

Why don't you fly it for two weeks under the Free to Play program and see for yourself if you are satisfied with the detail of the animations?

I will admit I didn't write my post very well since I was using my phone. I also had a sentence in there about how increased speed increases Mach and dynamic pressure, which changes the pressure distribution on the skin and structure. That's how you can eventually destroy an airframe in level flight at 1 g. The Nz accelerometer doesn't measure axial G's at all (which would only be part of the story), nor does it measure bending and shear stresses on the wing roots and control surfaces. Anyway, @GGTharos said it better.

Measured G is not strictly the same thing at all speeds. The dynamic pressure and Mach number increase with speed, resulting in a different pressure distribution on the skin and structure, which changes the lift to drag ratio. The angle of attack required to deliver a certain G load decreases, and the G component measured by the accelerometer more closely aligns with the total G load. That's not to say the model is correct, but it's more complicated than "G is G".

Use M-SEL

As far as I know, A0/A1/A2 setting has nothing to do with radar ranging. In ANF mode usually the radar display is disabled regardless of the A0/A1/A2 setting.

I agree. The error is occurring in flightdataunit.cpp, which seems like a plausible name for some avionics and instrument model(s).

The expected range of some variable is given as 0 to 2 pi. I would bet money there is an issue with calculating the yaw, pitch, and roll Euler angles at vertical. Based on the values 0 to 2 pi, it's likely yaw. (Pitch is typically -pi/2 to +pi/2, and roll is typically -pi to +pi.) There is a known singularity in the math at +/-90 deg pitch angle. A "nan" result could be from trying to divide by zero [which is cos(90°), and appears in the denominator of the yaw equation] or by taking the inverse trig function of a value outside the range [-1, 1]. Both of those operations can appear in the relevant Euler angle equations, depending how they're written. The range exceedance could be the result of floating point rounding error. These things should only occur very close to 90 deg pitch, which is why sometimes you don't get the crash, and sometimes you do. My own hypothesis, anyway. That's where I would start debugging.

Wild guess, there is extrapolation going on within the targetting software to calculate where you placed the cursor, because the image is out of date while the jet keeps moving. The longer you wait, the less accurate the extrapolation becomes.

First, you never have to bother with it because it is automatically set when you spawn. If you really want to set it, the way it's set up for mouse interaction is bugged. The dial is only selectable when the switch cover is closed. I have never bothered to figure it out.

You need to bring an overwhelming number of Viggens so some of the missiles get through.

This is correct. The software model cheats in that it knows the possible ranges of longitude for each DCS map, so it knows that latitudes over 100 will be two digits, and on some maps it knows it can only be west.

Earth rotation rate is 15 degrees per hour. Does that explain this drift? I'm not sure if it's actively compensated for this. Older INS packages sometimes weren't.

True for steady and uniform wind. But gusts or shear do have an effect. You probably know that but I just wanted to be sure.

I do it completely by feel. All the keys I mentioned have distinct layouts that are easy to find.

I just installed the mod. I like the large destination characters. But the S in LS is enormous, much taller than the L and even slightly exceeding the size of the small window it resides in. Is that real?

Is there a reason you can't map it to the keyboard? I use the arrow keys for the dobber, RCtrl+up/down for the increment, the numpad numbers and Enter key, and numpad . for RCL. I also mapped the 6 com/master mode buttons to the group containing Insert, Home, Page Up, Delete, End, Page Down.

Yes, and you can only move one axis at a time, no diagonal movement.

Any idea why this mod (and the cockpit textures mod) doesn't work from the Save Games folder, but has to be placed directly in the game install folder?

Radar ranging activates below a certain dive angle. If you go above that dive angle, it deactivates.

If you set the QFE exactly correct for the target, does it still jump? I think you're seeing radar ranging override the altitude setting.

New algae bloom model

Could be switching into and out of radar ranging mode below a certain pitch angle.

Can you elaborate? I use the Viggen in MP all the time, so I'm wondering what I'm missing.

People seem to be confusing these two concepts: stall, which is a disruption of airflow over the wing that reduces lift, and is almost purely an angle of attack phenomenon independent of weight, and only very mildly dependent on airspeed the condition of flying too slow to maintain level flight at an unstalled angle of attack, which is directly dependent on weight