HDR on KDE don't work

[pio2398]

I can't run games in HDR mode in any way

I tried gamescope:

DXVK_HDR=1 ENABLE_HDR_WSI=1 gamescope -f --hdr-enabled --hdr-debug-force-output -- %command%
This end with:

CreateSwapchainKHR: Creating swapchain for non-Gamescope swapchain.
Hooking has failed somewhere!
You may have a bad Vulkan layer interfering.
Press OK to try to power through this error, or Cancel to stop.

according to: https://zamundaaa.github.io/wayland/2024/05/11/more-hdr-and-color.html
this should work:
gamescope --hdr-enabled --fullscreen -- %command%
but fail with some message.

I also tried to force wayland in proton but it's start using X11 when I set DISPLAY= %command% or don't start at all with:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Wine\Drivers]
"Graphics"="wayland"

Any idea? I am using NixOS nad rx 7900 xtx.

Gamescope in Heroic seem to work without any problems.

[jathanasiou]

I am seeing the same issue as of the last update on Arch 6.9.2-zen with RADV drivers, as of updates that took place in the last 2-3 days.

[beedell-roke]

#issue-2314930172

@pio2398, krita-artists.org/t/92058/11 probably explains why. To summarise, XWayland appears to be limited to sRGB.

[pio2398]

@RokeJulianLockhart: well, gamescope probably using now wayland by default.
However, something is not working with Vulcan layers as expected.

[beedell-roke]

@pio2398, it doesn't appear to be, per gamescope/issues/543.

[pio2398]

@RokeJulianLockhart running x11 wine on Wayland is supported. Read KDE blog post linked by me.

Running native wine on Wayland without gamescope is also a option but don't work (proton don't have Wayland compiled?). This might not be clear in my first message.

[jathanasiou]

I just tried downgrading gamescope all the way to 3.14.0 and it still gives this error, while being unable to run games in HDR, so I'm thinking it's not actually gamescope that is the problem.

[pio2398]

@jathanasiou: I have similar opinion so I created this issues. However, I don't even have idea how how start debugging.

[jathanasiou]

Through some testing I've done, I keep getting this error:

• with or without the --hdr-enabled flag
• with or without -r frame limit
• both with Proton-GE and with Proton 9.0.1 which is the latest stable on steam right now.

But it does not seem to occur when running say glxgears with gamescope through the terminal. I am genuinely very confused as to what might be causing this.

[pio2398]

I also tried to run Steam in Gamescope from system (Gamescope outside Flatpak, Steam in Flatpak) and got some error.

[LostWarriorr]

Pretty certain this is an upstream gamescope/flatpak/proton issue but I'm really not entirely sure at this point. Someone using bottles wasn't able to use gamescope unless they were using X11 but X11 fails for me as well. Using the deprecated flatpak versions of proton allow the game to run using gamescope. These versions are also built without pressure-vessel.

But then it seems strange that something like Heroic works on your end (idk if it uses a custom proton) and then the user using bottles (Presumed to be using "soda" which is a custom proton) worked in X11 but not Wayland.

I also find a decent handful of posts talking about gamescope/flatpak with no issues on reddit or similar but it could of been back when the flatpak versions of Proton were still supported?

[jathanasiou]

Pretty certain this is an upstream gamescope/flatpak/proton issue but I'm really not entirely sure at this point. Someone using bottles wasn't able to use gamescope unless they were using X11 but X11 fails for me as well. Using the deprecated flatpak versions of proton allow the game to run using gamescope. These versions are also built without pressure-vessel.

@LostWarriorr

I've been getting this error for the last week without using flatpak at all. I just use Arch's official steam package with the steam-runtime.

I tried using different gamescope versions, gamescope git and even older ProtonGE versions (from a time when this was definitely not occurring, but the error remains.

Part of me is wondering if KDE/Plasma is a culprit as well since I haven't tried downgrading my entire DE.

---

EDIT: could these steam logs be relevant to the error we are seeing?

[Gamescope WSI] Failed to connect to gamescope socket: /run/pressure-vessel/gamescope-socket. Bypass layer will be unavailable.
[Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.

[LostWarriorr]

Pretty certain this is an upstream gamescope/flatpak/proton issue but I'm really not entirely sure at this point. Someone using bottles wasn't able to use gamescope unless they were using X11 but X11 fails for me as well. Using the deprecated flatpak versions of proton allow the game to run using gamescope. These versions are also built without pressure-vessel.

@LostWarriorr

I've been getting this error for the last week without using flatpak at all. I just use Arch's official steam package with the steam-runtime.

I tried using different gamescope versions, gamescope git and even older ProtonGE versions (from a time when this was definitely not occurring, but the error remains.

Part of me is wondering if KDE/Plasma is a culprit as well since I haven't tried downgrading my entire DE.

Its weird that you have an issue using native steam and gamescope as I don't think I have seen that yet.

I don't think its just a KDE thing as I have seen one other report from a GNOME user and I think a report on Linux Mint (although I don't remember if it was recent). The only thing all of these have in common (that is if mint was recent) is wayland.

There was someone saying it worked for them under plasma X11 but for me it doesn't.
I don't know if the game @pio2398 launched on heroic was a native game or he had to use proton (not sure if heroic does that or not)

This all boils down to no clear answer as to what is happening outside of it being something to do with Proton/gamescope

It could all be related to this org.freedesktop.Platform.VulkanLayer.gamescope:#6 (if using flatpak) but then it doesn't make since why heroic works unless it is using a custom proton without pressure-vessel

EDIT: could these steam logs be relevant to the error we are seeing?

[Gamescope WSI] Failed to connect to gamescope socket: /run/pressure-vessel/gamescope-socket. Bypass layer will be unavailable.
[Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.

I get the second error in my logs but not the first one.

[jathanasiou]

Still getting this myself. @LostWarriorr are you on an AMD GPU as well? I don't think nvidia users are getting this issue.

EDIT: Will open on https://github.com/ValveSoftware/gamescope as well since I am getting this on on native gamescope too.

[LostWarriorr]

Still getting this myself. @LostWarriorr are you on an AMD GPU as well? I don't think nvidia users are getting this issue.

Yes AMD

Distro: Debian Sid

DE: KDE Wayland

GPU: AMD 6800xt

CPU: 5800x3D

Monitors: 1080p 144hz and 1080p 60hz

Pipewire is being used and not pulseaudio if that is another factor

[jathanasiou]

We have a near identical system then. I'm on arch myself and single 144hz monitor but same DE, CPU/GPU and pipewire as well.