https://bugs.kde.org/show_bug.cgi?id=509669
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO CC| |[email protected] Status|REPORTED |NEEDSINFO --- Comment #19 from Zamundaaa <[email protected]> --- Cursor movements have much lower latency than compositing, and we composite on every image update. The dropped frame is afaict really just from that change in latency, and pretty much expected. Making cursor and overlay image updates async (again) will happen at some point, but doing them correctly while also avoiding clients going crazy with cursor surface rendering is not all that trivial. (In reply to fililip from comment #15) > This issue manifests itself in the same manner regardless of whether or not > the hardware cursor is in use (I tried KWIN_FORCE_SW_CURSOR=1 as per my > comment above). The software cursor cannot be affected by the commit you linked. Are you sure you applied it correctly? You can check with drm_info. -- You are receiving this mail because: You are watching all bug changes.
