
However, while middle screen measurements are a common and fully valid input lag testing method, they are limited in what they can reveal, and do not account for the first on-screen reaction, which can mask the subtle and not so subtle differences in frame delivery between V-SYNC OFF and various syncing solutions a reason why I opted to capture the entire screen this time around.ĭue to the differences between the two test methods, V-SYNC OFF results generated from first on-screen measurements, especially at lower refresh rates (for reasons that will later be explained), can appear to have up to twice the input lag reduction of middle screen readings:Īs the diagram shows, this is because the measurement of the first on-screen reaction is begun at the start of the frame scan, whereas the measurement of the middle screen reaction is begun at crosshair-level, where, with G-SYNC, the in-progress frame scan is already half completed, and with V-SYNC OFF, can be at various percentages of completion, depending on the given refresh rate/framerate offset. In my original input lag tests featured in this thread on the Blur Busters Forums, I measured middle screen (crosshair-level) reactions at a single refresh rate (144Hz), and found that both V-SYNC OFF and G-SYNC, at the same framerate within the refresh rate, delivered frames to the middle of the screen at virtually the same time. It has become the standard among testers since, and is used by a variety of sources across the web. The input lag testing method used in this article was pioneered by Blur Buster’s Mark Rejhon, and originally featured in his 2014 Preview of NVIDIA G-SYNC, Part #2 (Input Lag) article. Overwatch w/lowest settings, “Reduced Buffering” enabledĬounter-Strike: Global Offensive w/lowest settings, “Multicore Rendering” disabled I7-4770k w/Hyper-Threading enabled (8 cores, unparked: 4 physical/4 virtual)ĮVGA GTX 1080 FTW GAMING ACX 3.0 w/8GB VRAM & 1975MHz Boost Clockġ6GB G.SKILL Sniper DDR3 MHz (dual-channel: 9-10-9-28, 2T)ĥTB Western Digital Black 7200 RPM w/128 MB cache Razer Deathadder Chroma modified w/external LEDĭefault settings (“Prefer maximum performance” enabled)


