4 ms·
I had to go back to GNOME on Xorg. GNOME on Wayland won't run my 4k display at a consistent 60Hz, which results in horrible issues in games and emulators, as we
by leguminous 5y ago
I had to go back to GNOME on Xorg. GNOME on Wayland won't run my 4k display at a consistent 60Hz, which results in horrible issues in games and emulators, as well as massive numbers of dropped frames in 50/60Hz videos. It is set to run at 60Hz in the display settings, but actually seems to run somewhere in the 50s.
The easiest way to see this is checking the "stats for nerds" while watching a 60fps YouTube video and noting the persistent dropped frames. glxgears also doesn't maintain a consistent framerate.
This doesn't happen in Sway, so I can only assume there is some bug in Mutter that has persisted across several versions of GNOME and Fedora. So Wayland might be great, but my experience with GNOME on it has not been.
- zekica 5y agoThere is no "GNOME on Wayland" - Mutter <b>is</b> the window server - it talks directly to the Direct Render Manager and manages buffers. It's just that most of the GPU interfaces are standardized in mesa and the kernel so there is no need to reinvent the wheel and makes it so Wayland window servers + window managers are feasible to implement, and also why wlroots exists. You could have implemented Mutter on Windows NT using DirectX and such - Microsoft has done such a thing in WSL2.
- leguminous 5y agoI don't know a lot about the graphical stack, window servers, etc. All of my professional work has been on systems with no graphical components. I am trying to understand what you are pointing out. Is it that there is no separate "Wayland service" in the way that there is an Xorg service? That Wayland is just a protocol? Is using Mutter as a Wayland display server not "GNOME on Wayland," even if there is no separate service running?