https://bugs.kde.org/show_bug.cgi?id=448918
--- Comment #3 from Alessandro Astone <ales.ast...@gmail.com> --- (In reply to Zamundaaa from comment #2) > KWin does compositing in a single thread. If two outputs need compositing at > the same time and latency is too low, this causes stutter because it can't > manage to finish compositing both in time. > > With NVidia we don't get proper timestamps, which causes the latency to be > lower than desired, see bug 409040. Until that is fixed you can work around > this problem by setting the latency option in the compositing KCM to "prefer > smoother animations". > > *** This bug has been marked as a duplicate of bug 409040 *** I'm not sure this is the same bug. I've tried both smoother/smoothest animations and your open pull request @ https://invent.kde.org/plasma/kwin/-/merge_requests/1861 with the same result. Some terminal output of the reported example: $ __GL_SYNC_TO_VBLANK=0 glxgears -fullscreen # I launch glxgears on my 60hz monitor 311 frames in 5.0 seconds = 62.187 FPS # at the beginning fps is a bit higher than 60, maybe due to Konsole on the other monitor? 300 frames in 5.0 seconds = 59.936 FPS 302 frames in 5.0 seconds = 60.325 FPS # some fluctuation? 300 frames in 5.0 seconds = 59.930 FPS 300 frames in 5.0 seconds = 59.938 FPS 300 frames in 5.0 seconds = 59.937 FPS 617 frames in 5.0 seconds = 123.314 FPS # at this point i start playing a video on firefox 830 frames in 5.0 seconds = 165.977 FPS 871 frames in 5.0 seconds = 174.174 FPS 897 frames in 5.0 seconds = 179.370 FPS 897 frames in 5.0 seconds = 179.367 FPS 905 frames in 5.0 seconds = 180.971 FPS 895 frames in 5.0 seconds = 178.969 FPS 897 frames in 5.0 seconds = 179.371 FPS 887 frames in 5.0 seconds = 177.373 FPS -- You are receiving this mail because: You are watching all bug changes.
