This is how “G-sync compatible monitors” are designed to work. They are only providing continuous frequency adaptations within their working range. G-sync technology (at GPU level) can´t solve the monitors limitation. The best case scenario is always a full range monitor or a compatible one but with the lowest posible adaptive frequency (30Hz nowadays if I´m not wrong). Outside the working limits you just have a conventional monitor, so a standard V-sync or adaptive frequency but in fixed steps only, not continuous.
Unfortunatelly in most simulators or heavy games that 30-40 Hz/fps range, which is the typical lowest working range of G-sync compatible monitors, is at the same time the typical one you face under performance stress, so you are always dancing around the lowest working limits of G-sync compatible monitors.
By the way, to prevent the tearing you see when you are below your monitor working range you can try to force V-sync at your GPU control panel, so that both G-Sync and V-sync are enabled globally instead of at application level. You can disable V-sync at your games. It will still stutter due to monitor refresh and fps mismatch inside that range but tearing should go away. This is an old Windows 11 problem that still persists.
Currently using a display port cable but i can plug in an hdmi one. I can’t see why it would make any difference though as it seems fine in all other apps or games with the existing cable.
And it’s also good once I’ve adjusted MSFS using an nvidia filter profile.
Hey folks, please keep the discussion in this topic relevant to the 576.80 Nvidia driver.
If you want to discuss other things such as Frame Generation, G-Sync, and G-Sync monitors etc. please create a separate topic for it (feel free to link to that topic here when you create it).
Interesting, after all the recent threads kicking around the pros/cons. A few 2020 flights with mixed results in 576.80; today will fly in 24/SU2 and if also mixed results, may roll back to 572.52. OTOH, so many possible confounds at all times in both sims LOL, including latest the DLSS version. Cheers
Just a friendly reminder - this topic isn’t meant for discussing the impact of rBAR on MSFS, nor is it about Nvidia Profile Inspector. We already have separate, long-standing threads for both.
Please treat this post purely as information, not as an invitation to start a discussion - otherwise things may get messy here.
Not sure if this is correct place to post this but at any rate here goes.
I just installed the latest 576.88 driver version on my store PC version of MSFS 2024.
A definite improvement over 576.80. I did turn RBAR off in my Bios earlier today and ran tests with the previous .80 version. Quite a bit of stuttering taxiing around BWI airport.
My VRAM load ran around 75% of the 8GB for the most part.
Redid the same test with 576.88:
No stuttering in the BWI airport taxiing test and the VRAM load never exceeded 65%.
So, I would definitely give this version 576.88 a thumbs up!
Mainly because the guy said he had installed the 576.88 driver and he’s the first one I’ve seen on the forums, so he might have the answer. Nobody has posted on the 576.88 thread yet, but I can ask the question on there too I suppose.
Sorry for this late reply. I’ve been kind of busy since my original post. I’m also sorry, but I don’t really know what the Ansel filters are.
For what it’s worth, I have an RTX 3070 GPU with 8GB VRAM. I don’t use DLSS nor any of the special things that one can do with the NVIDIA app. I run it at 1080P, DX12 and I don’t use HDR.
I don’t mess with color, choosing instead just to go with the default NVIDIA driver color settings.
