Does RADV_DEBUG=nohiz help?
It doesn't, but thanks a lot for the suggestion!
Your suggestion made me check the env variables though, and I recognized that
RADV_FORCE_VRS="2x2" is set by default.
So I tried overriding it with
RADV_FORCE_VRS="1x1"
and indeed this fixes the problem!
So, this is actually not a bug in the sense that the game works perfectly fine without changing RADV_FORCE_VRS, right? Note that RADV_FORCE_VRS="1x1" does nothing.
Tracking note: Dropping the Mesa / RADV labels because setting RADV_FORCE_VRS is clearly not a default.
Need to find out then where RADV_FORCE_VRS="2x2" comes from, because I can't remember that I ever used that variable. Will report back when I found it.
I definitely do not set RADV_FORCE_VRS="2x2" myself intentionally, but I can confirm that the problem is on my end. Looks like something pulls this in, and I 'll find found it, but it is clearly no proton issue.
Apologies for having wasted your time, I'm very sorry!
Striking through corresponding lines in the initial bug report, and leave the
"game doesn't exit properly" part.
Nvidia drivers have a strange black overlay bug. Attaching proton log.
Specs here: https://gist.github.com/CygnusTerminal/ec60214e8c9db3670ad98386b9ec4488
steam-978300.log
When starting either a new campaign or a new co-op campaign the game window becomes black, the only way to terminate it is by using killing the process and another thing I noticed is that starting any type of campaign will also close the Steam Launcher I have on the background forcing me to re-launch that as-well.
Hello, I have just downloaded and started the game. The procedure I am about to describe was tested with both Proton Experimental and ProtonGE 9-21.
The game launches properly and without any issue whatsoever up to the main menu, from there I tried selecting either new campaign or new co-op campaign. Regardless of which the result is that the game window remains completely black and the only way to terminate it is for me to spam the ALT+F4 button until the popup that invites me to terminate the process appears.
Since I have two monitors I also noticed that without exceptions each time I start a new campaign (of any of the two types) my Steam Launcher in the background just suddenly closes. Icon disappearing and everything. Restarting Steam meanwhile the game is already in a blackened window state won't make the game work, also according to Steam (at this point) I am not running any game, despite Saints Row being still running on my screen actively (albeit with a black window obviously).
Any help is welcome, I can provide any extra feedback you may need.
Saints Row: The Third Remastered (978300): in-game HDR option never appears
Issue transferred from https://github.com/ValveSoftware/Proton/issues/10240.
@alexugit123 posted on 2026-10-10T21:48:53:
experimental-11.0-20261001 and proton-cachyos-11.0-20261005.The game's native HDR options never appear on Linux. In Options > Display only Brightness is shown. The HDR toggle and HDR Settings page are missing in windowed, borderless and fullscreen modes.
On Windows (same machine, same monitor, dual boot) the HDR rows are present whether or not Windows HDR is enabled. In windowed mode they are greyed out ("HDR: NO"), so they presumably need fullscreen. So the game does offer HDR on Windows; on Linux the rows are not even shown.
Findings from the attached log (gamescope with --hdr-enabled, DXVK debug logging on):
server hdr output enabled: true and hdr formats exposed to client: true.VK_FORMAT_R8G8B8A8_UNORM with VK_COLOR_SPACE_SRGB_NONLINEAR_KHR.VK_FORMAT_A2B10G10R10_UNORM_PACK32 with VK_COLOR_SPACE_HDR10_ST2084_EXT.D3D11DXGIDevice::QueryInterface: Unknown interface query for 0ec870a6-5d7e-4c22-8cfc-5baae07616ed (the same warning appears in the RDR2 log, so it is probably unrelated).nvapi64.dll, which fails to initialize (no NVIDIA GPU) and is unloaded. No AGS library is loaded.NtUserDisplayConfigGetDeviceInfo Unimplemented packet type 11 (4 times). I cannot tell whether these calls come from the game.Earlier run on Proton Experimental with PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 DXVK_HDR=1 (Plasma Wayland session, variables confirmed in the game process environment): winex11.drv was still loaded and the swapchain was B8G8R8A8_UNORM / SRGB_NONLINEAR. Logs available on request.
Other things tried:
HdrEnabled = true in display.ini (persists across launches, no effect). The Windows display.ini is identical.I can't tell whether the cause is in Wine, DXVK or the game, so I am reporting the symptom and the comparison with RDR2.
$HOME/steam-978300.log: the swapchain is SDR even though gamescope exposes HDR formats.Attached: steam-978300.log (compressed, DXVK debug level).
Did some more testing and here's a small comment, might help, might not:
Update: same result on Proton Experimental (experimental-11.0-20261001-x86_64), with the Wayland driver override removed (only winex11.drv loads).
Launch options:
PROTON_LOG=1 PROTON_ENABLE_AMD_AGS=1 ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 gamescope -f -W 2560 -H 1440 -w 2560 -h 1440 -r 240 --hdr-enabled -- %command%
The log shows gamescope exposing HDR to the game:
server hdr output enabled: true
hdr formats exposed to client: true
but the game's swapchain is SDR:
Format: VK_FORMAT_R8G8B8A8_UNORM
Color space: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
RDR2 (1174180) with the same launch options on the same system gets A2B10G10R10_UNORM_PACK32 / HDR10_ST2084. So the game itself isn't requesting an HDR swapchain even when HDR is available. Log attached.
Secondary finding (separate from the above): forcing the Wayland driver on GE-Proton11-7 with Plasma 6.7.5 loads winewayland.drv but logs "Wayland compositor doesn't expose windows_bt2100 image description (HDR may look broken)!". wayland-info shows KWin's wp_color_manager_v1 offering windows_scrgb and st2084_pq but not windows_bt2100.
proton experimentalx3 2026-10ge-proton11-7x2 2026-10DXVK_HDR=1x2 2026-10PROTON_ENABLE_AMD_AGS=1x2 2026-10PROTON_LOG=1x2 2026-10DXVK_LOG_LEVEL=debugx1 2026-10PROTON_ENABLE_HDR=1x1 2026-10PROTON_ENABLE_WAYLAND=1x1 2026-10RADV_FORCE_VRS="2x2"x3 2021-05RADV_FORCE_VRSx2 2021-05RADV_FORCE_VRS="1x1"x2 2021-05RADV_DEBUG=nohizx1 2021-05PROTON_LOG=1 PROTON_ENABLE_AMD_AGS=1 ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 gamescope -f -W 2560 -H 1440 -w 2560 -h 1440 -r 240 --hdr-enabled -- %command%x1 2026-10DXVK_LOG_LEVEL=debug PROTON_LOG=1 PROTON_ENABLE_AMD_AGS=1 ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 gamescope -f -W 2560 -H 1440 -w 2560 -h 1440 -r 240 --hdr-enabled -- %command%x1 2026-10nvapi64.dllx1 2026-10
Compatibility Report
System Information
I confirm:
Symptoms
The game has a strange problem with ambient occlusion. If enabled (no matter on which level) the graphics are overlaid by some grid (see attached screenshot). Performance is not affected and everything else looks correctly.(no proton bug, but some glitch in my env)When changing the light with ambient occlusion enabled, the grid might disappear, but light gets broken/missing in some parts.
Might be amd/mesa related.
The game doesn't exit properly and has to be killswitched.
Find attached