Hi I have this issue as well and know another person who has it as well. All on GNOME. This has been an issue for several driver versions now and is nothing new. Though I think it wasn’t always the case but I am not sure when it started.
dxvk and vkd3d are native
Frame Generation in Arc Raiders stops after 1-3 minutes in-game. Please check out: DLSS / FrameGen stops ingame causing FPS drop, stutter, lag - Arc Raiders
I have this installed and will have to give it a try when I get home from work. It is the remake version which I am assuming is the version you tried correct?
I am playing the RE2 remake, yeah. Specifically with DX11, as the DX12 performance isn’t great as per many discussions
What are your launch parameters?
As far as I can see this is primarily for regressions or other 590-only issues (this is the 590 feedback thread after all, not a general bug report thread), so bugs that been relevant for years aren’t meant to be on that list even if they affect 590 as well.
You didn’t reference a single Nvidia internal bug tracking number in that list.
For each issue you encounter:
- Submit an
nvidia-bug-reportafter reproducing with the 590 driver - Be sure to follow the bug reporting guidelines and attach your bug report in your post.
==== starts here ====
Reporting BUG
Synopsis:
Brief Description:
Steps to Reproduce and Frequency:
System Configuration: [System model][Operating System][Desktop Environment][GPU][Monitors - Model and Refresh Rates]
Linux Bug Report:
Additional details: [Screenshots, Screencapture, console output, logs or any details that can help with debugging]
====ends here ====
Perhaps consider opening a dedicated thread per unique issue and link to it from these general release-series discussion threads.
I am using Proton-CachyOS Native 12-22-25 and it looks like it works on my end. When loading in, the GPU usage was around 45% and had horrible performance. However, after a few minutes of waiting around, the GPU usage went up to 99% and was getting around 200 FPS with maximum settings. Maybe the shaders were processing before and the reason the performance suffered? Have you tried adding VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_wait to see if it will launch that way?
Launch parameters are
PROTON_USE_NTSYNC=1 PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 ENABLE_HDR_WSI=1 mangohud %command%
Hmm, I was able to get the game to launch in native wayland, the problem was that I was using the below software to remove the forced, ugly sharpening filter applied to the game GitHub - praydog/REFramework: Scripting platform, modding framework and VR support for all RE Engine games
I still think it’s an nvidia bug that this fails to work, as it works fine on XWayland.
Even disabling REFramework, it’s still unplayable on Wine Wayland. My FPS is about 9, and it doesn’t improve as you mentioned. I am stuck at that FPS. On XWayland I can easily reach over 100.
Expecting people to resurrect dead driver threads for unsupported drivers makes no sense. Other people still report old issues on new driver version threads anyway.
1 Like
Ive seen it mentioned several times in this this thread but it doesnt seem like it has been added to the bugs to review, but Stalker 2 is almost unplayable on 590. Im getting crashing 5-10 mins after starting, sometimes a little longer, sometimes a little shorter. This was not happening on the prior driver.
What happens is the game will freeze and become unresponsive then after a short period of time, crash to desktop. This is every single launch since the upgrade to 590.
CachyOS using KDE Plasma
GTX 4080
res is 3440x1440 at 144hz
I can get more info later if needed.
@amrits @aplattner can you guys investigate this issue of mine? i used commands
DXVK_ENABLE_NVAPI=1 %command% -use-d3d12
Apparently GTA 5 has DLSS 4 and FSR 3 framegen. FSR 3 is a far better experience and it’s not even close. Sure would be nice if Nvidia fixed their fake frame technology since, you know, it’s advertised on the box as a feature.
I’m playing the legacy GTA5 version instead so I don’t have to deal with garbage AA and DX12 perf. Old version has MSAA and uses DX11 instead, and honestly the ray tracing in the enhanced version is possibly the smallest implementation of RT ever.
1 Like
With 590 installed I am getting a weird issue where my GPU usage drops Drastically in some games causing very bad frame pacing. It doesnt manifest as a stutter but as a slowdown where the game is running in slow motion.
I have tested this issue in all 3 Crysis Remastered games and Horrizon Zero Dawn Remastered. This does not happen on 580 drivers. I have tried this on both KDE and Gnome and with and without VRR enabled as sanity checks. The issue still happens.
nvidia-bug-report.log.gz (564.7 KB)
Legacy won’t let me change settings. Not the point anyway.
1 Like
Whenever I reboot my machine I get to the login screen (which I think is Plymouth, I’m using Omarchy 3.3.3), I enter my password and see the progress bar move, then I loose HDMI output until I disconnect/reconnect the cable again, then everything works as expected. I’m using an HDMI 2.1 cable and monitor (Dell Ultrasharp 52" U5226KW). The problem does not happen when I use a DP cable (which unfortunately is 1.4, so I need to use the HDMI port).
I’m on arch 6.18.3.
I see this in the logs, not sure if related
Jan 11 14:33:41 archbtw kernel: nvidia-modeset: WARNING: GPU:0: HDMI FRL link training failed.
Jan 11 14:33:41 archbtw kernel: input: HD-Audio Generic HDMI/DP,pcm=3 as …
Jan 11 14:33:41 archbtw kernel: input: HDA NVidia HDMI/DP,pcm=9 as …
Jan 11 14:33:49 archbtw kernel: nvidia-modeset: WARNING: GPU:0: HDMI FRL link training failed.
Going to be hard to help you much if you dont provide a bug report log.
1 Like
Sorry, I’m new to the forums, landed here from a google search. I created a bug report on a form I found, not sure how people are generating these tarballs linked in other posts.
EDIT: found the .sh to generate them
nvidia-bug-report.log.gz (833.7 KB)