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%
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.
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
I find it helps with pacing. It also supports VRR with a commandline argument, '--adaptive-sync'.
VRR may need support in the environment to work, I'm not sure. Sway/wlroots does it fine. Presumably KDE does/can too since that's what the Deck uses in 'desktop' mode (otherwise, gamescope).
edit: I see in another post - you have! Agreed on KDE being scattershot. I hope the Gnome people clear things up for you. I wouldn't go so far as to suggest i3/Sway, even though I'm happy with them