[qsxcv]

credits to Jonagold for coming up with this idea in the finalmouse thread
http://www.overclock.net/t/1531877/finalmouse-2015/1850#post_24118688
http://www.overclock.net/t/1531877/finalmouse-2015/1870#post_24121092

AUG 2015 UPDATE: microe (creator of mousetester) releases
http://www.overclock.net/t/1570462/mousecomparator

use this instead. it's much easier and the sums plot are easier to interpret
basically, the procedure is to plug both mice in (use the adjacent ports so that polling is in sync), flip one mice 180, press two mice tightly against each other, and move them together horizontally without slipping.

originally Jonagold and some others were basically looking at which mouse responded first with the first count.

i've found it more useful and consistent to start from rest and push the two mice fairly hard for ~15cm, compare which mouse reaches 10 counts of motion first, and count how many counts the other mouse reported in that interval

disclaimer: i am human and so this applies to me. however i am aware of this and did my best to not cherry-pick plots which show one mice particularly favorably. i repeated each comparison several times to get a feel for the general differences, and below i will show plots that i found to be representative of the typical difference

g502 (positive) vs g303 (negative), 400dpi, 1000hz

almost perfect match, not too surprisingly.
at time = 648ms, both g502 and g303 have moved 10 counts

g502 (positive) vs wmo (negative), 400dpi, 1000hz

very close
at time = 2133ms, wmo has moved 10counts , g502 has moved 9 counts

g502 (positive) vs finalmouse (negative), 400dpi, 500hz (because finalmouse only does 500)

at time=1878ms, g502 has moved 11 counts, finalmouse has moved 5 counts

g502 (positive) vs torq x5 (negative), 400dpi, 1000hz

at time = 573ms, g502 has moved 10 counts, x5 has moved 6 counts.

g502 (positive) vs g100s (negative), 1000dpi, 500hz

both reach 35 counts at time = 344ms

for all of these, i started from rest and moved the two mice as fast as i could for ~15cm or so. the motion of the mice was about as fast as when doing a flick in cs.

i've also done like wmo (positive) vs g502 (negative) and it gives the same results

i've found this to be quite repeatable but you should try with your own mice so that we have more data and can compare.

 

[Scharfschutzen]

Only mice I have at work and not sure if this is even worth anything since they're at different dpi's:

Sensei RAW (positive) vs Lua (negative), 540 dpi / 500 dpi, 1000hz

 

[qsxcv]

thanks. should still be reasonably close for those dpi
for that image raw (sensei raw?) moved 11 counts while lua was still at 4 counts.

 

[iceskeleton]

very nice finds by people at overclock

 

[treach]

yep, good job from you both

 

[popups]

Quote:

Originally Posted by qsxcv

g502 (positive) vs wmo (negative), 400dpi, 1000hz

very close
at time = 2133ms, wmo has moved 10counts , g502 has moved 9 counts

g502 (positive) vs finalmouse (negative), 400dpi, 500hz (because finalmouse only does 500)

at time=1878ms, g502 has moved 11 counts, finalmouse has moved 5 counts

 

[banjogood]

Do you think FMs MCU filtering off would change the results? Perhaps make them more comparable to Logitech mice?

 

[qsxcv]

it should only affect like 1-2 counts for this test. not completely sure though... depends on how the filter diffuses the error

as i've said before it's not something that makes a big difference

also i forgot to mention, wmo and g502/303 both enter a rest mode. for wmo the sensor framerate drops 600hz after 1-2 seconds of inactivity. for g502/303 sensor framerate drops to 1000hz after 10-15seconds. for all the tests above i made sure that no mice was in rest mode when i began motion. ill do some comparisons between rest mode vs run mode tonight

 

[popups]

Quote:

Originally Posted by qsxcv

it should only affect like 1-2 counts for this test. not completely sure though... depends on how the filter diffuses the error

as i've said before it's not something that makes a big difference

also i forgot to mention, wmo and g502/303 both enter a rest mode. for wmo the sensor framerate drops 600hz after 1-2 seconds of inactivity. for g502/303 sensor framerate drops to 1000hz after 10-15seconds. for all the tests above i made sure that no mice was in rest mode when i began motion. ill do some comparisons between rest mode vs run mode tonight

The MLT-04 goes in to rest state "quickly." At least it doesn't take much for it to "wake."

While playing with an my old Intellimouse I noticed there was something off about it. That's when I remembered about the 3 different states it has. I noticed it during specific situations. I adapted by simply moving the cursor in a circular motion just fast enough to stop it from entering rest mode.

 

[qsxcv]

whats the 3rd state???

 

[thuNDa]

good job with this test method, yea.

 

[popups]

Quote:

Originally Posted by qsxcv

whats the 3rd state???

No motion, motion and in air.

 

[qsxcv]

how do you know that in air is different from no motion?

 

[Trull]

Quote:

Originally Posted by popups

No motion, motion and in air.

u wot?

 

[popups]

Quote:

Originally Posted by qsxcv

how do you know that in air is different from no motion?

In the air the LED blinks, whereas while resting on a surface it does not. Is that the case with the WMO?

 

[qsxcv]

iirc for both it strobes at 600hz

 

[CorruptBE]

Hmmz interesting.

I've got a holiday for 8 days now, might take a look at Abyssys 2014 WITH and WITHOUT Synapse.

And maybe some old 3090 vs 3310's as well (mostly Zowie's) as I've always found responsiveness to be like this from all the "sensors" I've used:

Old DA 3.0G without prediction > 3366 > 9500 & Razer 3.5G Mice without Synapse > 3310 > 3090

Also a thing I'm interesting in seeing is the Savu vs other 3090's (for some reason I always found the Savu feeling slightly better).

Anyhow I need a nap now first

Kudos on finding a more objective way, in the past results like this have somewhat helped push the industry in a different direction (remember Sujoy's mousescore??).

 

[uaokkkkkkkk]

It will be interesting to see tests of all the 3090's,3310 sensor based mice. That, and tests comparing the same model of mouse to each other.

 

[AnimalK]

Very cool. Curious to see the results of a DeathAdder S3988.

 

[qsxcv]

well i don't have many of those mice which you guys (and i as well) are interested in

but if anyone has these mice, i'd like to see how these perform against a 3366 mouse (since the g502 and g303 seem to be quite predictable and responsive for this test, and many people have one of them).
g302 and g402
twin-eye mice
mice with older avago sensor (2020, s3668)
wireless gaming mice