**THE NVIDIA DRIVERS THREAD**

[Bidley]

Ok so I just turned my PC to have a mess around with my G-Sync problems and this is bizarre.

I installed the latest drivers the other evening, and did a quick few runs on Steel Nomad to test my UV/OC. Previously I could just manage a score of 9023, this with +450 on the clock, +2000mhz on the mem and 125% power limit. Seemed a bit low but whatever, still top 9% apparently. After the driver install (clean install, followed by full system reboot) I jumped up to 9223 but had to reduce the clock speed to +430.

I turn on my PC today to mess around with G-sync, and with the same settings I decide to do a few SN runs. Bam, 9577 and I'm in the top 2%.

I fully expect to turn my PC on tomorrow and be getting something like 8500

 

[no_1_dave]

TLDR - issues when running vsync with frame gen

Honestly I don't think I've used V-Sync even once in the last 15 years.
I use G-Sync and have no tearing or stuttering issues

Your post was huge and you could have shorted in to 1 line, so I fixed it for you

 

[Rogueywon]

V-sync is the absolute devil, who lives in hell. Sooo many bad experiences with the input lag it adds. I was using G-sync until the January drivers came out, at which point I had to turn it off due to the black-screen flicker. I'm actually getting on fine without it.

 

[Eddie99]

V-sync is the absolute devil, who lives in hell. Sooo many bad experiences with the input lag it adds. I was using G-sync until the January drivers came out, at which point I had to turn it off due to the black-screen flicker. I'm actually getting on fine without it.

V-sync doesn't add any input lag when used in combination with G-sync, it just prevents screen tearing when the frame-time variance goes above your display's refresh rate. If you use G-sync without V-sync you need to set a much lower frame cap to completely eliminate screen tearing.

 

[stooeh]

'DLSS4' FG (x2) and MFG (x3 or x4) do not work properly with ANY DLSSG DLL files of v3.10.X and above when using the long term gold standard of Gsync on, Vsync on globally in NVCP, Vsync off in game, Reflex on in game if it has it. 'DLSS3' FG (DLSSG DLL v3.8.1 and below) still works fine with this gold standard, but obviously x2 FG is all you can get with this.

Vsync on has never been the gold standard for framegen, most games that I have tried block use of vsync when FG is on so only way is to force via driver. Last time I tried it was still meh when it came to input latency when forcing it on. Might be worth it with a 240Hz screen - no idea not tried it...

 

[Neil79]

V-sync doesn't add any input lag when used in combination with G-sync, it just prevents screen tearing when the frame-time variance goes above your display's refresh rate. If you use G-sync without V-sync you need to set a much lower frame cap to completely eliminate screen tearing.

Same here.. I've never had any issues with input lag Gsync+Vsync

I did try with Vsync off some months back just to see, and it didn't matter what frame cap I used it was still screaming 1000 frames in certain games

 

[wunkley]

Honestly I don't think I've used V-Sync even once in the last 15 years.
I use G-Sync and have no tearing or stuttering issues

Your post was huge and you could have shorted in to 1 line, so I fixed it for you

What a thoroughly ignorant response 'Dave'. You are not my number 1. This is why I barely post on here any more. So many negative arse wipes, and ignorant people in general.

 

[Doctor]

Did anyone else notice better ambient temps on the new driver? My 5090 idles at 21C now, was 33C on the old driver..

[edit] Nvm, what really happened is that the sensor reading is broken now, nice.

 

[Sin_Chase]

Honestly I don't think I've used V-Sync even once in the last 15 years.
I use G-Sync and have no tearing or stuttering issues

Your post was huge and you could have shorted in to 1 line, so I fixed it for you

Same. I don't know why you would ever run VSYNC with GSYNC? Surely the point is to stay within the refresh rate range of your monitor to ensure GSYNC is on and to do that you would set an FPS cap. Thereafter you have no need for VSYNC.

I lock 5 FPS below 240Hz and have no issues *shrug*

 

[Neil79]

Same. I don't know why you would ever run VSYNC with GSYNC? Surely the point is to stay within the refresh rate range of your monitor to ensure GSYNC is on and to do that you would set an FPS cap. Thereafter you have no need for VSYNC.

I lock 5 FPS below 240Hz and have no issues *shrug*

When G-sync first came out Vsync was set to ON by default in the control panel. Nvidia changed this to OFF because of people moaning that they didn't want the extra latency from Vsync. When G-sync and Vsync are both enabled together you can also change the low latency setting in the control panel to ULTRA which automatically caps your framerate. For example, I have a 165 Hz monitor and it gets capped at 158 fps.

Because it was the way it was supposed to be Gsync + VSync in Nvidia control panel, games however Vsync ALWAYS had to be off!

But again, every user can choose what they prefer.......

