Discussion
TIL: When the monitor *scaling* is set to e.g. 125% in #Gnome #Wayland tools like xrandr / XWayland go a little bonkers with the resolution:
> 8192x3456 67.85*+
> 2048x1536 165.00
> 1920x1440 164.93
Not really an issue until… you start a game that needs XWayland (so… Proton) and this goes "fullscreen".
Somewhere in the render pipeline of built-in FSR, oversampling and rescaling of Wayland later things go to hell, the GPU nopes out and the system becomes a stuttering mess.
@bekopharm
Still wonky on Gnome 51; I doubt they’re going to address this. Anything with X in the name is “legacy”.
But I can think of two fixes for the resolution confusion:
1. For Proton games: PROTON_ENABLE_WAYLAND with the GE or CachyOS Proton “remixes”
2. gamescope -w3840 -h2160 (or whatever your monitor’s native resolution is) – that is to say: a virtual monitor that’s like your non-virtual monitor)
This might be obvious to some, but others probably don’t know about it!
@anjune usually I use the game scope hammer too, yes. That's good advice.
Didn't like me yesterday. I guess something broke with the update. Have to check later but had no nerves for this so I just tuned the scaling to 100% again.
@bekopharm
Still wonky on Gnome 51; I doubt they’re going to address this. Anything with X in the name is “legacy”.
But I can think of two fixes for the resolution confusion:
1. For Proton games: PROTON_ENABLE_WAYLAND with the GE or CachyOS Proton “remixes”
2. gamescope -w3840 -h2160 (or whatever your monitor’s native resolution is) – that is to say: a virtual monitor that’s like your non-virtual monitor)
Might be all obvious to some but others probably don’t know about it
tbf that may already be fixed. I upgraded to gnome-shell 50.6 two days ago and stumbled over this yesterday.