With GLFW 3.4 coming to my distributions packages recently, I decided to take a look at one of my older Raylib projects to see how it was impacted by the fractional scaling changes. When opening it however, I was greeted by my application running at thousands of FPS. I decided to dig a little deeper and set up the rotating triangle example to make sure that the issue wasn’t on my side. Even then, logging out the FPS, I saw figures in the thousands (even after calling glfw.SwapInterval(1)). I compared this to my SDL gpu application and saw that it properly vsyncs but does use Vulkan under the hood as opposed to OpenGL. Interestingly enough, applications running through xWayland do work properly so this issue is seemingly limited to Wayland applications. Would anyone happen to know if this issue is due to some machine configuration on my end or driver issues on Nvidia’s end?
Sadly OpenGL swap interval control is very dependent on driver/OS/window systems etc. and some do not honour the swap interval request. Tearing control for Wayland is relatively new and may not be properly supported on your system.
Ah, thanks for letting me know. I’ll take a look at what Kitty does then and check, there’s probably something I can do to make resizing smoother and avoid even needing sync