[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 soredake changed: What|Removed |Added CC|katyaberezy...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 Unamelable changed: What|Removed |Added CC||leonpla...@gmail.com --- Comment #11 from Unamelable --- Switched from Wayland to X11. Same goes for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 gabek...@fastmail.com changed: What|Removed |Added CC||gabek...@fastmail.com --- Comment #10 from gabek...@fastmail.com --- I can add that in my setup, my 165Hz monitor is noticeably not displaying at 165Hz with compositing on (both compared to compositing off and to Windows). Adding MaxFPS=165 under [Compositing] in my ~/.config/kwinrc and restarting did not make any difference that I could detect. However, disabling my second monitor does in fact make things look 165Hz on the main monitor with compositing on. Perhaps this is now just a limitation of compositing over X11? - OpenSUSE TW 20230313 - KDE Plasma 5.27.2 - KDE Frameworks 5.104.0 - Qt 5.15.8 - Kernel 6.2.4-1 - X11 - Monitor 1: 2k resolution over DP @ 165Hz - Monitor 2: 1080p resolution over DP @ 60Hz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 outfrost changed: What|Removed |Added CC||kotlet.bahn+...@gmail.com --- Comment #9 from outfrost --- Confirming this is an issue in 5.23.4, on X11, with kernel 5.15.12-1-MANJARO (amd64), amdgpu, mesa 21.3.2. I've checked, and I do have `MaxFPS=144` under `[Compositing]` in kwinrc. Still, compositing on my 144 Hz monitor is limited to 60 fps. If I disable compositing, then moving windows, scrolling websites in Firefox etc. is smooth again. I used to be able to work around this by setting the compositing backend to XRender. In 5.23, XRender has been removed, so I'm stuck again. My setup is: * 1920x1080 60Hz @ 0,840 * 2560x1440 144Hz @ 1920,400 primary * 1920x1080 60Hz @ 4480,0 rotated left Observation: There is no screen at 0,0 in my setup. In bug #438176, Oto Šťáva mentioned that that has an effect on whether they experience compositing issues. I've tried changing every compositor setting in the kcm, to no avail. The only thing I haven't used is "keep window thumbnails: always". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 --- Comment #8 from Marcus Seyfarth --- It is a HP 25X, only a single display, 144 Hz, DP and Freesync. With KWinFT I got to run Chrome at 144 Hz on X11 eventually (the default display recognition was buggy though, I had to set 144 Hz manually as with the auto settings it also got stuck at 60 Hz), but I didn't get vanilla KWin to run Chrome with 144 Hz yet. I'll keep in mind to try out Wayland, but I am leaning to wait a bit longer to see it mature. Thanks for taking a look anyways, Vlad. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 --- Comment #7 from Vlad Zahorodnii --- (In reply to Marcus Seyfarth from comment #6) > Some good news, as of this week with KDE 5.22.2, Kernel 5.13, Mesa-git and > Chome 92 Beta, I cannot reproduce the reported frame drop issue on 1080p > videos in Youtube with HW decode acceleration via VAAPI anymore, however the > browser is still running at 60 Hz only on my 144 Hz monitor which is set at > 144 Hz and latency set to balanced (default). That's a limitation of X11. If you have several monitors with different refresh rates, it's better to switch to wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 --- Comment #6 from Marcus Seyfarth --- Some good news, as of this week with KDE 5.22.2, Kernel 5.13, Mesa-git and Chome 92 Beta, I cannot reproduce the reported frame drop issue on 1080p videos in Youtube with HW decode acceleration via VAAPI anymore, however the browser is still running at 60 Hz only on my 144 Hz monitor which is set at 144 Hz and latency set to balanced (default). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423230] Compositor only works at 60 FPS on a 144 Hz monitor on X11
https://bugs.kde.org/show_bug.cgi?id=423230 Nate Graham changed: What|Removed |Added Summary|Compositor only works at 60 |Compositor only works at 60 |FPS on a 144 Hz monitor |FPS on a 144 Hz monitor on ||X11 -- You are receiving this mail because: You are watching all bug changes.
