<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - XWayland refresh rate locked to 60 Hz" href="https://bugs.freedesktop.org/show_bug.cgi?id=103282#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - XWayland refresh rate locked to 60 Hz" href="https://bugs.freedesktop.org/show_bug.cgi?id=103282">bug 103282</a> from <a class="email" href="mailto:stevengruspier@gmail.com" title="stevengruspier@gmail.com">stevengruspier@gmail.com</a> <pre>(In reply to grmat from <a href="show_bug.cgi?id=103282#c0">comment #0</a>) > Looks like xwayland doesn't report the correct refresh rate/vsync timings(?) > to clients. I've been working around compositor implementation flaws by > using a custom EDID file. Now the compositors I've tried (Mutter, KWin, > Sway) run at the correct 144 Hz, however xwayland clients still only refresh > at 60 Hz. > > This is bad because if using a monitor with no even multiple of 60 Hz (like > 72, 75, or 144 Hz monitors), there is stutter instead of smooth playback. > And I guess many common apps will be running through xwayland for quite some > time. > > I can also confirm the problem running glxgears, which runs v-synced and > prints 60 FPS to the console. You might be interested in this one Bug Report for wanting to add different refresh rates to mutter: <a href="https://bugzilla.gnome.org/show_bug.cgi?id=781296">https://bugzilla.gnome.org/show_bug.cgi?id=781296</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>