Hiob

More weight requires more lift. More lift can be generated by more AoA or more speed. Since you will eventually run out of AoA and stall, let alone need a given AoA for a proper approach, you have no choice but to increase speed with higher weights.
That‘s universal for every plane btw. not just the Viper.

What are your shadow settings? Looks to me as if you had shadows very low or off. Maybe that causes the unnatural light? 

DLSS doesn't work that well with lower resolution. When you reduce the render resolution from there, there isn't much raw data left to interpolate from.
Do you really need to use DLSS? 1080p shouldn't be too demanding on the system (which of course I don't know the specs of).
Perhaps you post your specs and settings and I can try to suggest optimal settings - but I fear that you just reached the edge of the envelope for DLSS there. Not mnuch you can do to improve on it.

I would think so. I assume in RL the fight is over at this point. (Movies don't count as a reference). Double so when you take into account, that in RL every aircraft carries some boomsticks.
Edit:
Lol - I don't know if that counts as "solution".... I'm by no means a subject matter expert! 😅

Not really trackIR related I think. 
The darkening or inconsistent brightness issue is a reported bug in the 2.9 beta release afaik. Nothing to do but wait for ED to fix it I guess. (Maybe make a bug report and provide a track in the proper sub-forum) 
The triple monitor setup may add to the trackIR problem. I don’t have experience with such a setup, sorry. (have you enabled the status lights on your trackIR camera? Most of the time my head tracking goes haywire, the camera lost sight of the reflectors/IR-leds of the head piece, due to excessive angles)
I never noticed any influence of the NVCP on trackIR either. Maybe apart from different V-sync or frame-cap settings. But those are supposed to influence the stuttering issue that some people have with trackIR. (Personally I think it‘s snake oil, but to each his own).

I can’t comment on the difference to the old version. But that is for sure a maximum weight configuration that would rarely be used in RL and certainly not in high elevation and hot air conditions.

It's already reported and acknowledged. The sound of the Mi-8 is currently w.i.p. and some bits of it made accidently into the release.
Take a look in the Mi-8 forum for more details.
 
 
p.s. When you have aircraft-specific issues, it is best to look and post in the according sub-forum. 

I think the MT won't call the updater. Try run the standard version. Once updated, you can run the MT-shortcut again.

Ok, third time is a charm.
I was finally able to reproduce your power loss (due to a droop in rotor rpm). When I turned on the anti ice, it was the icing on the cake (pun intended). No, in all seriousness. Heading AP, Anti-Ice, Dust-Protection, that all directly or indirectly draws power from the main rotor (or the attached generators) - at some point - it is too much.
Make it a habit to only turn on those systems when you need them OR at least when you are out of hover/transitional lift  and in a controlled cruise flight.
Oh, and to top it all off, you had the heat suppressors equipped.... 😅😉

That is called Aliasing. You can set MSAA*2 or MSAA*4 to improve that, but it hits performance.
And of course SSAA.... also hits performance

To answer the original question: Yes.
Quote: "A force trim system is incorporated in the longitudinal, lateral and directional control axes. The force trim system is designed to keep the controls in the position that the pilot or CPG selects."

Lower your head to be on the same level as the center point of the instrument. The needle is quite a bit in front of the scale. I assume the problem is gone then.
 

Too slow! 😜 But yes - that it is - thank you! 🤗

You need to unlock it first with the silver/grey switch below the canopy frame on the right side (somewhere in the middle).
It's not a bug. It works - it's just confusing at first. But it makes sense when you think about it. It keeps the wind from slamming the canopy shut.

I think he's refering to the clipping. The wheels sink "into" the carrier deck. That is not unusual for objekt on object collision models though. Unless specifically optimized for carrier landings (which the Macchi obviously isn't) that's probably the norm.
I wouldn't worry about it unless the same happens on concrete runways.

I would recommend though, to leave this setting in DCS alone and limit the fps in the Nvidia Control Panel.
I'm not quite sure how it works, but from what I observed - when the fps are in some way, shape or form limited, the Menu-fps match the ingame-fps (respectively the capped limit).
However, when the fps are free, the menu-fps would sky-rocket (like in other games) and in that case, DCS catches them around 60 fps.
Edit: That observation may be outdated though, I haven't paid particular close attention to that matter since tge latest update.....

SAS saturation means, that the system has reached its maximum available offset. The way the sas works is, that it offsets the position of your flight controls, via magnet coupled hydraulic actuators, but they only have a certain amount of available travel. When the offset is going in the same direction all the time (perhaps due to side winds) it will reach its maximum and can’t do anything until the middle position is reset.
You can observe, what it‘s doing with the „box“ in the controls overlay.

Ok, I did a small Benchmark scene with your IA-Mission in the Caucasus. See attached file (sorry for the wobly flight, I had no controls set up).
Those are the results:
22-06-2022, 20:19:54 DCS.exe benchmark completed, 5315 frames rendered in 49.187 s
                     Average framerate  :  108.0 FPS
                     Minimum framerate  :  100.9 FPS
                     Maximum framerate  :  115.1 FPS
                     1% low framerate   :  100.5 FPS
                     0.1% low framerate :   94.7 FPS
Those are my settings: (plus I had Reshade enabled)
Start and Stop the record when the head moves to get comparable results.

SU25T.trk
 
Edit:
Oh - I found your Problem. 😊
What do you pay for the solution?
(Kidding)
You're most likely getting way too much fps. DCS is by default capped at 180. When you get more than (or close to) this - weird things starts to happen.
You can either limit the max fps in the NVCP to 120 e.g. OR modify a line in the /DCS/Config/graphics.lua from "maxfps = 180" to "maxfps = 300". (line 428)
(Or simply ramp up the visual fidelity).
Let me know if that solves your problem!
 
Edit2:
Results with Settings to "low":
22-06-2022, 20:38:50 DCS.exe benchmark completed, 8123 frames rendered in 49.094 s
                     Average framerate  :  165.4 FPS
                     Minimum framerate  :  158.6 FPS
                     Maximum framerate  :  173.5 FPS
                     1% low framerate   :  152.0 FPS
                     0.1% low framerate :  124.1 FPS

Just a general question: Do you have any overclocks applied? (gpu or cpu). I had crashes too, at first, and needed to tune down the clockspeeds slightly. The new version (or the apache module) seem a bit more demanding. No problems since.
Sorry, if I sound like a broken record. 😄