3 ms·
Interesting. Yeah, vsync is a latency killer and it's disabled by default in `rx`. What software renderers are not so good at is drawing lots of pixels every fr
by cloudhead 7y ago
Interesting. Yeah, vsync is a latency killer and it's disabled by default in `rx`. What software renderers are not so good at is drawing lots of pixels every frame, so for example panning a view with lots of images open, or zooming in and out of an image that covers the screen.
I'd expect these kinds of operations to be slow at high resolution without the help of the GPU. You could probably speed things up with SIMD and multi-threading, at the expense of implementation complexity.
- gdxhyrd 7y ago> vsync is a latency killer VSync, if done properly, only adds less than a single frame of latency. That is 17ms tops for 60Hz, which nobody notices unless you are a pro-gamer on an FPS game. Certainly it does not matter for a pixel editor.
- baq 7y agoText editors on 144 FPS gsync monitor are noticeably better than vsync 60 FPS in a way in which a BMW door is noticeably better at closing than entry level cars. Technically both work the same and yet you can tell they’re very different.
- gdxhyrd 7y agoNo. VRR (GSync) does not do anything if your computer can achieve 144Hz (which for a text editor any computer should).
- xchaotic 7y agoThis can be easily proven that the extra latency can be noticed by doing a reaction test and recording the screen
- gdxhyrd 7y agoI haven't said you cannot notice. In fact, I said you can, in the right conditions.
- cloudhead 7y agoI don’t see how you’d reliably get less than a frame of latency with vsync. If your mouse input lands while you are waiting for the next frame, you will lose at least one whole frame. In terms of comparison with an FPS, the same amount of responsiveness is required for any UI - ie. there should be no perceptual latency. Adding 17ms certainly is perceptual.