Using V-Sync alongside G-Sync on an NVIDIA GPU can be beneficial but requires careful configuration to avoid issues like screen tearing or input lag. According to a discussion on Reddit, some users recommend having V-Sync enabled in the NVIDIA Control Panel and disabled in-game, while keeping G-Sync enabled for both fullscreen and windowed modes.

For optimal performance, it is suggested to set the NVIDIA Control Panel's "Low Latency Mode" to "Ultra" and cap the frame rate 3 frames below your monitor's maximum refresh rate.
This setup helps maintain smooth gameplay without introducing excessive input lag.

However, some games may not perform well with this configuration, such as Total War: Warhammer 3, which experienced a significant drop in frame rate when using Ultra Low Latency settings.

It's also important to note that when G-Sync is enabled, V-Sync is automatically managed by the system. If the frame rate exceeds the monitor's refresh rate, V-Sync will activate to prevent tearing, and it will deactivate once the frame rate drops below the refresh rate.

In summary, the best approach is to enable G-Sync and set V-Sync in the NVIDIA Control Panel to On, and disable it in-game to achieve a balance between performance and visual quality.

Although I'm rather surprised we are back to this discussion again, how many years has it been?

 

[Eddie99]

Same. I don't know why you would ever run VSYNC with GSYNC? Surely the point is to stay within the refresh rate range of your monitor to ensure GSYNC is on and to do that you would set an FPS cap. Thereafter you have no need for VSYNC.

I lock 5 FPS below 240Hz and have no issues *shrug*

There's no reason not to enable V-sync when using G-sync, there's literally no downsides to enabling it and it completely eliminates screen tearing. Frame caps aren't perfect, when you cap your frame rate to a few frames below your display refresh rate, the frame cap will be your average fps but there will be some frame time variance, so it will sometimes render a frame before your monitor is ready resulting in screen tearing. This will be more noticeable on some games than others, for example MW3 had constant screen tearing without V-sync and I had to lower my frame cap all the way down to 120fps on a 144hz screen to prevent it without V-sync.

I measured the input lag by recording a 240fps video and counting the frames between pressing the trigger and getting a muzzle flash on screen, with V-sync off it was 4 frames delay, with V-sync on it was 4 frames delay, literally no difference. V-sync only adds input lag when using it alone without G-sync or if your fps cap is above your display's refresh rate. Blur busters did a good article on it, check the second question in the FAQ.

G-SYNC 101 - Blur Busters - Page 15

G-SYNC Module The G-SYNC module is a small chip that replaces the display's standard internal scaler, and contains enough onboard memory to hold and process a single frame at a time. The module exploits the vertical blanking interval (the span between the previous and next frame scan) to...

blurbusters.com

 

[Raelgun]

With the topic of Vsync and Gsync, I've found turning off windows display setting VRR off to resolve a lot of issues.

Now admittly Currently using AMD however VRR in windows was causing no end of issues, lots of stuttering, even some games frames were halved.

It won't be a complete fix but it might be an option, my assumption is VRR in windows fights with GPU makers solutions and not works with it, just a suggestion for people to try.

 

[Neil79]

There's no reason not to enable V-sync when using G-sync, there's literally no downsides to enabling it and it completely eliminates screen tearing. Frame caps aren't perfect, when you cap your frame rate to a few frames below your display refresh rate, the frame cap will be your average fps but there will be some frame time variance, so it will sometimes render a frame before your monitor is ready resulting in screen tearing. This will be more noticeable on some games than others, for example MW3 had constant screen tearing without V-sync and I had to lower my frame cap all the way down to 120fps on a 144hz screen to prevent it without V-sync.

I measured the input lag by recording a 240fps video and counting the frames between pressing the trigger and getting a muzzle flash on screen, with V-sync off it was 4 frames delay, with V-sync on it was 4 frames delay, literally no difference. V-sync only adds input lag when using it alone without G-sync or if your fps cap is above your display's refresh rate. Blur busters did a good article on it, check the second question in the FAQ.

G-SYNC 101 - Blur Busters - Page 15

G-SYNC Module The G-SYNC module is a small chip that replaces the display's standard internal scaler, and contains enough onboard memory to hold and process a single frame at a time. The module exploits the vertical blanking interval (the span between the previous and next frame scan) to...

blurbusters.com

Well done!

I was trying to remember that site...

G-SYNC + V-SYNC “On”:
This is how G-SYNC was originally intended to function. Unlike G-SYNC + V-SYNC “Off,” G-SYNC + V-SYNC “On” allows the G-SYNC module to compensate for sudden frametime variances by adhering to the scanout, which ensures the affected frame scan will complete in the current scanout before the next frame scan and scanout begin. This eliminates tearing within the G-SYNC range, in spite of the frametime variances encountered.

