Posts: 1,212
Threads: 32
Joined: Nov 2011
26 Jul 14, 05:48PM
(This post was last modified: 26 Jul 14, 11:08PM by Vanquish.)
As the title says!
Just unzip and click "run.bat" to start.
https://drive.google.com/file/d/0B5jyMDf...sp=sharing
I'm probably not the best person to test this since my monitor is 60hz and has quite a great deal of input lag anyway, I'll test it with a CRT I have in my attic at a later date. Just thought this was interesting.
My results (on TFT):
50ms - 24/25
40ms - 25/25
25ms - 23/25
15ms - 19/25
10ms - 14/25
Posts: 992
Threads: 35
Joined: Mar 2011
25/25
I'll do some more extensive testing.
it's fairly easy to detect, maybe because im using 1000 polling rate with the mouse and 120hz monitor. I know that 1000 polling "skips" but that's a detection i cannot make.
Posts: 1,212
Threads: 32
Joined: Nov 2011
26 Jul 14, 08:33PM
(This post was last modified: 26 Jul 14, 11:21PM by Vanquish.)
hah and then I forgot to post my result :D post updated, thanks!
I'm a huge advocate of not using 1000hz as a polling rate (because no mouse can handle the input). As you say it's not a big deal but if you're comparing 500hz to 1000hz, there's only a millisecond of extra input delay and I'd rather sacrifice that extra millisecond of responsiveness (tbh on a 120hz monitor the extra millisecond might actually be surprisingly useful but for my setup it's not) for the sake of consistency in the frequency that the mouse updates its position on my screen. I think input lag is only going to be a significant problem on a mouse which has a 125hz polling rate [EDIT: or if you own a mouse with an 'artificial' polling rate, such as the Roccat Kone or Zowie EC-series mice]. Even if you have a mouse which is locked to 125hz, such as a WMO, you can actually overclock your mouse to poll at 500hz. There's a cool thread about it
here.
And I guess it's easier to detect on a 120hz monitor than a 60hz monitor, but I kinda predicted that most people who have played FPS games for a long time would not really have much trouble identifying input lag when they see it anyway. I just wanted to see if I'd get proven wrong :D
Posts: 963
Threads: 77
Joined: Dec 2010
26 Jul 14, 08:46PM
(This post was last modified: 26 Jul 14, 08:49PM by 1Cap.)
50 ms
25/25
regular notebook
800 dpi mouse
win7
Posts: 2,230
Threads: 32
Joined: Jun 2011
Posts: 1,212
Threads: 32
Joined: Nov 2011
26 Jul 14, 09:46PM
(This post was last modified: 26 Jul 14, 11:08PM by Vanquish.)
Updating my results a bit:
50ms - 24/25
40ms - 25/25 (?)
25ms - 23/25
15ms - 19/25
10ms - 14/25
I guess 15ms or thereabouts is my threshold for spotting input lag.
Posts: 51
Threads: 1
Joined: Jun 2011
50 ms: 25/25
20 ms: 23/25
15 ms: 17/25
10 ms: 14/25
5 ms: 9/25
Posts: 2,136
Threads: 50
Joined: Jun 2010
50 ms: 25/25
20 ms: 21/25
15 ms: 23/25
10 ms: 25/25
5 ms: 13/25
Not long after starting 15ms, I noticed an easier way to spot it, but somewhere between 10 and 5ms is clearly my cut off. Can anyone explain what the practicalities of this are?
Posts: 1,212
Threads: 32
Joined: Nov 2011
04 Aug 14, 04:59PM
(This post was last modified: 04 Aug 14, 05:00PM by Vanquish.)
I just thought it was an interesting test tbh. I guess it's useful in the sense that you can assess your sensitivity to input lag and delay/etc with a tangible statistic as opposed to just "feeling", but taking this test is somewhat redundant if you have a monitor/GPU/mouse with excessive input delay since the laggy feeling will be harder to detect than if you're using a 144hz/CRT monitor and a mouse with a high polling rate because of the intensity of the contrast between lag in milliseconds.
Your results are very impressive btw jamz.