Is there any plan to fix this issue which is still present in the 580.76.05 driver?
I tested many scenarios again.
First test I recorded on video. Quite long, so summary, time marks and video under spoiler. Sorry for quality, 12-min long video and 100Mib so…
First test
Full_video
First game start ( xwayland ):
1: Verified Warhammer 3 client on steam. Launched without any env variables. Graphics settings: Ultra + Unlimited Video memory. You can see my settings on 1:04sec.
2: Launched battle benchmark. Apparently, the type of benchmark also matters.
3: Benchmark stuck at 23 sec.
Second launch. 02:40, no env var ( xwayland ):
1: Same Graphics settings as in first launch.
2: Launched mirror of madness benchmark. 03:12sec.
3: Finished succesfully at 04m 35sec.
4: Launched battle benchmark at 04:45. Finished succesfully at 06:48.
Third game start in 07.00.
cmd line: env OBS_VKCAPTURE=1 PROTON_USE_WOW64=1 PROTON_ENABLE_WAYLAND=1 mangohud %command%
( wayland drv ).
1: Same Graphics settings as above.
2: Launched battle benchmark.
3: Finished succesfully. Time stop 10:06
Last try in 11.00..
cmd line: mangohud %command%
( xwayland )
1: Same Graphics settings.
2: Battle benchmark launched at 11:14.
3: Freezed again on 00:17sec of benchmark.
Summary from first test: issue happening only on specific benchmark and it needs to be launched first.
After that, I tested on other graphical settings.
env var: mangohud %command%
(xwayland).
- Options → Main → Quality → set to Low → “battle benchmark” → finished successfully.
After successful benchmark → Options → Main → Quality → set “Ultra” → “battle benchmark” finished successfully again on same session. - Restarted the game, then: Options → Main → Quality → “Ultra Preset” ( was saved from previous launch ) → battle benchmark → game freezes. Closing the game.
- Restarted the game. Options → Main → Quality → set to High → "battle benchmark → finished successfully, then → Options → Main → Quality → set “Ultra” → "same benchmark → finished again.
- Restarted the game. Options → Main → Quality → verified that it’s “Ultra” → "same benchmark → freeze.
So, graphics settings, type of benchmark and order of “loading” do impact on reproducibility.. somehow.
Update: NTSYNC also required to reproduce this issue.
No game mods.
No scx/other schedulers were used during this test. Only Linux baseline one.
Kernel 6.16.0. Driver Version: 580.65.06
Still the same problems with the most recent stable which was promoted stable: Many games do not run and complain about missing GPU features, Vulkan layers not working (obs-vkcapture, Steam overlay, mangohud)…
In my case, yes, there was a difference. nvidia-uninstall first, then I checked if there are any nvidia packages present from my distribution as well, including cuda packages, removed them all, rebooted and .run took care of the rest. No current problems with any GTK4 programs on my machine.
Is this bug where apps like Nautilus in Gnome freeze and if you force close the app the entire Gnome session dies? I just upgraded to the new 580 production release and I am seeing this. Downgrading to version 575.64.03 until this bug is fixed.
Fedora 42, Gnome 48, 1660 Ti
I can’t speak to the Gnome session behavior.
Nautilus is a GTK4 app, and this regression affects all GTK4 apps as of 580 series.
Oh. Some envvar still set from beta?
I did send you a bug report via PM? Again, you can go days without it happening.
Settings: 4k low with DLSS Ultra Performance. DX11 or DX12 doesn’t matter but since shaders over 1GB are being deleted, DX12 would be best unless you want to deal with shader stutter.
Again, as you could see from the bug report sent to you, I’m using a 4060. HDMI / DisplayPort doesn’t matter, although the driver seems to ouput more errors into dmesg using HDMI. DisplayPort just gets something about “rfkill input handler” usually.
Something that I’ve noticed but i’m not sure is related is that in-game performance seems to get worse with system uptime. In other words, FPS and frame times will be far better after a fresh reboot than if you were to play on a system with a few weeks of uptime. Again, no idea if it’s even related. It could be a Gnome issue.
BTW, have you done a bug report on having to unplug and replug display cables in order to get display when the computer idles with the screen off?
Edit: while you’re at it, could you finally fix frame gen and Reflex? They’ve been broken in The Finals since both were added.
Hello, Can you please share nvidia-bug-report to proceed on this investigation?
Can you please share nvidia-bug report to investigate this further?
With the 580 driver? Open or proprietary?
Thank you for sharing detailed repro information, I will try locally and update.
Is that a laptop version of it or the desktop version?
Are you sure you are using Wayland? Did your graphics system revert to Xorg maybe?
The game seems to crash often when the display goes to sleep.
Acknowledged.
Could you help to share more information on below reported issues.
5454535 No display when the system wakes from idle with the display powered off
Please share fresh bug report after enabling Debug mode in Xorg.conf file as below
Option "Debug" "true"
in theDevice
section.
5454512 Random black screens when playing extremely demanding games(Metro EE, The Finals) with driver 575.51.02
We will continue to try repro in house, but since this issue is intermittent, please collect bug report with debug mode as soon as you see black screen.
Regarding Frame gen and Reflex issue, are you seeing these two options greyed out or features appear to have no effect after enabling it.
Will try.
Regarding Frame gen and Reflex issue, are you seeing these two options greyed out or features appear to have no effect after enabling it.
They exist but actually enabling them seems to A) require a restart and B) cause massive latency issues with zero FPS increase. It’s like playing with VSync enabled almost but VSync is off.
I’ve played The Finals under Windows and used frame gen and it does work. This is a Linux issue and affects multiple games. I’ve yet to play anything that has working frame gen under Linux.
Indeed, you need to restart the game. But as far as I know there are issues with it still.
There is an ugly workaround for it but it isn’t the real fix. Besides, it’s most likely outdated now and might need a rebase. vkd3d: Add busy-wait path for shared semaphores on Nvidia. by doitsujin · Pull Request #2317 · HansKristian-Work/vkd3d-proton · GitHub