So with selecting highest refresh rate in the NVCP settings, what do we have to do when selecting our actual monitor refresh rate? Do I need to go beyond the 120hz I’ve been running?
It uses the refresh rate that you have set in the monitor settings.
1 Like
nice site for pc
How do you get DLSS here, I just get only FSR
EDIT> Had to turn on the hardware acceleration in windows
If you’re trying to achieve the same effect while using G-SYNC, you can use RTSS as a frame rate limiter. Just make sure the limiting method is set to anything other than Reflex. This allows for a bit of frame-time headroom when you’re hitting your target frame rate, while still retaining G-SYNC functionality when performance drops below it.
With G-Sync (VRR) engaged, my approach from the original post no longer applies. Not because VRR is “bad”, but because needing VRR typically means your delivered frame rate and frame times are not stable. In MSFS, the moment you hit MainThread/CPU limits and frametimes start spiking, you get stutters and can even get audio popping/crackling. VRR can match the panel refresh to whatever the sim delivers, but it cannot remove MainThread spikes or create missing CPU headroom.
RTSS can produce very good frame pacing similar to what I describe, but only while the MainThread still has margin. Once the MainThread saturates, the pacing equilibrium breaks and neither RTSS nor G-Sync can “heal” it externally.
Also, RTSS can interact badly with MSFS. There are reports of RTSS causing crashes, and of native frame generation becoming less smooth when an RTSS lock is used. In my own testing it also occasionally broke frame generation and triggered CTDs on long flights.
I can absolute confirm the way to deal with this whole G-Sync mess… it took me ages to get behind or how msfs deals with this (honestly i dont understand it at all 
my settings
1 Like
Hi all, the new NVIDIA driver 591.74 substantially changes how frame generation and VRR behave in MSFS24 (at least on RTX 50 series).
From my initial testing, it looks like the G-Sync + FG issues that led me to recommend switching G-Sync off for the sim are finally gone. It seems one can now apply the “unsaturated MainThread” concept simply by locking FPS in the sim while keeping G-Sync ON.
Once I confirm this with more flights, I will update my recommendations in this thread accordingly.
6 Likes
Great work you’ve done with investigating and evaluating the new DLSS 4.5 features.
Can this also be transferred to FS2020 with a RTX 4080?
So, with the latest driver version (591.74).
Would this be a correct configuration for using G-Sync and FG?
1 Like
Hello, for me these settings are really good and they helped me a lot. However, I can’t seem to get the main thread as low as yours. I don’t know how you do it.
1 Like
Strange, with the latest 591.74 driver I’m having issues with G-SYNC. I have been running TAA 100%, in-game FPS lock of 40 FPS and FG x3 to give a stable 120Hz. With the previous driver (581.80) this combination worked very well, G-SYNC worked nicely on my monitor. With the newest driver and same settings G-SYNC is very sporadic and behaves as though it has lost focus with the game window. I can tell because there is a very high frequency stutter (as you would expect with a 120FPS image being displayed at 144Hz) and my monitor OSD is showing 144Hz, even though the FPS is stable at 120. When it locks back on again the OSD shows 120Hz and the image is much smoother.
I’ve seen some other reports online of G-SYNC not working properly with this latest driver in other games. This is just my experience, but I’ve gone back to 581.80 for now. I’ll keep an eye on the next driver release to see if this is fixed at my end.
1 Like
I think disabling g-sync is still necessary if you are running pop-out windows to use on other monitors.
1 Like