Input lag
Input lag or input latency is the amount of
In
Potential causes of delay from pressing a button to the game reacting
The potential causes for input lag are described below. Each step in the process, however small, increases total input lag, however the combined result may not be noticeable if all input lag is low enough.
Controller sends signal to console
For wired controllers, this lag is normally negligible. For wireless controllers, opinions vary as to the significance of this lag. Some people claim to notice extra lag when using a wireless controller, while other people claim that the 4–8 milliseconds of lag is negligible.[1]
Console/PC processes next frame
A
Individual frames need not be finished within the interval of a screen refresh to output at an equivalent rate. Game engines often make use of pipelined architectures to process multiple frames concurrently, allowing for a more efficient use of the underlying hardware. This exacerbates input lag, especially at low frame rates.[2][3]
Display lag
This is the lag caused by the television or monitor (also called output lag). In addition to the latency imposed by the screen's
Typical overall response times
Testing has found that overall input lag (from human input to visible response) times of approximately 200 ms are distracting to the user. It also appears that (excluding the monitor/television display lag) 133 ms is an average response time and the most sensitive games (
See also
References
Input Lag Test: TVs from 2016 + 2017 Dein-Fernseher.de
- ^ "Wireless Controller Latency: is It a Problem? - LockerGnome". LockerGnome. 2011-08-27. Archived from the original on 2016-08-28. Retrieved 2016-06-12.
- ^ Ericson, Christer (2007-09-22). "Input latency". realtimecollisiondetection.net - the blog.
- ^ Carmack, John (2013-02-22). "Latency Mitigation Strategies". #AltDevBlogADay. Archived from the original on 2013-02-25.
- ^ "The Dark Side of Overdrive". bit-tech. Retrieved 2016-06-12.
- ^ "Console Gaming: The Lag Factor". Eurogamer. Gamer Network. 5 September 2009. p. 2. Retrieved 2016-06-12.