6e6a3834 causes frame callback-driven game to run at half framerate
On my ThinkPad T495s, 6e6a3834 makes Quaver run at 60 FPS instead of 120 FPS when on a 120 Hz monitor. The game uses Wayland and redraws upon receiving a frame callback. When set to Unlimited FPS, it manages above 120 FPS just fine. Also, running OBS in the background (just capturing the screen, not recording) makes the game run at 120 FPS (although not 100% consistently). Running the Steam window in the background (i.e. behind the game) also sometimes makes it run at 120 FPS. Forcing GPU clock to high with gamemode's sudo /usr/libexec/gpuclockctl 1 set high
seems to make the game run at 120 FPS too.
This might be working as intended and an unfortunate interaction between the readiness and the GPU frequency scaling that makes the game render just slow enough to not make it for readiness, but I'm not sure. Setting max render time constant to 999999999 does not help. cc @daenzer
Fedora 38 Wayland