> That’s not true, though. It takes more than 30ms just to render your frame, deliver it to the monitor, and wait for a screen refresh. For cheap non-CRT scree

> That’s not true, though. It takes more than 30ms just to render your frame, deliver it to the monitor, and wait for a screen refresh. For cheap non-CRT screens you are correct. Otherwise, not so much. And even if you're using a cheap screen, latencies of 50ms vs 30ms (typical numbers for vsync on vs vsync off) definitely have an impact on player performance besides just feeling more/less sluggish. See also my post here: https://news.ycombinator.com/item?id=23806493 https://news.ycombinator.com/item?id=23806493 > https://www.pcgamer.com/heres-how-stadias-input-lag-compares-to-native-pc-gaming/ https://www.pcgamer.com/heres-how-stadias-input-lag-compares... That PC gamer article is horrible and amateurish. There's no mention of what vsync/nvidia driver settings they used etc. Also games like Destiny are pretty far from being optimized for low input lag. With CRTs and properly optimized/coded games like CS you can achieve input lag as low as 5ms (though that's just the time until the monitor begins drawing the first rows of pixels after the change). Here's a few links on input lags measurements: http://www.esreality.com/post/2691945/microsecond-input-lag-measurements/ http://www.esreality.com/post/2691945/microsecond-input-lag-... https://forums.blurbusters.com/viewtopic.php?f=10&t=1381&hilit=csgo+input+lag https://forums.blurbusters.com/viewtopic.php?f=10&t=1381&hil... http://esreality.com/post/2640619/input-lag-tests-ql-csgo-q3a/ http://esreality.com/post/2640619/input-lag-tests-ql-csgo-q3... People doing A/B tests: https://forums.blurbusters.com/viewtopic.php?f=10&t=1134 https://forums.blurbusters.com/viewtopic.php?f=10&t=1134 And a demonstration that even input lag as low as 10ms can be noticeable: https://www.youtube.com/watch?v=vOvQCPLkPt4 https://www.youtube.com/watch?v=vOvQCPLkPt4