Yes, but it’s a hack, when it’s properly implemented you won’t need gamescope and it won’t have to be fullscreen as far as i’m aware, although i could be wrong about the fullscreen thing.
Ah, I guess the HDR support in Wayland is still exposed via an “experimental” interface. But it looks like a handful of Wayland compositors support it, including wlroots which a bunch of smaller compositors are based off of.
It’ll be more performant, lower latency, have proper HDR support (current method is a hack), scale properly based on your displays, and probably be generally less buggy long-term (probably more buggy when it first gets added since it’s a pretty fundamental change).
You’re currently using a compatibility layer called xwayland to run it, which adds a ton of cruft.
Could you elaborate on the advantages, I’m using wayland and steam for games, no issues so far.
HDR support
Doesn’t valve already use gamescope (Wayland compositor) with HDR support? And KDE?
Yes, but it’s a hack, when it’s properly implemented you won’t need gamescope and it won’t have to be fullscreen as far as i’m aware, although i could be wrong about the fullscreen thing.
Ah, I guess the HDR support in Wayland is still exposed via an “experimental” interface. But it looks like a handful of Wayland compositors support it, including wlroots which a bunch of smaller compositors are based off of.
Even with support from the compositor, you need support for it in every part of the graphics pipeline.
Currently you can either use Wine with Wayland + Vulkan layers + KDE or gamescope + KDE (or gamescope directly in TTY).
wlroots doesn’t support HDR.
Ooo, the MR it links to is 10mo old and still open.
And the most recent comment indicates that it’s not currently being worked on by someone.
hmmmm sugar pie https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4962
It’ll be more performant, lower latency, have proper HDR support (current method is a hack), scale properly based on your displays, and probably be generally less buggy long-term (probably more buggy when it first gets added since it’s a pretty fundamental change).
You’re currently using a compatibility layer called xwayland to run it, which adds a ton of cruft.
Fractional scaling
xwayland*