Frame gen needs VSync off to work properly with reasonable latency, it isn't a bug it forces it off in games which support it - you need to use G-Sync and cap frame rate ~3 FPS below refresh rate if you want "VSync" though that might cause some stutter due to frame pacing limitations.
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
**THE NVIDIA DRIVERS THREAD**
- Thread starter Boomstick777
- Start date
Frame gen needs VSync off to work properly with reasonable latency, it isn't a bug it forces it off in games which support it - you need to use G-Sync and cap frame rate ~3 FPS below refresh rate if you want "VSync" though that might cause some stutter due to frame pacing limitations.
Right - For the last 10 years or so the accepted and best standard is to run Gsync on in NV control panel, Vsync on in NV control panel, and Vsync off in any in-game setting. This has worked perfectly for years. If you want the best latency also use Reflex if a game has it, if not cap your FPS to ~3 under your refresh rate using RTSS.
With the 572.xx drivers and the release of the 50 series, and the newest DLLs for framegen (basically anything above nvngx_dlssg.dll v3.8.1) - x2 framegen does not work properly - GPU usage will not go above ~80% and you don't get full performance. An easy way to test/ show is the frametime line in RTSS's own frametime monitor looks 'fat'.
Also with these latest framegen DLLs (nvngx_dlssg.dll v3.10.xx), if on 50 series x3 and x4 framegen just does not work. At all. Either has zero effect or causes stuttering.
The only way I can use framegen reliably on my 5080 is to make sure the game is using nvngx_dlssg.dll v3.8.1 - then use x2 framegen which works perfectly, the RTTS frametime line is thin and normal and GPU usage is maxed out as it should be.
There are quite a lot of threads around on the interwebs about this, but it doesn't seem to be as known about an issue as it should be. The really weird thing is, I'm pretty sure x2, x3 and x4 framegen worked properly on the first set of 572.xx drivers, but I can't roll back to those as they didn't work for any SteamVR games!
(Also, I DDU'd and reinstalled latest drivers again and the weird fps issues I was having are gone so at least that's fixed. But the DLSS4 frame gen issues are exactly as they were and haven't been fixed in these latest drivers, and the release notes say they have).
Last edited:
Not correct. See above
Last edited:
I've just noticed I'm getting a roughly 5% better average framerate in Monster Hunter Wilds compared to yesterday, with much improved 1% lows. Problem is, I've no idea if that's down to the new drivers or to a game patch that also released today.
I can't say what may or may not work in different driver versions and what the trade off might be but at a functional level they are incompatible at game engine level and even driver level vsync with frame gen has some considerations. Similarly frame rate caps have problems with frame gen.
I always force vsync on via the Nvidia control panel and leave vsync off in-game with my G-Sync compatible display which that is always turned on. For me, I really don't get any issue with frame gen on in any game that I've tried.
Just played AC Shadows earlier for the first time on 572.83 as I haven't installed the latest ones yet, and it ran extremely smoothly with frame gen on and vsync off in-game but still capped globally via the control panel. My 4090, as always, gets maxed unless I reach my vsync cap where it naturally drops.
With so many different hardware combos it's going to be different for everyone, but this way has worked very well for me for a few years.
Update: Just installed 576.02 over 572.83 and the install went fine as it should, no permanent black screen during install this time with both of my displays, they went off and both came back about 5 secs later. At least something from Nvidia works
Just played AC Shadows earlier for the first time on 572.83 as I haven't installed the latest ones yet, and it ran extremely smoothly with frame gen on and vsync off in-game but still capped globally via the control panel. My 4090, as always, gets maxed unless I reach my vsync cap where it naturally drops.
With so many different hardware combos it's going to be different for everyone, but this way has worked very well for me for a few years.
Update: Just installed 576.02 over 572.83 and the install went fine as it should, no permanent black screen during install this time with both of my displays, they went off and both came back about 5 secs later. At least something from Nvidia works
Last edited:
Open Issues:
[GeForce RTX 50 series notebook] Resume from Modern Standy can result in black screen [5204385]
[RTX 50 series] Cyberpunk 2077 will crash when using Photo Mode to take a screenshot with path tracing enabled [5076545]
[RTX 50 series] Red Dead Redemption 2 crashes shortly after starting a game in DX12 mode. No issue in Vulkan mode [5137042]
[RTX 50 series] Colors may appear slightly saturated in games when in game-resolution is below native resolution of monitor and display scaling is set to 100% [5158681]
Forza Horizon 5 lights flicker at night time [5038335]
Track corruption in Forza Motorsport in benchmark or night races [5201811]
[RTX 50 series] Hogwarts Legacy may display flickering when Frame Generation is enabled [5216455]
[RTX 50 series] Portal RTX displays rainbow colored artifacts after updating to GRD 576.02 [5108472]
[GeForce RTX 50 series notebook] Resume from Modern Standy can result in black screen [5204385]
[RTX 50 series] Cyberpunk 2077 will crash when using Photo Mode to take a screenshot with path tracing enabled [5076545]
[RTX 50 series] Red Dead Redemption 2 crashes shortly after starting a game in DX12 mode. No issue in Vulkan mode [5137042]
[RTX 50 series] Colors may appear slightly saturated in games when in game-resolution is below native resolution of monitor and display scaling is set to 100% [5158681]
Forza Horizon 5 lights flicker at night time [5038335]
Track corruption in Forza Motorsport in benchmark or night races [5201811]
[RTX 50 series] Hogwarts Legacy may display flickering when Frame Generation is enabled [5216455]
[RTX 50 series] Portal RTX displays rainbow colored artifacts after updating to GRD 576.02 [5108472]
Soldato
- Joined
- 11 Mar 2013
- Posts
- 5,533
Have a 4070 super. New drivers good?
A slight improvement on the previous version, but many of the problems we've had since late January are not fixed.
Haven't had any problems on my 5080 apart from a black screen during one driver installation which was easily resolved by turning my monitor off and on again.
Noticed a performance uplift on these new drivers as well, so all gucci for me
Noticed a performance uplift on these new drivers as well, so all gucci for me
Soldato
- Joined
- 21 Oct 2002
- Posts
- 6,490
- Location
- West Sussex
All working fine here, as per normal
Soldato
- Joined
- 11 Mar 2013
- Posts
- 5,533
I was getting BSD on the last couple driver updates.
This one worked perfect. No issues.
Cheers
g-sync flicker or OLED flicker?
Cos OLED flicker is just something that happens with OLED and there are ways to minimize it.
Not experienced g-sync flicker and I always have g-sync on
I've no idea. It really flares up when g-sync is turned on, but it doesn't look like the usual g-sync flickering you see on YouTube. And it isn't OLED flicker because one of my monitors is IPS and it does it on that. It doesn't happen if one of the monitors is switched off.
I'll try and upload a video but it looks almost like a dodgy cable connection, the whole screen distorts and flickers for a millisecond. I've tried multiple cables, DP and HDMI. It's worst sitting idle at desktop.
Last edited:
That's what I've been using since I got 4090 back in the days, without issues. That is, as long as I don't set low latency in drivers to ultra, which drivers suggest is advised for gsync monitors - that totally broke FG in most games for me. Keeping it on but not on ultra seems to be working ok.
This had been an issue with 4k series and FG - it didn't work with vsync at all initially. Nvidia back then fixed it relatively quickly, so it has been working fine since - when vsync is used in Nvidia drivers instead of the game. It always worked great on my 4090 since that fix. And then they messed it up again with MFG apparently - but that's not something I can and would use.
Last edited:
First time since 5k series arrived that new driver didn't cause black screens on install for me. Also, my astrophotography processing software is now much more stable (especially AI models in it) since yesterday's release - and I use my GPU for that more than I use it for gaming these days.
Last edited: