Please try loading into an aircraft cockpit, when dlss fg x2 is on, and have their sim stats on, and use an xbox controller to do a complete 360 of the camera and report smoothness and mainthread timing value.
I have this exact issue with the same hardware, in VR. It dips from target fps every few seconds with a stutter (and audio stutter), especially when panning but also while still. This is even on low settings with GPU under 30-50% load. Latency is high like in your case.
This started immediately after the nvidia app installed 591.74. Game breaking!
Admin, is there a way to combine this threads and put in a bug report? I think this is a widespread issue and something is definitiely wrong with both MSFS since SU4 and the driver.
Yeah, a bug report would be good as the game is unplayable.
Further observations before I go to bed - in non-VR play, the FPS is stable but there are now occasional audio-only stutters (without any disturbances in the debug FPS counters). When in VR, there are frequent audio stutters and a good proportion of them are accompanied by graphics stutters. Some of the graphics stutters practically freeze the game.
I’ve tried DLSS presets M and K, and very low graphics settings, but it still sucks. In all cases, GPU load 40-60% and VRAM 50-75%.
I even tried loading in DLSS preset E (old version), as well as TAA, and no difference.
If this only happens after reboot to me it suggests something extra has loaded in the background. First place I’d look is Windows startup however also check all other programs that could be polling your hardware, e.g. Afterburner and (or in my case) MSI Centre, Samsung Magician, Realtek etc. Their ‘Start with Windows’ options might not actually show in Windows start up. If you do need any of these service apps then always keep them (reasonably) updated.
REALLY interesting test today. Will feed this all back to Nvidia now in my ticket.
(BTW I have uninstalled MSI afterburner, and didn’t have it running anyway. It sat there in the same dormant state since Nov, and didn’t cause and issue. Xbox game bar is off)
It’s deffo something to do with whatever came in the new driver (591.74)
For the last few days, I’ve stayed with 591.59 (18th Dec)
The following is now 100% repeatable and definite. It also has an interesting link with MSFS 2020 too. You can consider the below accurate and definite, as I’ve repeated it that many times now.
DDU drivers, clean and restart.
Install drivers (same one, 591.59, but this works whether you go newer, older or stay on the same one)
Restart PC.
See result from MSFS 2020 - ALL GOOD OK, Mainthread in teens, smooth.
Install drivers (same one, 591.59, but this works whether you go newer, older or stay on the same one)
Load into MSFS 2024 - ALL GOOD OK, Mainthread in teens, smooth.
Close sim
Restart sim (2024) and the issue returns.
Conclusions;
a) This is not isolated to MSFS 2024
b) It MAY be DX12 related, as you cannot start MSFS 2020 with DX11 at the moment
c) BOTH sims work ok after the first restart of the computer after a fresh driver install
d) Only a restart of the simulator is required to make the issue return.
So all……………
i) Is anyone else with the issue willing to give the above a go to see if you get the same results? If so, that’d be more than one provable instance I can go back to Nvidia with.
ii) I now have a temporary workaround. Although annoying, it works EVERYTIME.
Thanks and I’ll let you know how I get on with Nvidia.
I must admit this is a real headache. I have the same hardware you have but no stuttering issues. One thing you can check is also monitor refresh rate in windows (DDU resets it. So make sure it is set to your MSFS target FPS). If I were you I would try a complete system wipe at this point since it will take you less time then all the testing you are going through. Other than that I must say that latest NVIDIA drivers are not the best and caused me d3d12core.dll crash several times and I had to use DDU to solve the issue
MSFS 2020 is running at 2560x1440, while MSFS 2024 is at 3840x2160, so the resolution difference is obvious. Comparing the two doesn’t really make sense.
interessting post because I have some issues with the MSFS24 as well after installing of Nvidia 591.74. It has mainthread issues with my CPU, which is struggling a lot, I do have stuttering and as well sound distortion. When something is popping up in windows, it is slow…or for example, the sound effects in GSX are also slow…the sim is running about 45-60 fps, but the mainthread is around 24-28 ms. I have an RTX 5070 Ti with 16 GM Ram , an i7 14700k CPU and 64 GB Ram. I did all of the solution provided above, like DDU installer, BIOS update and check with Latency mon, but at the moment no solution. I also find that when you have a fresh installation, the sim runs well, but after a few hours of flying or after a new re-start it starts to slow everything down again. I also got issues with USB peripherals, like the WinWing ones, which got slower and later they stop working.
@apeduke1806 I have a massive thank you for you. Thank you so much, my sim is working fine again.
I now have a permanent (well interim) fix, and really enjoyed a long flight in the Fenix last night!!
577.00 !!!
I did actually try this before, but I can only think I didn’t use DDU that time, because on a few occasions I used the NVIDIA launcher without clean install…….
I don’t think this should be marked as solved though, as the issue is still captured in the below statement, and I will raise with NVIDIA in my ticket.
When updating to 591.74, ALL post 577.00 graphics drivers are affected no matter which one you chose.
The issue itself is, regardless of super resolution setting, TAA / DLSS / DLAA, using frame generation x2 and up causes the mainthread to be saturated.
Rolling back to 577.00 removes whatever issue that was / is.
Steps to fix for others that wish to try.
ddu driver
Clean direct x shader cache
Delete MSFS rolling cache file
install 577.0
restart
check
relaunch
check
Thanks so much all for your help diagnosing this. Not that we have a proper conclusion yet, but it all helped ruling out things that were perhaps not impacting the issue.
I will inform NVIDIA of this, and let you know the feedback………
What? Are you serious?
I already mentioned earlier that the drivers should be uninstalled using DDU to ensure a clean installation.
If you want help, you need to follow the instructions you’re given, not do things your own way. As you can see, that approach didn’t work out very well.
Next time, please follow exactly what’s suggested step by step.
KJFK, FENIX A321, TAA, Ultra/High, Fauna and Traffic - off - Ryzen 7 9800X3D, RTX 4090, main monitor OLED 4K AOC, 64GB DDR5 6000 CL26
As we can see in the screenshot above, the main thread is green and there are no issues visible there. Because of that, I’m not fully convinced the driver is the culprit - 591.94 without NVIDIA app.
I would rather lean toward a user-side misconfiguration, such as an improper NVIDIA driver reinstallation or modified game .dll files. That said, I can’t be certain, since I don’t have access to OP PC.
In any case, I’ve noticed that this new driver tends to bug out during installation, but it’s more likely a Windows-related issue rather than a fault of the NVIDIA installer itself.
Therefore, if any issues are observed, using DDU and performing a clean reinstall without the NVIDIA App and without NVIDIA HD Audio is recommended.
ALSO, all replaced .dll files should be restored to their original versions.
No, I didn’t. From the first post in this thread, I didn’t see any mention of problems related to frame generation, so I tested with FG off.
I also limited the FPS to 60 just like OP did in his MSFS settings.
From the screenshots he provided, I didn’t see Frame Generation being enabled either.
Really take your points above guys, and please accept my apologies if I’ve mislead.
It’s really important, I know, cos people might read all this to solve their own issues. And based on how I’ve felt about this, id hate someone to go off in the wrong direction.
Definitely forgetting which changes you’ve made. Guilty.
Regarding the not using DDU, completely agree. But I did on a few occasions intentionally not use it to rule out different methods of flashing. Unluckily for me, I chose 577.00 to do this.
@TenPatrol - one thing that is now clear to me is, this is certainly related to Frame Gen. I have the same clean results as you with frame generation off. But my setup doesn’t look great without it. I didn’t understand this to be a contributing factor when I logged this.
Any chance you could run the test again with frame generation x2 on?
Did you get the momentary stutters when the mainthread was at 33ms?
Because while I’ve been a little, ahem, erratic I can correlate this 32ms mainthread to MY stutters. And when the mainthread is approx 15ms, my stutter is gone.
(Which is now latched to the good no stutter 15ms mainthread condition with the rollback to 577.00)