460.32.03 performance regression in Red Dead Redemption 2 (Steam Play)

Hello,

I hope this is the right place to start this thread since I’m quite sure this issue is related to the driver.

Since I upgraded my Nvidia driver to version 460, I noticed significant performance regression in Red Dead Redemption 2. I am experiencing constant short framerate drops that happens every couple of seconds. This behavior is consistent and is not affected by the in-game surroundings. Once or twice the framerate dropped to stable level around 40 fps and stayed this way for another 5-10 seconds. Other than that the game runs perfectly smooth.

This sort of behavior wasn’t present with the 455 driver I used before. In fact, back when it was the stable version, I decided to try the (then beta) 460 driver and this stuttering was already present. I was just hoping that it would be resolved before 460 was considered stable.

I am running the game using Steam Play (Proton Experimental) with Vulkan as the rendering API in 2560x1440. I recorded the described behavior with MangoHUD. The log can be viewed here: FlightlessMango

My system information:

System:    Host: jasus Kernel: 5.10.7-3-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.20.5 
           Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME Z370-P v: Rev X.0x serial: <superuser required> 
           UEFI: American Megatrends v: 0601 date: 11/13/2017 
CPU:       Info: 6-Core model: Intel Core i7-8700K bits: 64 type: MT MCP L2 cache: 12 MiB 
           Speed: 800 MHz min/max: 800/4700 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 
           6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 
Graphics:  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] driver: nvidia v: 460.32.03 
           Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia resolution: 1: 2560x1440~144Hz 
           2: 2560x1440~144Hz 
           OpenGL: renderer: GeForce RTX 2070 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 460.32.03

I will happily provide any further information you might find useful.

Thank you

Benchmark results with the 455 driver (2020-12-30):Benchmark-20-12-30-02-44-55.txt (2.0 KB)
Benchmark results with the current driver (2021-01-26): Benchmark-21-01-26-15-35-47.txt (2.0 KB)

EDIT: I also noticed that GPU usage drops from 95+% down to 60-80% during these slowdowns.

EDIT 2: I uploaded more data series (different drivers, kernels and launch options). The performance difference between 460.xx and 455.45 is very clearly visible now: FlightlessMango (sorry for not keeping the logs equal length)

Maybe some problem with the new shader cache? Please try to delete it so it gets created in the new location:
https://download.nvidia.com/XFree86/Linux-x86_64/460.39/README/openglenvvariables.html

Unfortunately that’s not it. I removed both old and new cache directories, but the problem persists.

There are a similar problem with rFactor 2, and yes, I deleted all caches, but the problem persists

1 Like

Hello, good afternoon

I have a problem with the performance of Red Dead Redemption 2 PC since I launch DLSS for RTX, the GTX, the one I have, the GTX 1060 6GB has FPS blocking. The performance test tells me that Maximo is 70 FPS 1920x1080 and the red dead redemption 2 pc is like blocking the fps and performance I would like it to improve the performance 100% both the series 10 and 16 but it is a block that we are going to be unplayable and no fair please improve seriously

If we pay for a product it is for you to talk to the developers red dead redemption 2 pc if we pay for a product that product has to improve performance 100% nobody knows if the graphics will be capable the next time I play, send you screenshots

Specifications of my Computer: Intel Core i7-11700K, Kingston 3200Mhz RAM Memories 1x32GB Kit, Asus Strix Rog GTX 1060 6GB, RM750 80 Plus Gold Power Supply, NVMe 1TB Kingston KC2500, 2TB HDD Seagate and lastly corsair A500 air cooling.

I know that the game is blocking my performance FPS if I put it ultra, shoot 20 FPS before I shot 35 FPS but of course the graphics card tells me maximum FPS reaches 70 FPS 1920x1080, please improve performance 100% please thank you

Best regards

David

I don’t think that addelucas1977’s problem is related to the exact issue I was describing, but I finally managed to fix my problem.

I took a quite long break with RDR2 - I just recently returned to it. Unfortunately, I noticed that the driver version 495.44 also exhibits the performance drops, though it seemed that weren’t so common and significant. A couple of days ago I learned about Feral Gamemode and decided to try it out on RDR2. To my surprise, the performance issues have disappeared completely since I added gamemoderun to my Steam launch command. I wish I had came up with that earlier.

Proton version: 6.21-GE-2
Steam launch command: __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __GL_SHADER_DISK_CACHE_SIZE=100000000000 __GL_YIELD="NOTHING" __GL_ALLOW_UNOFFICIAL_PROTOCOL=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 WINEDLLOVERRIDES=dxgi=n,b PULSE_LATENCY_MSEC=60 gamemoderun mangohud %command% -adapter 1 -vulkan -USEALLAVAILABLECORES -cpuLoadRebalancing -ignorepipelinecache

Please note that my launch command involves all sorts of attempts to eliminate the infamous ERR_GFX_STATE crash. Frankly, at this point this is just some sort of shotgun debugging… Anyway, with these settings the game still crashes sometimes, but not as often as it used to without them (or so it would seem). I’m quite confident that gamemoderun was the solution to the performance issues, though.

I don’t know if anybody has been experiencing any similar problems, but if so, I hope this information is useful.

Does setting “prefer maximum performance” in nvidia-settings have the same effect? Would point to some clocking problem, maybe during transition to boost clocks.

No, that doesn’t seem to be changing anything. I think I already tried that last year, but tried again just to be sure. Do you want me to gather some mangohud/benchmark logs with different configurations?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.