DLSS 3 post 1.61 - still heavy lag exiting out of menus

[Alfredo_Linguini]

I am still experiencing this problem.

It does not make a difference whether I have MSI Afterburner and RivaTuner on or not.

https://www.reddit.com/r/cyberpunkgame/comments/10qyotn
Please fix this, I want to finally play this game with good graphics...

Version 1.62: Problem still persists.

 

[brentcharles]

I am still experiencing this problem.

It does not make a difference whether I have MSI Afterburner and RivaTuner on or not.

https://www.reddit.com/r/cyberpunkgame/comments/10qyotn
Please fix this, I want to finally play this game with good graphics...

Hi there,

I don't know if this will help, but this is how I resolved the frame gen stuttering on my Ryzen system:

1. Install Process Lasso
2. Start game, make sure frame gen is disabled, and DLSS is set to "Auto"
3. Alt-tab to Process Lasso, right-click on the cyberpunk process, then click on CPU affinity
4. Uncheck half the cores as shown in the attached pic and hit Ok
5. Switch back to the game and enable frame gen (leave DLSS upscaling at "Auto"

The game runs perfectly fine for me using this method with a Ryzen 7700x and RTX 4080. I get ~150fps walking around and ~120fps driving at 1440p with everything cranked and RT set to Psycho.

I hope this helps!

 

[Alfredo_Linguini]

Hi there,

I don't know if this will help, but this is how I resolved the frame gen stuttering on my Ryzen system:

1. Install Process Lasso
2. Start game, make sure frame gen is disabled, and DLSS is set to "Auto"
3. Alt-tab to Process Lasso, right-click on the cyberpunk process, then click on CPU affinity
4. Uncheck half the cores as shown in the attached pic and hit Ok
5. Switch back to the game and enable frame gen (leave DLSS upscaling at "Auto"

The game runs perfectly fine for me using this method with a Ryzen 7700x and RTX 4080. I get ~150fps walking around and ~120fps driving at 1440p with everything cranked and RT set to Psycho.

I hope this helps!

Hi, this got me excited but sadly it did not work. I followed each of your steps, disabled CPU 8-15 with Process Lasso, left DLSS on Auto.

It is really too bad, it's been 2 years I've waited to play. Thanks for helping.

 

[Lors]

It can't be called fix if you have to set DLSS to auto or have to disable half of the cores.
The higher the resolution, the more workload is pushed towards GPU and the heavier is the stuttering.

I don't really think there is a fix for any modern Ryzen CPU right now. I switched to Intel and the stutter was gone.

 

[Alfredo_Linguini]

It can't be called fix if you have to set DLSS to auto or have to disable half of the cores.
The higher the resolution, the more workload is pushed towards GPU and the heavier is the stuttering.

I don't really think there is a fix for any modern Ryzen CPU right now. I switched to Intel and the stutter was gone.

Is the problem because of AMD CPU? I would have been fine with a temporary fix but I would not settle to leave DLSS to Auto, i think the game just makes it default to performance mode which is too blurry for me.

 

[Tiklandian]

How did CDPR still not fix this in both games yet lol....

 

[don_homas]

Is the problem because of AMD CPU? I would have been fine with a temporary fix but I would not settle to leave DLSS to Auto, i think the game just makes it default to performance mode which is too blurry for me.

Here is a long thread about the same issue in witcher 3. Each and everyone reporting about it is using a ryzen, including myself :/

DLSS 3 Frame Generation produces severe stutters/freezes

I'm playing on RTX 4090 + Ryzen 5950x and 64GB DDR4 3200 RAM. Gsync ultrawide monitor Playing at max settings RT all on. But noticed this happens on any setting. When Frame Generation option is enabled I'm getting severe stutterings/freezes. Noticing 2 types of situation when this is happening...

forums.cdprojektred.com

 

[brentcharles]

I've been doing some additional testing, and found a few things:

1. Ignore the part about setting DLSS to 'Auto'. That is unnecessary, your preferred setting should work fine (I'm using 'Quality' now).
2. The monitor I used with my workaround above has a native/max resolution of 1440p/165hz.

I decided to test this setup with my LG C9 (native/max resolution of 4k/120hz). I left the in-game resolution at 1440p and all other settings unchanged. And the stutter was back.

So I changed the in-game resolution to 4k (the native resolution of the TV), and set DLSS to 'Performance', with all other settings unchanged. The stutter was gone again.

I don't understand what role (if any!) the output display would have in this; some help from CDPR certainly would be appreciated.

 

[Vyrisus7]

I've been doing some additional testing, and found a few things:

1. Ignore the part about setting DLSS to 'Auto'. That is unnecessary, your preferred setting should work fine (I'm using 'Quality' now).
2. The monitor I used with my workaround above has a native/max resolution of 1440p/165hz.

I decided to test this setup with my LG C9 (native/max resolution of 4k/120hz). I left the in-game resolution at 1440p and all other settings unchanged. And the stutter was back.

So I changed the in-game resolution to 4k (the native resolution of the TV), and set DLSS to 'Performance', with all other settings unchanged. The stutter was gone again.

I don't understand what role (if any!) the output display would have in this; some help from CDPR certainly would be appreciated

I've been testing this extensively the past several days to figure out exactly what causes this. As others have experienced, I have the same stuttering issue in and out of menus with a Ryzen CPU when frame gen is enabled. It has nothing to do with your display. The issue is triggered by how much load is on your GPU when you go into or out of menus and/or cutscenes. If you have frame gen enabled and your GPU is at or very near full load when you go into the map/inventory/settings screens, then you will get severe stuttering when you close those screens and go back into the game. However, if you configure your game settings in such a way where the GPU stays under full load at all times, the stuttering is largely eliminated. Not completely eliminated mind you, but it's mostly gone except for maybe a tiny hiccup coming out of the menu screens here and there.

There seems to be some kind of problem in this game with the way the GPU and Ryzen CPU's keep step with the game engine (and each other) when the GPU is at full load with frame gen enabled. In these instances, it seems like the game engine is massively spiking the load to the GPU temporarily beyond its limits and the GPU has to take several seconds to catch up. I've managed to produce a manually-repeatable crash from this by going into and out of the menu screens rapidly with GPU at 100% load and frame gen enabled. The Windows crash report points to the GPU driver not being able to keep up with the requests being made by the game.

In short, when it comes to the stuttering issue, the game settings and display don't matter, what matters is the GPU load percentage when frame gen is on. If you have a Ryzen CPU, try to keep GPU load at or under 90% at all times. Hopefully this annoying issue gets fixed at some point as it's been going on since frame gen came out.

 

[BinaryJay]

Please fix this. Incredibly annoying.

I use 7950X and 4090... FPS tanks for a few seconds almost every time leaving the menus.

 

[DARTHPIBE]

Got the same problem, is there any fix for it?

 

[brentcharles]

I've been testing this extensively the past several days to figure out exactly what causes this. As others have experienced, I have the same stuttering issue in and out of menus with a Ryzen CPU when frame gen is enabled. It has nothing to do with your display. The issue is triggered by how much load is on your GPU when you go into or out of menus and/or cutscenes. If you have frame gen enabled and your GPU is at or very near full load when you go into the map/inventory/settings screens, then you will get severe stuttering when you close those screens and go back into the game. However, if you configure your game settings in such a way where the GPU stays under full load at all times, the stuttering is largely eliminated. Not completely eliminated mind you, but it's mostly gone except for maybe a tiny hiccup coming out of the menu screens here and there.

There seems to be some kind of problem in this game with the way the GPU and Ryzen CPU's keep step with the game engine (and each other) when the GPU is at full load with frame gen enabled. In these instances, it seems like the game engine is massively spiking the load to the GPU temporarily beyond its limits and the GPU has to take several seconds to catch up. I've managed to produce a manually-repeatable crash from this by going into and out of the menu screens rapidly with GPU at 100% load and frame gen enabled. The Windows crash report points to the GPU driver not being able to keep up with the requests being made by the game.

In short, when it comes to the stuttering issue, the game settings and display don't matter, what matters is the GPU load percentage when frame gen is on. If you have a Ryzen CPU, try to keep GPU load at or under 90% at all times. Hopefully this annoying issue gets fixed at some point as it's been going on since frame gen came out.

It seems the only scenario my thread disabling method worked was on a high refresh rate monitor with an uncapped frame rate. Testing on a LG C9 display, I've had good results using the in-fame fps limiter that others here have mentioned, keeping the frame rate below the refresh rate of the display. Like you mentioned, this keeps the GPU around 80%.

I'm curious, does using the in-game fps cap help at all, or does it crash anyway? For what it's worth, I opened a support ticket with CDPR and provided everything they asked for, but never heard back.

 

[Swanky]

Same. I've had this issue with 1.61 and 1.62.
Did open a ticket and their answer was to dial down cascading shadows res and draw distance. Which is a weird suggestion given I run the ingame benchmark with an average of 142 FPS (and a low of 68) with my settings (limited to 72 by the provided ingame limiter).
Even still, changing the aforementioned settings did not change the result - still getting extreme lag when exiting menus. This has also persisted over several cycles of driver updates - board, processor & graphics.

 

[Netrunner2go]

I'm curious, does using the in-game fps cap help at all, or does it crash anyway? For what it's worth, I opened a support ticket with CDPR and provided everything they asked for, but never heard back.

Same. I've had this issue with 1.61 and 1.62.
Did open a ticket and their answer was to dial down cascading shadows res and draw distance. Which is a weird suggestion given I run the ingame benchmark

so they either have no clue what the problem is or the given benchmark is another false/fake information they dropped on the playerbase...

 

[BinaryJay]

The FPS cap helps the menu exit issue for me with my 4090/7950X but causes other problems where the FPS drops to nothing randomly while just running around for what appears to be no reason at all in a similar way but without the menus being involved. That seems to stop happening when I remove the in game FPS cap, but then the menu problem gets worse again.

I started replaying this to prepare for the DLC but there is no way I'm spending any more money on this game when it doesn't work properly.

 

[Swanky]

As far as I remember reading different posts about it's mostly AMD processors with Nvidia GPUs affected, and it read like it has also affected The Witcher 3 after its RTX patch.

 

[don_homas]

It would be interesting to hear if anyone have updated their firmware/bios and got an improvement, like someone here mentioned.

We are, afterall, using the latest of the latest. When I got my 4080/7700x setup, I got some really intense frame drops in games. Apperently, the bios version that I got with my Asus x670 was kind of reeaally bad, it actually made it so that my 4080 didn't use the full power of the PCIe slot, so I got the speed of 4x pcie instead of 16x. Took me a while to figure out, and it's something that I've never experienced before during my 30+ years of PC building.

Maybe this is a similar thing. What happens if everyone just update their firmware? Joy?

edit: i would update to the latest verions myself of curse, but I can't risk fucking with things right now.

 

[Vyrisus7]

It seems the only scenario my thread disabling method worked was on a high refresh rate monitor with an uncapped frame rate. Testing on a LG C9 display, I've had good results using the in-fame fps limiter that others here have mentioned, keeping the frame rate below the refresh rate of the display. Like you mentioned, this keeps the GPU around 80%.

I'm curious, does using the in-game fps cap help at all, or does it crash anyway? For what it's worth, I opened a support ticket with CDPR and provided everything they asked for, but never heard back.

Sorry for the late response. The crashing can happen using either method of FPS capping, but the in-game limiter seems to work a little better than the one in Nvidia control panel. As you know, with frame-gen enabled, setting a value of X using the in-game limiter makes the menus run at that number, but the actual game runs at double whatever number you set. I think this helps further mitigate the stuttering issue in and out of menus since the overall average load on the GPU is less when using the in-game limiter vs Nvidia's. Having the menus running at a lower FPS than the rest of the game gives the GPU more overhead to absorb the temporary spikes when going into and out of the menus.

I do keep my FPS limited under the refresh rate of my monitor as you mentioned. My monitor is 120hz, and so I set an FPS limit of 50 in-game, which caps me at 100 outside of menus. With my particular graphical settings, this keeps my GPU at around 90% utilization or less the vast majority of the time.

Basically, any scenario which causes the GPU to run at or near full capacity causes the stuttering to return, at least for me.

 

[Alfredo_Linguini]

I tried the game last night after a long time, updated to latest 1.62, the problem still persists.