Comment 46 for bug 1763892

Still a massive upgrade for me. Ive been working in Windows for the last 10
years with FPS/Hz ranging from 100-240. Loving ubuntu, but it feels so
choppy right now.

Cheers Daniel.

ons. 13. mar. 2019 kl. 09:50 skrev Daniel van Vugt <
<email address hidden>>:

> A few caveats to remember though:
>
> * In Wayland sessions, if the screen is idle then the mouse cursor will
> slow to 60Hz (https://gitlab.gnome.org/GNOME/mutter/issues/406)
>
> * Removing the 60Hz limit doesn't mean everything will happen at full
> frame rate. There are many reasons why (https://trello.com/c/Q6JYXPPs)
>
> * Firefox seems to have its own 60Hz limit built-in. Chrome/Chromium
> has no such limit.
>
> ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #406
> https://gitlab.gnome.org/GNOME/mutter/issues/406
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1763892
>
> Title:
> 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
>
> Status in Mutter:
> Fix Released
> Status in mutter package in Ubuntu:
> Fix Released
> Status in mutter source package in Bionic:
> In Progress
> Status in mutter source package in Cosmic:
> Fix Released
>
> Bug description:
> [Impact]
>
> Gnome Shell redraws at 60 FPS at most, regardless of the hardware
> refresh rate, and regardless of the current display mode. This is
> particularly annoying for owners of 144Hz/120Hz/240Hz displays.
>
> [Test Case]
>
> 0. Find a monitor or laptop with a high refresh rate (120Hz or more),
> noting NOT to trust gnome-control-center or xrandr because an
> unrelated bug in mutter may cause those to report 120Hz even on 60Hz
> displays. Make sure the advertised hardware specs show the display is
> a high frame rate.
>
> 1. Edit /etc/environment and add:
> CLUTTER_SHOW_FPS=1
>
> 2. Reboot.
>
> 3. Open a terminal window and run:
> journalctl -f | grep FPS
>
> 4. In a new window run 'glmark2' or some other OpenGL benchmark that
> is not frame rate limited (note: glxgears for unrelated reasons IS
> frame rate limited in Wayland sessions, but can be used in Xorg
> sessions).
>
> 5. Verify the terminal window from step 4 shows high FPS values coming
> from the journalctl log that match the hardware spec, and are much
> higher than 60.
>
> [Regression Potential]
>
> Medium to low. This patch has been used upstream and in Ubuntu 19.04
> for some months already without any issues. Although minor syntactical
> changes had to be made to avoid conflicts when backporting it from
> mutter 3.32 to mutter 3.30. If regressions did occur they would be
> visible in the frame rate of the entire screen.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions
>
--
*Med vennlig hilsen / Best regards*

*Simen Henriksen*Digital Marketing Consultant

*www.simenhenriksen.no <http://www.simenhenriksen.no>*