-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interacting with KDE desktop elements or changing wallpaper settings on high refresh rate monitors causes shader to speed up. #43
Comments
Oh wow that's super strange. Thanks for sharing. I have a 120hz monitor, however so far I've only been working from a VM so I hadn't noticed this. I'll see what I can do |
What if you try changing
And
Does this make sense? I know nothing about shaders Edit: Actually it should be 4 and not 8 (1/240) |
Good thinking. Could you please test it? |
I'm sorry, I don't really know how to find those files on my install. I'm still very much a Linux noob lol If you could help point me in the right direction, I'd greatly appreciate it! |
It's in |
In a folder of your choice:
|
Alright, I'm finally getting around to this, sorry for the wait there. |
When using this wallpaper on a monitor with a refresh rate above 60 Hz, interacting with desktop components of KDE Plasma 5 (not including applications like Dolphin) causes the shader to speed up very briefly, and it's very distracting.
https://github.com/y4my4my4m/kde-shader-wallpaper/assets/33814663/a34f79b9-2235-44fe-b5bf-1e5e37e5e7c9
In this case, I'm currently using a monitor with a refresh rate of 240 Hz but the problem is still visible in a 60 FPS recording.
A similar issue occurs when opening the wallpaper settings to adjust the shader, this time speeding up consistently for the entire time the menu is open.
https://github.com/y4my4my4m/kde-shader-wallpaper/assets/33814663/6f8d570a-74e1-45c9-8400-90b1099e8a0c
Changing the refresh rate to 60 Hz does resolve this problem, but I would rather not have to do that.
The text was updated successfully, but these errors were encountered: