Overclock.net › Forums › Components › Mice › somewhat objectively evaluating sensor responsiveness
New Posts  All Forums:Forum Nav:

somewhat objectively evaluating sensor responsiveness - Page 56

post #551 of 700
reword ur question because the xai is the only mouse i know of that dose this correctly built into the mouse
post #552 of 700
How do you know that though? Can you try that test that I outlined? Use MouseTester and record swiping your Xai off of some surface you know it tracks well on. Best to hold that surface up with the other hand to make sure no residual stuff is being imaged.
post #553 of 700
rgr
post #554 of 700
post #555 of 700
Ok, let's try that again. tongue.gif

Look at my graphs on the previous page. What you want to see is a growing curve (your movement on the tracking surface) and then a more or less sharp decline once there's a lack of surface to track against.
post #556 of 700
post #557 of 700
best i could do i lifted it till it wont track then droped it to track best i could do
post #558 of 700
post #559 of 700
Hello.

Have you seen this thread?

It's easy to measure input lag objectively with this stuff.
1. Enable Dual Mode. Blue will be Device1 and green will be Device2.
2. Move the 2 mice together, pressing them together while collecting.
3. Open Plot and choose xVelocity. Maybe DPI-s weren't accurate so change it to make the speeds equal. You don't need to Collect again, just change DPI and press Plot again.
4. When the speeds of the 2 mice are equal, use the Input lag delay field.

IMPORTANT: one measurement is nothing. The result may vary, so make at least 5 measurements to get rid of errors.

Here's an example measuring Razer Mamba's input lag in wireless mode, compared to G100s, both at 500 Hz. Blue is G100s.



post #560 of 700
Yeah, that's the original method qsxcv came up with. And thanks again for implementing it in the program and generally improving it!
The way I did it there can however tell us more about the lag without the need for a second mouse (i. e. absolute and not only relative results), and potentially something more about the nature of the lag too, i. e. some qualitative evaluation rather than mostly quantitative. Maybe even different types of lag (with the standard test you can't account for differences in lag associated with acceleration, deceleration or impulse response).

So my A6010 vs. MLT04 is +4ms at any CPI... So just counting reports after the surface ends doesn't do the trick as far as interpreting continuous tracking lag.
Edited by HAGGARD - 2/9/16 at 11:46am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mice
Overclock.net › Forums › Components › Mice › somewhat objectively evaluating sensor responsiveness