in the pervious release thread I had mentioned how certain “features” (mainly FSR, frame rate limiting, and steam overlay) were not working using the latest gamescope versions under wayland.
I’ve dusted off a couple upstream posts I was following about these issues, and found some workarounds that work together to fully address all my issues.
- per Games open in an invisible window since 3.14.3 when using FSR · Issue #1237 · ValveSoftware/gamescope · GitHub, adding
--backend sdlgets FSR working once again - per Gamescope breaks Steam Overlay · Issue #835 · ValveSoftware/gamescope · GitHub, adding
SDL_VIDEODRIVER=x11gets the game overlay working
My original launcher settings that to me are the “base, non-workaround” options that stopped working after gamescope 3.14.2:
DRI_PRIME=1 gamescope -r 60 -o 30 -h 720 -H 1360 -F fsr %command%
My initial modified launcher settings with gamescope-plus 3.14.24 that only resolved game overlay and frame limit (not FSR)
DRI_PRIME=1 DXVK_FRAME_RATE=30 gamescope -h 720 -H 1360 %command%
My current launcher settings started with the original baseline, and then added the two newly discovered workarounds… resolving the FSR, frame rate limit, and game overlay issues
DRI_PRIME=1 SDL_VIDEODRIVER=x11 gamescope -r 60 -o 30 -h 720 -H 1360 --backend sdl -F fsr %command%
The bonus for me using these settings was that there was one game that always failed to launch with FSR… but using this combination even it too happily runs.
Looking forward to removing these workarounds down the road, but for now this works for me, and maybe helps you.