The aim of the color management extension is to allow clients to know the color properties of outputs, and to tell the compositor about the color properties of...
I’m currently able to play BG3 in HDR (on Nvidia!) using gamescope. Once the Wayland stuff makes it to Bazzite, how would that change my Steam launch parameters? No more gamescope?
So the protocol is a blueprint of how to implement it. Kwin, Mutter and Gamescope are the ones implementing the code. Gamescope/Kwin already had HDR. What will probably happen now is slightly better accuracy and the removal of flags (your parameters) once they apply the new constraints.
I’m currently able to play BG3 in HDR (on Nvidia!) using gamescope. Once the Wayland stuff makes it to Bazzite, how would that change my Steam launch parameters? No more gamescope?
ENABLE_HDR_WSI=1 gamescope -f -w 3840 -h 2160 --hdr-enabled --hdr-debug-force-output --steam -- env ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 DISABLE_HDR_WSI=1 %command% --skip-launcherI’m on AMD but I already play in HDR without gamescope with Proton-Tkg (Wine master).
For games I then only have to set
DISPLAY= ENABLE_HDR_WSI=1 %command%.The HDR layer is here: https://github.com/Zamundaaa/VK_hdr_layer
It should not be needed anymore pretty soon.
Sweet tyvm for the info
So the protocol is a blueprint of how to implement it. Kwin, Mutter and Gamescope are the ones implementing the code. Gamescope/Kwin already had HDR. What will probably happen now is slightly better accuracy and the removal of flags (your parameters) once they apply the new constraints.
Far out tyvm