https://bugs.kde.org/show_bug.cgi?id=395632
--- Comment #40 from Benjamin Xiao <ben.r.x...@gmail.com> --- Still running into this issue on Plasma 5.14.5 and Frameworks 5.55. Has there been any progress on this? It's really ruining the out of the box KDE experience on gaming displays. Been doing some more research into this and there seems to be multiple issues at work here. 1. First is the KWIN_TRIPLE_BUFFER issue as noted in comment 38. Having it not set or set to a value of 1 causes "Painting blocks for vertical retrace" to be no, which apparently causes Kwin to ignore the active refresh rate of the monitor. 2. Second, I just discovered today that Kwin doesn't seem to be updating its refresh rate when I change it via xrandr or System Settings. The monitor itself runs at the new refresh rate but "qdbus org.kde.KWin /KWin supportInformation" continues to return whatever refresh rate was active at the time Kwin is started. So for example, if I boot up my computer and my refresh rate was 60 at the time, and then I go into System Settings and change it to 144, "qdbus org.kde.KWin /KWin supportInformation" still gives me 60Hz, even though the monitor is at 144. It doesn't refresh until I do a "kwin_x11 --replace". This isn't just the information not changing. It appears that certain apps are actually getting told the old refresh rate instead of the new one. Apps like Chrome will run at the old refresh rate until I "kwin_x11 --replace". You can certainly see how this causes poor frame timing and frame jitter. My monitor is running at 144, but Chrome and Kwin are running at 60. To work around these issues: 1. I set KWIN_TRIPLE_BUFFER=0 so that Kwin doesn't just ignore the refresh rate. 2. I've also added "xrandr --output DisplayPort-0 --mode 2560x1440 --rate 144" to /usr/share/sddm/scripts/Xsetup so that SDDM runs at 144Hz instead of 60Hz. That way, when Kwin starts, it will run at 144hz right off the bat. If I don't do this, Kwin will be stuck at 60hz according to "qdbus org.kde.KWin /KWin supportInformation". Chrome and other apps will also be running at 60hz until I restart Kwin. I get pretty good performance with those two steps but honestly, its a pretty hacky workaround. Kwin should be respecting what I set in System Settings and I shouldn't have to disable triple buffering. -- You are receiving this mail because: You are watching all bug changes.
