Arch Linux

agurkmeister

Member

Registered: 2024-01-16

Posts: 8

Xorg desktop running at a locked 60fps

So I have 2 monitors. One is 144hz and the other is 60hz and I'm running Gnome on Xorg.
After connecting my second monitor (60hz) It seems all windows are locked to 60fps. I've had the issue for a while and I just sorta got around it by only using a single monitor.
I just want to know if there is a workaround or if this is just a limitation of Xorg as it works fine on Wayland. I just don't wanna use Wayland as I play a lot of games through proton and I have issues with Wayland in that regard. Performance in native games is also around 15% lower.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,104

Re: Xorg desktop running at a locked 60fps

Limitation of xorg will work fine on Wayland. You can choose which screen to sync to but then either the faster or the slower one will get hit by the relevant artefacts. Your "best" bet is to disable the compositor, though afaik GNOME doesn't have a dedicated button for that. YMMV but I have no issues gaming on Wayland, but that's on Plasma.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,314

Re: Xorg desktop running at a locked 60fps

https://www.phoronix.com/news/GNOME-Bug … rame-Rates

Also
https://gitlab.gnome.org/GNOME/mutter/-/issues/2822
https://gitlab.gnome.org/GNOME/mutter/-/issues/148
https://gitlab.gnome.org/GNOME/mutter/-/issues/1430

Mutter cannot operate non-compositing.

Please post your xorg log.

As for wayland being your saviour: yesnodepends.
The mutter bug only exist on X11 (but that's a gnome problem, not an X11 problem)
Whether you can sync to two outputs at all depends on the available CRTCs/GPU/driver.
In reality, you'll probably sync to one output - typically the low FPS one by default because the faster one is better at hiding the tearline (or is VRR anyway) - there isn't anything wayland could really change about that.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc