NVCP V-sync + Frame Gen Stutter

+
I cannot use V-sync in the Nvidia Control Panel + Frame Generation in game without massive stutters every few seconds. Sometimes its every few minutes, still unplayable. Here's the thing, without using V-sync i get screen-tearing, so that's not an option. I'm on a 165hz G-sync Monitor and no matter the FPS cap I set within the NVCP i get tearing. It's almost as if my G-sync is being disabled while using frame generation somehow. So i have several options: play with V-sync on/FG on with stutter, play with V-sync off/Frame gen on and get tearing, or just don't use FG at all and have less FPS but a smooth experience. Currently the only work around I've found (due to my own time trouble-shooting as I've yet to find a solution from anyone else) is to set V-sync to fast and use 2x FG. With this setup i get around 120 FPS and zero tearing, however, as soon as I turn Path tracing off my FPS shoots up and I do. This work around doesn't work with 3x or 4x FG. I have no idea what else to try; I need to get this game to function properly with FG 3x/4x AND V-sync turned on in the NVCP. I don't have this problem in MH Wilds, and that game and CP are the only games where I've ever used FG. Maybe I'll reinstall The Witcher 3 and see if this problem persists, idk. If anyone has a 50 series card and does or doesn't have this issue I'd love to hear it.

EDIT: Also, running just V-sync by itself does not seem to limit my FPS as it does in other games through reflex. I've also seen others saying that FG automatically enables reflex in-game and caps your FPS. This DOES NOT happen for me. With no manual FPS caps my FPS exceeds my refresh rate while using 3x or 4x FG.

Specs:
Ryzen 7 9800X3D
MSI Gaming Trio RTX 5070ti
Corsair Vengeance 32GB DDR5 6000 C30
 
Also, running just V-sync by itself does not seem to limit my FPS as it does in other games through reflex. I've also seen others saying that FG automatically enables reflex in-game and caps your FPS. This DOES NOT happen for me. With no manual FPS caps my FPS exceeds my refresh rate while using 3x or 4x FG.
That seems very weird, V-sync without FG and reflex should work. v-sync with FG is a bit of a conflict since Reflex gets enabled witch is about lowering latency due to v-sync, this is why you cant enable v-sync when using FG ingame you can force it trough NVCP but it will not work perfectly. You could try to force Fast v-sync in NVCP and se if the stutters gets better. Also have you enabled g-sync for windowed and fullscreen? I use Max frame Rate for CP2077 in NVCP and it works fine, i only overcap on menus tho since i play with PT. I do get stutters at times but its generaly loading or when autosaving.
 
I think I was incorrect about V-sync not capping my FPS but FG, which enables reflex, does not cap my FPS. AFAIK Reflex is supposed to behave like an FPS limiter, as it does in Destiny 2. I've tried fast sync with an FPS cap of 150 and 2x FG and that's the smoothest experience I can achieve. However if I turn PT off my FPS becomes too high and i get screen-tearing. I do have G-sync enabled on a G-sync Chip Monitor but not both windowed and Full screen. 3x or 4x FG is a tearing mess regardless of my FPS not being over my refresh rate. It's all behaving so weird for me in CP.

Thankfully Nvidia staff responded to me on the Geforce Forum and is aware of this issue with V-sync and FG in Cyberpunk. They've been unable to reproduce it on their systems but he had me use GPUView to create a trace log of the stutter and email the log to their driver support.
 
I think I was incorrect about V-sync not capping my FPS but FG, which enables reflex, does not cap my FPS. AFAIK Reflex is supposed to behave like an FPS limiter, as it does in Destiny 2. I've tried fast sync with an FPS cap of 150 and 2x FG and that's the smoothest experience I can achieve. However if I turn PT off my FPS becomes too high and i get screen-tearing. I do have G-sync enabled on a G-sync Chip Monitor but not both windowed and Full screen. 3x or 4x FG is a tearing mess regardless of my FPS not being over my refresh rate. It's all behaving so weird for me in CP.
Ive never hade my fps caped by reflex in any game. Im on the 4090 so cant test the x2 or x4 FG at all but without that for me its smooth, i do get some spikes but there rare and when driving fast or similar. Hopefully the nvidia test will help.
 
Apparently there's a driver issue with 50 Series cards causing V-sync and G-sync to result in frequent stuttering while using multi-frame gen. Not sure if regular FG is impacted by this or not.
 
Yeah I tried just setting a manual fps cap without forcing v sync and I got massive screen tearing even though I'm on a G-sync display. I even set my cap a whole 10 fps under the refresh rate to be sure. As is typical with the 50 series launch, tons of issues, lol. So far I have to basically disable G-sync and force V-sync while using 4x FG for a smooth experience, but then I have atrocious latency so it's kinda meh. At least it's smooth though.
 
Yeah I tried just setting a manual fps cap without forcing v sync and I got massive screen tearing even though I'm on a G-sync display. I even set my cap a whole 10 fps under the refresh rate to be sure. As is typical with the 50 series launch, tons of issues, lol. So far I have to basically disable G-sync and force V-sync while using 4x FG for a smooth experience, but then I have atrocious latency so it's kinda meh. At least it's smooth though.
How is it without x4 FG? does it work with just dlss+fg?
 
I've been able to get 2x FG to run smooth by turning off V-sync but leaving G-Sync on. I get around 120 FPS but that's with Path Tracing. If I turn PT off my FPS caps out and I get tearing. There's definitely some driver bug affecting both V-Sync and G-sync while using FG, at least with 50 series cards anyway. According to some Nvidia employee on the forums they are aware of the problem but apparently they've known about it for weeks. He just asked me to send my GPUView trace logs to their driver support so hopefully a future driver update will resolve this.
 
Top Bottom