I have the 5080 and my issue was my monitor would constantly switch between displayports and go black when I enabled gsync. The only workaround was creating a custom resolution. Today’s driver update finally resolved the issue.
2 Likes
Running this on a GTX 3070, and an ASUS GSYNC’ed monitor. No issues. Actually, I don’t notice any difference from the previous driver version. In TAA mode - I am not using any frame generation stuff and limit my FPS to 40. Very smooth, predictable result with no VRAM warnings on my 8GB GPU. Oh, BTW, I am also running at 1920x1080 and 120 vertical refresh rate.
1 Like
I’m a broken record on the subject of GSync. Not long after its release in 2013, I learned the hard way (after spending $800 on a GSync monitor) that it’s not GSync that smooths out the image, it’s the refresh rate of the monitor. At one point, I had 3 27 inch monitors running. All 3 were capable of 144 Hz refresh rate. Only 1 was GSync capable. Operating at 144 Hz, it turns out, is all I needed to have an insanely butter smooth image during game play. I literary did a side-by-side comparison and there was absolutely NO visual difference between the $400 144 Hz non-GSync monitors and the $800 144 Hz GSync monitor.
With 12 years in the field, nothing has changed. GSync continues to generate more problems than it solves. It has never worked correctly and certainly not as advertised by nVidia’s marketing gurus. GSync and ALL frame sync technology is garbage, in my opinion. I think it’s long past time for us to kick it to the curb and simply buy high refresh rate monitors. With the monitor refreshing at 100 times per second or faster, it is simply impossible for the human eye to detect any tearing that may be occurring.
Thanks for taking the time to respond and with the screenshots. 
Well I don’t know what settings are incorrect. I don’t have any issues with other programs with my current settings.
I’ve tried just about everything I can think of, adjusting the monitors settings, HDR calibration, tweaking some of the brightness and contract options in the nvidia control panel etc…
Reset everything to default and tried again and again but still no joy. Borrowed a friends monitor for a weekend to try, same issues. The only thing I’ve found so far that gives me a satisfactory image quality are the Nvidia filters.
First 576.80 flight in 2020, no complaints from the FBW A320NX or the pilot. Cheers!
2 Likes
I had the same issues with my Samsung monitor switching back to DP when gsync was enabled but this driver has fixed the issue.
1 Like
Have you tried creating a custom resolution via nvidia control panel?
Interesting. I just turned off my GSync and cranked the vertical refresh rate up to max- 165.
Will try this config. for a few days and see how this works on my system.
I don’t agree. I own a G-sync full range monitor and it works as expected since I purchased it some years ago. However there are some requisites and conditions people tends to forget:
- Full range monitors provide the true fluid experience but they are expensive. Cheaper ones are not full range because they don’t include the Nvidia chip and therefore they are only G-sync compatible. This means, for instance, they will only work above 30/48/60Hz depending on model and that means you need 30/48/60 fps in game as well to see G-sync compatibility working. Below those fps values there will be no G-sync at all. This is not a G-sync problem, but a monitor problem. Supported monitors list is below. Anything not listed here or with min variable frequency above 1 Hz (the “compatible” ones) can lead to problems:
-
Exclusive full screen applications barely fail. However borderless windowed applications (like MSFS or FS2024) fail as soon as rendering focus is not in those applications. This is not a G-sync issue but how Windows and G-sync are meant to work. As soon as you click outside game or it loses focus after ALT-Tab, Windows desktop or other aplications take priority instead and therefore G-sync will match 120Hz or wathever your monitor refresh value is set in Windows or that other aplication. So, it won’t match the fps in game. In that situation the game will appear to stutter but this is not a G-sync error. G-sync is still working to render desktop or the application that has the focus. The rest of things won’t be fluid.
-
As far as I have seen main current sources of stuttering/microfreezes are game, frame generation and HAGS, but not G-sync. If you disable HAGS and use AMD FSR3 frame gen instead of Nvidia’s frame gen (as AMD does not need HAGS) you will remove most of the stuttering in big cities. Nvidia DLSS is simply broken in FS2024. SU3 is expected to fix the ones at airports according to latest beta build release notes. Anyway, despite that situation, even in the case of heavy fluctuations in fps G-sync will still match monitor refresh with it, no matter how low it is, so will keep working well.
Cheers
Working fine for me on SU3 Beta, with a 5080.
No difference I could see to the previous version.
On my 4th 576.80, FBW A32NX flight in 2020 (and my first after the DLSS update); very smooth, nothing glitchy that wasn’t so before. FPS as expected given add-on scenery DLCs.
@Wdseith You mentioned testing three monitors but didn’t specify the exact models. Could you clarify which ones they were?
If possible, also include their production or purchase dates, since firmware or panel revisions can make a big difference.
I don’t agree with you - tearing can still happen at 100Hz or higher, especially if VRR isn’t active.
Most G-Sync or FreeSync monitors only support VRR starting from 48Hz, so if your FPS drops below that, VRR stops working, and you get tearing or stutter - exactly what VRR is meant to prevent.
Also, high refresh rate and HDR mean nothing if the actual panel (matrix) used in the monitor has slow response times or weak VRR implementation.
Bottom line: It’s not just about 144Hz on the box. What really matters is the type of matrix used and whether VRR works across the full FPS range.
Ideally, VRR should kick in as low as 20Hz, so even in heavy scenes you stay smooth and tear-free.
2 Likes
This driver + the new DLSS version 310.3 is a huge improvement for me in performance, stability and V-RAM usage in DX12.
2 Likes
I can get you answers on the specific makes and models of the monitors next week when I return home. All of the monitors were 1 ms response rate and 144 Hz. What I was saying is not that tearing would not occur above 100 Hz, rather I was saying it wouldn’t be visible to human eye.
All fair statements about how to get GSync to work correctly. The comparison I made and have made multiple times, was between a true GSync monitor (not simply VRR, but one with a GSync module) and a non-GSync monitor. All tests were done in full screen EXCLUSIVE mode (not full screen WINDOWED mode) and at 144 Hz refresh rate. I stand by my statement–GSync is NOT required (nor is any form of synchronization) to get a butter smooth looking image when the refresh rate of the monitor is high.
Turning HAGS off is not required. Turning on FSR3 is not required. A butter smooth image requires a miminum of 60 FPS (before applying frame gen), a high refresh rate monitor, and minimal OS overhead (i.e., nothing running in the background). Getting the FPS to 60+ requires tweaking the in-game graphics settings to levels your GPU can handle at your monitor’s native resolution.
None of this is rocket science. If GSync gives you a placebo benefit, great. But it is absolutely not required for a butter smooth image.
1 Like
This is the first Nvidia driver for ages that has not caused me a single BSOD. I have been getting loads on most days for over a year & not just in Flight Sim. I have a RTX 3060 12GB with a i7-8700K.
2 Likes
G-sync indeed exists to avoid the need of reducing game graphical settings to achieve 60 fps or wathever the figure for the refresh rate you choose.
Basically if you are going to sacrify image quality in favour of reaching the min performance required to maintain 60 fps in all kind of scenarios you can face in game then sure, you don´t need G-sync.
In my own experience you will always find several cases in most games where current workload drops performance after having selected your ideal settings, unless you reduce settings to really low values or you only play old games on a high-end PC. MSFS and FS2024 are the perfect example of how hard is to balance quality and performance as performance basically depends on the combination of each aircraft, scenery, airport, traffic and weather conditions.
However if you want to keep the same quality everywhere and sacrify fps without facing V-sync stuttering then G-sync (with a full range monitor indeed) is the way to go in my opinion.
It´s not placebo. You can compare both approaches in these demos:
-
FPS goes below your selected refresh or target and stuttering happens
UFO Test: Demo of Stutters and Tearing -
FPS changes do not produce stuttering with G-sync enabled
UFO Test: Demo of Stutters and Tearing
Cheers
1 Like
Don’t blindly trust everything AI says - it doesn’t even know that FG is currently bugged in MSFS. As impressive as it might seem, it’s not a reliable source when it comes to flight simulators or gaming. People like us simply know better in this field.
There might be something wrong with your GPU or OS, because I also have an RTX 4090 and I haven’t had any issues with DP - neither with older nor newer NVIDIA drivers.
It might be a good idea to start a new thread describing the issues you’re having - someone will definitely be able to help.
This current topic is focused on NVIDIA drivers, so it’s probably not the best place for troubleshooting.
1 Like
I did some tests yesterday.
I have a Ryzen7090, a RTX4080 and a gSync-compatible 4k Monitor 40-60 Hz, FS 2024 SU3. I did tests
- FG: FSR3, LossLessScaling (2x, not adaptive), DLSS (HAGS deactivated without DLSS)
- gSync on/off
- vSync on/off
- Framelimiter off, 30 FPS and 29 FPS.
- rebar on/off, one test deactivated in BIOS and on test deactivated in nVidia Profile Inspector ( in BIOS it was on).
The Scenario was EDDF at gate A54 with inibuilds A350 and “Force LOD 0” in Debug Mode turnt on. The ingame settings have been optimized with nVidia App (most is ultra, DLSS upscaling in “Quality”). This results in 13 - 15 GB VRAM usage, but not limiting the Framerate. I did some large flights around the plane with the drone camera, to the city of Frankfurt and the soccer stadium (“Waldstadion”), in oder to change the scenery and force other textures to load.
The results:
FSR3 is the worst. Stutters in particular with Drone Camera outside the plane. Enabling FSR3 increased the main thread times in particular (close to 40 ms in certain situations). Lossless Scaling and DLSS are close together in terms of performance, both showed no stuttering at all having the right settings (see below). But DLSS looks better. In Lossless Scaling you can see the “morphing” in particular switching between Cockpit and Drone camera (sudden large change in the picture).
gSync is a must. Tearing and Stuttering increases heavily without gSync.
vSync is a must with DLSS. For LossLess Scaling it had more or less no impact.
Rebar has absolutely no influence, neither deactivated in the BIOS nor in the nVidia Profile Inspector, neither in terms of VRAM usage nor in terms of performance.
The game Changer: FPS limiter to 29 FPS. Without limiter (leads to around 38 - 40 FPS) or at 30 FPS limiter (my Monitor has a limit of 60 Hz) it stutters heavily, and tearing is visible. But 29 FPS Framelimit, which results in 58 Hz with FG, is absolutely perfect using gSync and vSync. Small variations in frame rate over and under 58 Hz are covered by gSync. The Framelimiter leads to constant frame times, the result is always somewhere in the range of the gSync, which makes it perfectly smooth.
So I can’t confirm, gSync is causing trouble, but you have to take care to stay within the gSync range - also FPS above the gSync range is critical. And I can’t confirm DLSS is a mess in 2024, it was the best out of 3 FG methods (while Lossless Scaling was very close and is absolutely recommended in case DLSS is not available).
3 Likes
Please forgive me if this is a stupid suggestion but did you try swapping out cables?