Hello
I have noticed that when using the wine_wayland driver, the frame rate gets locked to the refresh rate of my main monitor.
This issue was also happening on cs2, when using SDL_VIDEO_DRIVER=wayland. This seems to have been fixed, though.
The frame rate isn’t locked on Hyprland, which I am testing right now. Hence why I am writing here, instead of the nvidia forums.
Tearing is enabled in system settings and also as a window rule for the game in question.
The game with which this happens is osu!, using the winello installation script. Some months ago I tested it with other games and it happened there, too, but I can’t recall which game it was, sorry.
For reproducing this issue, after installation, run the game with DISPLAY= osu-wine. Set unlimited fps inside the game options and let a song/map run, with the Auto mod.
While this is aside from the bug I am experiencing, I also noticed that the performance on this game is quite a bit lower than on Hyprland (0.24ms vs 0.32ms while spectating, or 0.4ms vs 0.6ms when moving my 4khz mouse). I can’t think of why, I don’t have anything installed for power management or scheduling on both.
Another thing. This is happening with both, but maybe someone knows a solution, in wine_wayland, it detects the wrong refresh rate and uses 144 Hz from the secondary monitor, instead of 240 Hz.
P.S.: While I am still going through the trouble of setting up Hyprland, I can appreciate KDE and all the effort going in there, even more. Even most basic features (to me) are just missing or exist only as third party tools, which might be abandoned.
I am using an up to date arch, with nvidia-open. If there is anything missing you might need to know, just tell me and I’ll provide it.