got bored and tried this again.
just got 17/25 for 10ms
if you add up my three results (16,15,17) you get 48/75
that's a p-value of 0.01 !!!
anyway a situation where 10ms input lag for sure affects performance is in csgo, dust2, awping enemies running across mid double doors from t spawn. you need about a reaction time around 0.15 to 0.17s to kill them as they cross the gap. and for that, an additional 10ms of input lag can definitely lead to missed shots.
Input lag AB test
Re: Input lag AB test
First two tries just now,
50ms: 25/25
5ms: 18/25
This is a fantastic app. damn. I play a rhythm game called 'osu' and despise input lag with a burning passion. Placebo my azz. ty for this
50ms: 25/25
5ms: 18/25
This is a fantastic app. damn. I play a rhythm game called 'osu' and despise input lag with a burning passion. Placebo my azz. ty for this
Re: Input lag AB test
uwotm8oblistar wrote: 5ms: 18/25
can u try at 10ms?
Re: Input lag AB test
50 ms : 25/25
8 ms : 25/25
4 ms : 14/25
So as I expected, I'm very sensitive to input lag until below 8 ms.
8 ms : 25/25
4 ms : 14/25
So as I expected, I'm very sensitive to input lag until below 8 ms.
-
- Posts: 8
- Joined: 26 Jan 2015, 15:49
Re: Input lag AB test
Nifty little program, thanks!
My suggestion would be to add geometric shapes in the background to have some reference point.
I find that doing the same movement repeatedly loses effectiveness with repetition.
Your brain just gets used to it and you can't tell the difference anymore.
I find myself combining all sorts of movements: circles, eights, squares, crosses, Xs, triangles, moving from side to side of the splitting bar, etc...
Some shapes so that one can trace the perimeter in the fastest/most accurate way would make the test more effective in my opinion.
My suggestion would be to add geometric shapes in the background to have some reference point.
I find that doing the same movement repeatedly loses effectiveness with repetition.
Your brain just gets used to it and you can't tell the difference anymore.
I find myself combining all sorts of movements: circles, eights, squares, crosses, Xs, triangles, moving from side to side of the splitting bar, etc...
Some shapes so that one can trace the perimeter in the fastest/most accurate way would make the test more effective in my opinion.
Re: Input lag AB test
50 ms : 25/25
25 ms : 25/25
4 ms : 18/25
Samsung SyncMaster 2032BW 70Hz
25 ms : 25/25
4 ms : 18/25
Samsung SyncMaster 2032BW 70Hz
- lexlazootin
- Posts: 1251
- Joined: 16 Dec 2014, 02:57
Re: Input lag AB test
I really want to try this but my version of the program is v-syncing on windows 8. is there something I should be doing?
I don't think getting 18/25 is enough to determine you can tell a difference. you could easily just click one side and every (Something) of a person would get it too easily. (If someone could tell me how to do the math of figuring out how many people would get ATLEAST 18/25 please tell me)
EDIT: NM I can force it off with amd drivers... silly me.
I don't think getting 18/25 is enough to determine you can tell a difference. you could easily just click one side and every (Something) of a person would get it too easily. (If someone could tell me how to do the math of figuring out how many people would get ATLEAST 18/25 please tell me)
EDIT: NM I can force it off with amd drivers... silly me.
-
- Posts: 31
- Joined: 30 May 2014, 15:45
Re: Input lag AB test
lex how did you force it off with AMD?. In CCC I put it to "always off", but the FPS stays the same as my hz.
Re: Input lag AB test
I had to use radeonpro to force it off.MaximilianKohler wrote:lex how did you force it off with AMD?. In CCC I put it to "always off", but the FPS stays the same as my hz.
- lexlazootin
- Posts: 1251
- Joined: 16 Dec 2014, 02:57
Re: Input lag AB test
yea idk, it's kinda fooked. i had to just keep changing setttings till it worked... it's pretty random, i would edit the program and turn on and off the vsync and do the same to my driver. eventually it would workMaximilianKohler wrote:lex how did you force it off with AMD?. In CCC I put it to "always off", but the FPS stays the same as my hz.