Autumn
> Does #623 fix this issue or is it unrelated? It is unrelated.
This protocol https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/163 This xwayland PR https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/976 and this Gamescope PR https://github.com/Plagman/gamescope/tree/new-surface-association Should properly solve the problem.
I would just wait, there are a lot of still moving parts.
Game also has an issue where in gamescope sometimes it never repaints unlss the mouse moves. Surprisingly, it isn't related to `hasRepaint`, or what we consider the focus to be...
That version is too old, it's missing the NVIDIA fixes.
Try disabling mangohud?
This is just because the app thinks it's always focused when run under gamescope, which is intentional. Gamescope is mainly made for games, which really don't like not being focused....
Yes, I plan to experiment with HDR support soon. I started the work on the vkd3d side recently: https://github.com/HansKristian-Work/vkd3d-proton/pull/1227
This is not needed, as it is implemented by the Gamescope WSI layer.
The Gamescope WSI layer implements `VK_EXT_hdr_metadata` which can be used by MPV. MPV does work with it.