Closed sfjuocekr closed 1 month ago
From the application's side, I don't see much we could do here, since it seems to be the windowing system/Wayland performing the actual throttling, which is well outside the application's control.
One reason that might play into it and possibly also causes Qt to misbehave on Wayland is that Wayland solely uses EGL for rendering, while projectM and many other applications still use the classic GLX interface. Wayland might have some EGL-to-GLX bridge, but could possibly decide to throttle applications using GLX which aren't in focus to save some resources.
There might be a setting to control this, but since I've not migrated to Wayland for these compatibility reasons yet, I've not dug deeply into it.
I'll update this bug report if I can find something. Anyone else is also invited to give some advice here, e.g. users having more experience with Wayland.
This issue has some information: https://github.com/libsdl-org/SDL/pull/9345
I closed this because it seems to be an oversight in the Wayland protocol that is pending a fix.
And I want to add that anyone that runs into this issue can circumvent it by checking this box:
Please confirm the following points:
Affected Application
projectM Standalone SDL2 Frontend (includes the Steam app)
Affected Version
4.1.0
Operating System
Linux (Desktop)
Additional Application Details
Using from AUR: projectm-sdl2-git
Type of Defect
Graphical issue (rendering glitches, black screen, heavy flickering)
Log Output