https://bugs.kde.org/show_bug.cgi?id=395632
--- Comment #29 from Benjamin Xiao <ben.r.x...@gmail.com> --- (In reply to Martin Flöser from comment #28) > If KWin correctly detects the refresh rate the maxfps setting has no > influence at all. It's the same code. If I set MaxFPS=144, there's definitely a difference. I can feel it in webpage scrolling and when moving windows around. I wish there was another way for me to prove it to you besides the ShowFPS plugin. The difference is very visible. Also doesn't the fact that ShowFPS shows different values prove that there's something going on? Yes I get that it isn't accurate, but the MaxFPS setting is doing something because when I have it set to 144, Show FPS effect gives me 100. If I don't have it set, it gives me 75. If the code there is exactly the same, there must be a different section of the code that's influencing this. If you don't think that Show FPS is accurate, could you please let me know of an alternative way to prove it? This is NOT placebo. Many people on Reddit are also experiencing this same issue and have had to use MaxFPS=144. You've already posted several times there saying that it isn't a valid solution and that we should file bug reports, but currently that remains the only valid solution to fully taking advantage of our high refresh rate monitors. -- You are receiving this mail because: You are watching all bug changes.
