As the title says I can’t disable G-Sync in KDE Wayland on my monitor. Adaptive sync is set to never in KDE display configuration. I can’t enable ULMB2 unless G-Sync mode is off. Is there any way to disable it?
I’m on EndeavourOS (6.6.7 kernel) KDE Wayland using nvidia 545.29.06 driver.
Here’s a screenshot
Not sure if this is a bug so I’m asking here first before posting a bug report.
Yeah, same problem (nvidia 565), it doesn’t matter what is set to disable, it always stays in that mode.
Plus the fps are way lower than on X11. Even if everything is set to disable any sort of vsync.
A similar result that I noticed in X11 in regards to the fps, lower like in wayland, is when the AsyncFlipSecondaries config were turned on. Which accordingly to an article AsyncFlipSecondaries option in allowing for a vblank-synced flip on the primary display while all other displays will try to flip async/immediately and not synchronized to the central vblank.
https://www.phoronix.com/news/X.Org-AsyncFlipSecondaries
That could be related to the gsync/vrr issue on wayland. Since it already has tearing support and any sort of vsync variable are set to disable it.
Another issue that could also be somewhat related to this, is on the new wayland driver on proton. There are mouse issues, but not only, there is also a 60 fps cap, which I read were related to it not being able disable sync to vblank on it.
Just as nvidia are not recognizing commands to change settings, could be that it’s the same for environment variables. Therefore the reason.
KDE/SDDM make it easy to change to X11 on login, so that’s the workaround for now.
It’s still present for me on 565 open driver as well.
The issue was acknowledged and filed internally by nvidia in July, but I haven’t heard from then since then.
https://forums.developer.nvidia.com/t/cant-enable-ulmb-2-on-wayland/277478/4
Perhaps include this thread there. Because it could be that this vblank issue might be affecting other parts. Who knows, it could be mix problem between DE and GPU driver.
At least if the driver recognized the environment variables, it would help on confirm these things.
That fps issue that I mentioned between X11 and Wayland. When X11 are properly configured (which is the additional that it has, where Wayland does not, like the xorg conf and nvidia settings), I have the same result as a very optimized Windows 10/11, in responsiveness and fps.
So, the fact that Wayland are not reaching that when X11 are, there are clearly issues underlying it.
