I have a question, did SU5 break MODs that try to enhance flight dynamics. As I was working on a flight dynamics MOD all was going spendid until SU5, now nothing is working.
This is beyond frustrating , SU4 was working great. It seems we take 3 steps forward and 2 steps back…can I ask what good is beta testing if you release an update with so many flaws.
So that got me thinking. I enabled VR fake mode in Dev tools and ran the same CJ4 test that I did in my bug report. Shift+6 and Shift+7 still worked as it changed the view quite quickly from the upper switches to the lower panel and amazingly the stutter wasn’t noticable. This is what CapFrameX showed. You can see where I changed the view the 5 or 6 times I did but no huge spikes like there was in 2D
Interesting…
@IslandSimPilot is not going to like this.
Love the videos by the way mate…..
However, I had a stuttering issue back in jan due to what I thought was a new driver version. Using 577.00 fixed it. After the later driver updates for dynamic frame gen, things got better, specifically in my mainthread returning to normal (32ms to 15ish)
After SU5 and updating to the latest driver at the same time, stutters were back, as was the high mainthread.
Rolling back to 577.00 has yet again fixed it.
Anyone willing to give it a try?
I also noticed (on my system) TAA would skyrocket the mainthread when compared to DLSS 4.5 with preset M. (On the latest drivers)
Back now on 577 and TAA and happy.
While my story and specs are differnt to everyone else’s, I did also see increased stutters when upgrading to su5.
EDIT. For all reading, don’t want to mislead, I use DLSS frame gen x2, and my mainthread issue is linked to that. Those not using FG will probs not benefit.
There are so many variables at play in the sim and our various configurations that it’s almost a miracle anyone gets smooth performance. But if your system is happy with 577.00, who am I to argue? The goal, after all, is to enjoy flying!
It was “people using drivers older than my car” that made me laugh.
And I do enjoy it so much when it’s smooth. I personally think the sim looks better now.
Can you link to a video capture of what you seeing? I want to see if I’m seeing the same thing but perhaps am not as sensitive to it, or if yours is markedly worse. Thanks!
If nobody is distracting us by suggesting the issue is on our end with our PCs, we’re slowly starting to reach some proper conclusions.
Good job running that test - that’s useful data.
Now do the same but with DLSS enabled, since that’s what most VR users actually run MSFS. Try DLSS Performance mode, please.
I’m on AMD so DLSS is not available to me. I tested FSR 3 performance in 2D the other day but there was no change in the stutter. I also tested it in extremely low res, 640x480. I couldn’t read the dials but the stutters were still there. 
Update: I just tested FSR3 Ultra Performance in VR fake mode and the results were the same as without FSR3, no stutters in VR mode so clearly VR is not affected by the 2D stutters we’re experiencing.
Update 2:
Sorry guys but the last statement, regarding VR users not affected, may not be correct. When I switch to VR fake mode and did my test I checked my graphics settings first to make sure they were not changed. Specifically TLOD and OLOD set to 200. So I assumed when performing the test it used those values but I decided to take a look at the Usercfg.opt file to be sure and in the graphicsVR sections both the TLOD and OLOD were set to .500000.
I tried to manually set both values in the file to 2.000000 and restarted the sim but the sim keeps putting VR values back to .5
It seems there is now way, at least in VR fake mode, to up those settings so this is not a fair comparison. VR users may very well be affected but the graphics levels are so low they don’t notice.
Even in 2D, when I set TLOD and OLOD to 50, I won’t notice the stutter but those settings are unreasonably low, as we know.
That is really weird. I wonder why?
Although it makes sense from what I am experiencing. Everything is smooth for me in VR, unless I push things to the point that I run out of vram.
This is all so strange, I use a 5090 without VR, when it gives me the stuttering we are talking about, the vram is far from being saturated, if it had been at the limit, I could understand, but in reality it is not at the limit at all.
Hi, your comment is interesting. But do you mean those slowdowns you mentioned when you look down and then, after a few seconds, look up (or vice versa), especially in the virtual cockpit? I haven’t tried using such an “old” driver; who knows, it might hold some surprises.
Yeah, mainly….
Panning the camera in the cockpit.
Panning outside
And switching views.
With some drivers, 32ms mainthread and stutters.
With 577.00, 15ms and no stutters.
Remember this is with frame gen x2.
No frame gen and its fine, but that itself looks jerky on my setup.
I think as a minimum, it’s worth seeing what your mainthread number is, or whether it spikes at the same time you get the stutter.
EDIT. tried the new driver, 596.49, and it comes with a specific fix for what i think is my issue. Improved smoothness while using FGx and vsync at the same time. Im smooth with the latest drivers again.
Ok, I want to test the 577.00 drivers. I just have one question: which files (original or modified to have more recent DLSS) do you use for framegen and DLSS in the msfs2024 folder? Oh, is the driver you mention 577.00 or other versions of 577?
I forgot to change them when I rolled back.
So in dlss swapper, theyre the latest. 3.1.06 is it?
Sorry not near my computer, going from memory
Below are the settings for VR. The default settings were actually set very low -almost everything was on Low and the LOD was 50/50. However, when I changed the VR TLOD and LOD to 200/200,
also in the UserCfg.opt file, the value was set to 2.0
I think you’ll probably explain it to me faster before I figure it out myself 
How do you enable this “fake VR” mode?
EDIT
Nvm, I found it
Every time I tried to set it to 2, it just reset it back to .5 once I enabled VR fake mode
My TLOD and OLDO in settings is still set to 200 so not sure what VRfake is using.
After enabling fake VR, in my MSFS settings both VR TLOD and OLOD stay at 200 and it’s also set to 2.0 in the UserCfg.opt file, so in my case it seems to work correctly.
What makes testing harder though is that custom views - for example OVHD and MCDU - behave differently in VR compared to 2D, so it’s impossible to test it 1:1 accurately.
Anyway, I also switched to DLSS Quality and it does seem smoother in fake VR - although that might simply be because the custom views are not 1:1. In 2D the camera is much closer, while in fake VR it’s positioned much farther away.
EDIT
I completely forgot about the SHIFT + Num7 and SHIFT + Num2 keys. I’m going to run the test again now.
If you explain to me how to test this, I can try and test with the real thing.
Just an FYI, I use 75 tlod on the ground. Lots of sacrifices with only 16gb and 8k native. It scales up quickly, but 75 on the ground. That’s what I need for the most demanding airport.
Moderator edit for translation:
Yes, the latest version you can force is 310.6. To do some testing, I’d be happy to know which version of the dll that controls framegen you’re using, which would be nvngx_dlssg.dll. I’d also like to know if you’ve also installed streamline 2.11, which is necessary for the new multiframe gen and dynamic frame gen. Thanks again.
Si, l’ultima versione che puoi forzare è la 310.6, mi farebbe piacere, per far bene dei test, sapere quale versione usi anche della dll che comanda il framegen, che sarebbe nvngx_dlssg.dll e sapere se hai messo anche la streamline 2.11, necessaria per il nuovo multiframe gen e dynamic frame gen. Grazie ancora.
