Editing Input lag
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | ''' | + | I'''nput lag''' is the delay between pressing a button and seeing the game react.<ref>http://www.anandtech.com/show/2803</ref>The potential causes for "input lag" are described below (steps which have negligible contributions to the input lag have been omitted). Each step in the process increases "input lag", however the net result may be unnoticeable if the overall "input lag" is low enough. |
− | |||
− | |||
− | |||
==Causes== | ==Causes== | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | ===Controller=== | |
− | |||
− | |||
− | + | <br />For wired controllers, this lag is negligible. For wireless controllers, opinions vary as to the effect 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.<ref>http://www.lockergnome.com/uncategorized/2011/08/26/wireless-controller-latency-is-it-a-problem/</ref> | |
− | |||
− | |||
− | |||
− | |||
− | + | ===Display lag=== | |
− | + | This is the lag caused by the digital televisions and monitors. Image processing (such as upscaling, 100 Hz, motion smoothing, edge smoothing) takes time and therefore adds some degree of input lag. It is generally considered that input lag of a television below 30ms is not noticeable,<ref>http://www.bit-tech.net/hardware/monitors/2009/02/06/the-dark-side-of-overdrive/4</ref> Discussions on gaming forums tend to agree with this value. Once the frame has been processed, the final step is the [[pixel response time]] for the pixel to display the correct colour for the new frame. | |
− | ---- | ||
− | |||
− | |||
− | + | [[CRT tvs]] and [[monitors]] have no input lag. | |
− | |||
− | == | + | ===Typical overall response times=== |
− | |||
− | |||
− | + | <br />Testing has found that overall "input lag" (from controller input to display response) times of approximately 200ms are distracting to the user.<ref>http://www.eurogamer.net/articles/digitalfoundry-lag-factor-article?page=2</ref> It also appears that (excluding the monitor/television [[display lag]]) 133ms is an average response time and the most sensitive games achieve response times of 67ms (again, excluding [[display lag]]). | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | [[Category: | + | References |
+ | {{reflist}}=== | ||
+ | [[Category:Video hardware]] |