Changes

Jump to navigation Jump to search

Input lag

107 bytes added, 19:38, 17 September 2013
Cleanup; dead links removed (make the page first, then link)
I'''nput Input 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==
===Display lag===
This is the lag caused by the digital televisions and monitors. Image processing (such as upscaling, 100&nbsp;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|CRT TVs]] and [[monitors]] have no display lag.
===GPU driver latency===
Hard syncing option in some emulators can reduce or remove this.
You avoid all of this with This can be avoided by using KMS and DRM/EGL - you are , specifically on Linux; using these, the user is in control of your front and back buffers and dont don't have to rely on API magic - APIs, so you know exactly that they can find where and when a frame was dropped and how to act accordingly with that in mind. You might need It is advisable to get the latest drivers if you have an driver to improve performance, as notable graphics chip manufacturers (e.g. AMD card or else , Nvidia) do not find KMS mode will suck. I don't know how far along Nvidia is by nowa priority. Intel graphics chips, however, should be fineregardless, but it is still advisable to update drivers.
===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>
==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]]).
==Ways to reduce input lag==
==References==
 
{{reflist}}
[[Category:Video hardware]]
Anonymous user

Navigation menu