Issues with the WSI layer, hdr, and steam overlay / input failing to hook #1225
Comments
|
You can't do HDR on X11/XWayland. You need to set WAYLAND_DISPLAY |
|
Sorry, you are launching the game, so it needs GAMESCOPE_WAYLAND_DISPLAY, not WAYLAND_DISPLAY. It also needs ENABLE_GAMESCOPE_WSI=1 I don't get why this would change anything about overlay though. Does it work in this way? |
|
I believe do I need to run gamescope with sence the big Wayland update, steam overlay doesn't attach to gamescope when launching the normal way, afik it is an issue with the overlay not gamescope. when the game connects to gamescope via I will be at my box to test in a few hours. |
|
You only need GAMESCOPE_WAYLAND_DISPLAY, no extra flag |
|
ok so runing a game with gamescope run from a terminal with the launch options running a game with the same setup and the lauch options the same applies when gamescope is launched with From what I can tell I assume this is expected as proton/wine does not support native Wayland so Wayland environment variables are ignored. Your comments @Joshua-Ashton lead me to assume there are things that gamescope does when launching an application directly via Assuming that is correct and intentional than this issue can be closed as won't fix. Out of curiosity, and again assuming the above is true, how difficult would this be: |
|
I tried removing the code in |
|
I can sucessfuly run GoW with HDR on Plasma 6 using Gamescope, but no way to get the overlay working makes it unusable, because no proper controller mapping (my desktop layout persists even though game is running). What's positive, is that it doesn't break VRR like it does in embedded mode (which I only forced to run with amd-color patched kernel and gamescope with patches to use it, but is highly unstable and part of games have broken colors no matter if SDR or HDR). Related issue: #1006 A side note, it would be cool to have the ability to run Gamescope with all the overlay and input handled inside like it is done in SteamOS embedded session. That would solve both this particular problem, but also overlay being broken for Flatpak apps flatpak/flatpak#1756 (which straight-up cancels Steam Input for all Flatpak launchers, emulators, EmuDeck, all that fun stuff). But of course I don't know how the internals work and if it's even feasible. |
VoidAndCaffeine
changed the title
VoidAndCaffeine
changed the title
I duplicated what I assume you did @Joshua-Ashton, I removed the I assume as a side note for some reason running cyberpunk with |
|
Here is something interesting installing the git master with my pr and then lauching results in a working overlay, but as soon as I run EDIT: |
VoidAndCaffeine
changed the title
I run gamescope more or less a a daemon to get around #835. rather than directly launching games with
gamescope (vars) -- %command%, I use gamemode to automatically start gamescope and then passDISPLAY=:2 DXVK_HDR=1to the game. I decided i was going to give plasma6 + hdr a go but I found that my (admittedly niche) setup is broken. Launching the normal way,gamescope (vars) -- %command%, properly initiates hdr.To reproduce: (my example will be cyberpunk as I don't own ori)
pkill gamescopegamescope -e -f -h 1440 -r 165 --hdr-enabledspecifically the git master version (no others work on my system)DISPLAY=:2 DXVK_HDR=1 %command% --launcher-skiphere is the output from the above example:
and here is the output launching the normal way:
The text was updated successfully, but these errors were encountered: