You are not logged in.
Usually VSync introduces input lag. That's in the nature of Vsync try turning it of in the KWin settings.
That's why hardcore gamers buy 120 Hz monitors, because VSync adds a tiny handicap in fast paced shooters.
Last edited by blackout23 (2013-05-05 10:32:25)
Offline
smakked wrote:but in reality who moves windows around that fast ?
It's not about moving windows, it's about lag, which is "everywhere", again, the same example http://youtu.be/nNK0YIqawuY but I understand that this is not a problem for most people.
Yeah doesnt bother me, just installed Nvidia driver and it is actually alot more noticeable then the opensource variant.
Certified Android Junkie
Arch 64
Offline
I tried it out. It's just VSync doing its job as I expected.
Offline
Since I have both Windows 8 and Arch Linux installed on the same machine I can report the following regarding lag when dragging windows, using Radeon HD6850 (with open drivers on linux):
- X11 + Compiz standalone: noticeable lag when dragging at slow speeds
- Wayland + Weston: still noticeable lag, a bit less that X11
- Windows 8: no lag that I can see, if you try to move faster you can't see anything anyway
No tearing whatsoever in any of the cases. Not sure how indicative this is of the general lag with the graphics systems of course.
Offline
intel i5 3570k, nvidia gt670, and no lag , is so strange your problem. Probably, a driver issue
Offline
Since I have both Windows 8 and Arch Linux installed on the same machine I can report the following regarding lag when dragging windows, using Radeon HD6850 (with open drivers on linux):
- X11 + Compiz standalone: noticeable lag when dragging at slow speeds
- Wayland + Weston: still noticeable lag, a bit less that X11
- Windows 8: no lag that I can see, if you try to move faster you can't see anything anywayNo tearing whatsoever in any of the cases. Not sure how indicative this is of the general lag with the graphics systems of course.
radeon 6850 with opensource drivers-.....
Offline
@smph
radeon * (especially with opensource driver) - it is a lag by default under linux.
Also OP has nvidia with proprietary driver, so your comparison isn't correct. When radeon lags, nvidia should be smooth.
Offline
Well, there was some talk about the general compositing performance on linux so I did the comparison mainly in reference to that. I also tried Intel integrated graphics (Ironlake) on the same machine, and with Compiz the window dragging lag was pretty much exactly the same but interestingly under Weston there was no lag whatsoever (like Windows 8).
And don't get me wrong, my desktop is actually quite smooth even when running Compiz with radeon opensource at low clocks, there's just this frame-or-two lag between the cursor movement and the screen action, not very noticeable in general use IMO.
Edit. I can also tell that resizing the same GTK3 apps is MUCH smoother on Wayland than with X11, so there is hope.
Last edited by smph (2013-05-05 21:19:09)
Offline
nuc wrote:Nonsense. Compositing is important for fluentness and less workload because it enables hardware acceleration. Without compositing there will be tearing and unfluent window resizing because the CPU has to render it. With Hardware acceleration, the GPU does the job.
Oh, come on. I agree only with tearing. Resizing is much, much faster without compositing.
I'm have heard this earlier. For me if I resize without compositing I get heavy tearing and graphical artifacts. With compositing the tearing is gone and the artifacts disapear. Instead I get a little bit less fluent resizing but the differense is really small and as the graphical quality is so much better I think it's look much better with compositing.
I also get a little bit choppy resizing in OSX it's better than KDE but not a big difference really. I have always assumed it is a effect of clientside decoration, some sort off PID link:ish effect or somthing...
Offline
frame-or-two lag
Seems relevant: Nvidia has a default lag of up to 3 frames, which can be changed with OGL_MaxFramesAllowed.
Offline
Can you please show us the output of
qdbus org.kde.kwin /KWin supportInformation
command?
Offline
For me if I resize without compositing I get heavy tearing[...]
No one has said otherwise.
[...]and graphical artifacts. With compositing the tearing is gone and the artifacts disapear.
I'm not sure about what artifacts are you talking. The only thing that comes to mind is XSync, but unfortunately KWin also isn't good at this. Here's a comparison with Compiz (60fps; take a look at tabs bar and scrollbar):
Compiz - 883KiB https://mega.co.nz/#!mBhylLaI!Y790Tkk0I … O0-nlz-EM4
KWin - 1.1MiB https://mega.co.nz/#!Pcgi3bQA!KO7xZ3iWz … NFAZASHWmE
smph wrote:frame-or-two lag
Seems relevant: Nvidia has a default lag of up to 3 frames, which can be changed with OGL_MaxFramesAllowed.
Thanks for the tip, but unfortunately if there is any difference, I can't see it.
Offline