Could you provide details on how you got gamescope working with sway? What is th...

bravetraveler · on Dec 31, 2023

Sure thing! Here's an example command line (from Steam):

    env DXVK_ASYNC=1 SDL_VIDEODRIVER=x11 gamemoderun taskset --cpu-list 0-7,16-23 gamescope -W 3840 -H 2160 -r 160 -o 160 --borderless --fullscreen --rt --steam  -- %command%

Gamescope has become odd with the introduction of '--expose-wayland'.

I think the 'SDL_VIDEODRIVER=x11' part may be key; I didn't need this before, but now I often do. Not every game requires it. It's weird.

It helps if something crashes because "wayland isn't available". Adding '|& tee /tmp/game.log' is useful for debugging.

Pinning (taskset)/gamemode stuff left for context. This example gives a game the cache-rich threads on a 7950X3D.

Beyond '--adaptive-sync'... I believe VRR calls for the feature to be enabled on the output in Sway.

See 'man 5 sway-output', looking for 'adaptive_sync' for more info on that

edit: One last note. I'm on Fedora - the libraries here are so new that Flatpak-based Steam tends to work best.

colordrops · on Jan 3, 2024

Thanks, definitely appreciate this. I tried the line plus many variations without luck. Perhaps my video card is just too old (GTX 1050)

bravetraveler · on Jan 3, 2024

Happy to share - sorry to hear it didn't help.

Nvidia and Wayland are long-troubled friends. The age of the device may or may not contribute...

If you make the command line end with '%command% |& tee /tmp/game.log', you should get some info in '/tmp/game.log'. That may offer some insight

colordrops · on Jan 3, 2024

Great tip, thank you, will try that.