Frametime compensation with V-SYNC “On” is performed during the vertical blanking interval (the span between the previous and next frame scan), and, as such, does not delay single frame delivery within the G-SYNC range and is recommended for a tear-free experience (see G-SYNC 101: Optimal Settings & Conclusion).

Gsync/Vsync ON in Nvidia Control Panel

As for why a minimum of 2 FPS (and a recommendation of at least 3 FPS) below the max refresh rate is required to stay within the G-SYNC range, it’s because frametime variances output by the system can cause FPS limiters (both in-game and external) to occasionally “overshoot” the set limit (the same reason tearing is caused in the upper FPS range with G-SYNC + V-SYNC “Off”), which is why an “at” max refresh rate FPS limit (see part 5 “G-SYNC Ceiling vs. FPS Limit” for input lag test numbers) typically isn’t sufficient in keeping the framerate within the G-SYNC range at all times.

and the frame rate limit slightly below the G-Sync Range

Is ALWAYS the preferred, even Nvidia some time back said as much

 

[Neil79]

Also in regards to frame rate limiters..

Typically, in-game limiters (including Reflex) are lower latency than external limiters such as RTSS or Nvidia MFR, but the latter tend to have steadier frametime performance.

 

[Varys]

Sick of Nvidia app changing my settings. Especially making games full screen

 

[Bidley]

I've managed to find other people are having the same issues as me with the white screen flickering. It seems to diminish if I turn refresh rate/colour depth down or turn G Sync off, so it seems to be related to the connection bandwidth. So still not fixed! I exchanged about 8 or 9 emails with Nvidia support, provided loads of logs, sysinfo, told them my monitor models about four times, until they said, essentially "thanks for that, please send all of that again via this driver feedback link, and we'll fix it when we can be arsed". Cheers.

As a result I've had to have G Sync off all this time and... I can't really tell any difference

Meanwhile my 9070xt system just works.

 

[stooeh]

There's no reason not to enable V-sync when using G-sync, there's literally no downsides to enabling it and it completely eliminates screen tearing. Frame caps aren't perfect, when you cap your frame rate to a few frames below your display refresh rate, the frame cap will be your average fps but there will be some frame time variance, so it will sometimes render a frame before your monitor is ready resulting in screen tearing. This will be more noticeable on some games than others, for example MW3 had constant screen tearing without V-sync and I had to lower my frame cap all the way down to 120fps on a 144hz screen to prevent it without V-sync.

I measured the input lag by recording a 240fps video and counting the frames between pressing the trigger and getting a muzzle flash on screen, with V-sync off it was 4 frames delay, with V-sync on it was 4 frames delay, literally no difference. V-sync only adds input lag when using it alone without G-sync or if your fps cap is above your display's refresh rate. Blur busters did a good article on it, check the second question in the FAQ.

G-SYNC 101 - Blur Busters - Page 15

G-SYNC Module The G-SYNC module is a small chip that replaces the display's standard internal scaler, and contains enough onboard memory to hold and process a single frame at a time. The module exploits the vertical blanking interval (the span between the previous and next frame scan) to...

blurbusters.com

Vsync at 240Hz is going to be a lot less of an issue compared to lower refresh rates when it comes to vsync latency. GSync wont get rid of it at refresh cap since it would be in plain vsync mode at that point. I see that my games with NV Reflex cap at ~138 with vsync on at 144Hz for this reason.

 

[opethdisciple]

I had no issues with gsync + vsync + 144Hz for a decade.

 

[stooeh]

Perhaps issue wasn't the right word. Point was that the vsync related latency is lower at higher refresh rates. I don't think I'd notice it at 240Hz but I do at 120/144 in some games and I've also got used to it a bit over the years. FG input latency still a tough sell for me though

 

[Kirby Wurm]

I have performance regression with these newer drivers, very minor (under 2%) albeit repeatable, when running TimeSpy with my 24/7 OC (18000MHz RAM, +300 on the core, no UV yet), that seems directly tied to the clock speed, which is about 50-100MHz lower than when using the previous driver (572.08).

Will try increasing the core offset to compensate but don't know if I'll bother reverting if that's not stable. I've been fortunate in having no issues on this current platform using the 5080 (the AM4 system I had did have a cold boot problem initially).

On the topic of V/G-Sync, I've only been with Nvidia again for 3 months but have been using V-sync off/G-Sync application controlled in the driver's with V-sync on in games, with a frame cap of 172fps in the driver's (175Hz display) and have thus far had zero issues. These are the same settings I employed with my 6800 XT without issue for 4 years. I'm not saying these are the recommended settings, but just pointing out my experience.

Overall I'm liking the NV app, though I do miss per game OC profiles, and fully featured OC/UV options within the control panel. At the same time installing and using Afterburner again is no big hassle.