huh ok, Enotus Mouse test works...

Enotus Mouse Test v0.1.4
Mouse: Deathadder [email protected],%hid.mousedevice%;HID-compliant mouse
Model: n/a
Resolution: 1800 dpi \excellent\
Polling speed: 888 Hz
Max speed: 1.32 m/s (93261 points/s) \good\
Precision: 99.9 % (0.09 m/s) \excellent\
Smoothness: 44.6 % \bad\
Debug data: [('159', '0.99'), ('93', '1.03'), ('79', '0.97'), ('92', '1.00'), ('79', '1.01'), ('92', '0.99'), ('79', '0.99'), ('93', '1.02'), ('79', '1.00'), ('91', '1.04')]

wtf smothness DA, pooling rate (dimr showing 1000) and speed...
with second test speed 2,44
--------------------------------------------------------------------------------
Enotus Mouse Test v0.1.4
Mouse: @oem58.inf,%hid\vid_045e&pid_0040.devicedesc%;Microsoft USB Wheel Mouse Optical (Mouse and Keyboard Center)
Model: n/a
Resolution: 400 dpi \bad\
Polling speed: 492 Hz
Max speed: 1.50 m/s (23653 points/s) \good\
Precision: 99.0 % (0.15 m/s) \excellent\
Smoothness: 8.2 % \ok\
Debug data: [('49', '2.07'), ('43', '1.92'), ('48', '2.08'), ('51', '1.97'), ('44', '2.03'), ('48', '1.93'), ('46', '2.01'), ('48', '2.00'), ('48', '2.06'), ('45', '1.86')]
with second test speed 1,80

I don't understand why high dpi is better... dont care... but interesting results.

EDIT:
Another test

Enotus Mouse Test v0.1.4
Mouse: Deathadder @msmouse.inf,%hid.mousedevice%;HID-compliant mouse
Model: n/a
Resolution: 1800 dpi \excellent\
Polling speed: 880 Hz
Max speed: 4.06 m/s (287590 points/s) \excellent\
Precision: 99.4 % (0.10 m/s) \excellent\
Smoothness: 44.7 % \bad\
Debug data: [('521', '1.00'), ('264', '1.00'), ('261', '1.03'), ('263', '0.97'), ('261', '1.00'), ('263', '1.00'), ('261', '1.00'), ('263', '0.98'), ('259', '1.02'), ('261', '1.00')]

smoothness on 500hz is about 25%, pooling rate unstable...

----------------------------
Enotus Mouse Test v0.1.4
Mouse: @oem58.inf,%hid\vid_045e&pid_0040.devicedesc%;Microsoft USB Wheel Mouse Optical (Mouse and Keyboard Center)
Model: n/a
Resolution: 400 dpi \bad\
Polling speed: 497 Hz
Max speed: 2.09 m/s (32880 points/s) \good\
Precision: 99.5 % (0.17 m/s) \excellent\
Smoothness: 5.3 % \good\
Debug data: [('62', '2.01'), ('73', '2.00'), ('71', '2.04'), ('66', '1.95'), ('54', '2.00'), ('62', '2.00'), ('69', '2.00'), ('67', '2.00'), ('64', '2.00'), ('69', '2.00')]
with other test max speed was over 4 m/s

so WMO>DA :P

I wrote an app to test one mouse's accel vs. another.

I just need to patch it up a bit so it's easier for general use. Right now I just recompile it when I need to adjust something.

cool stuff.
Did you know how 'smoothness" works in Enotus test because it seems a bit bugged? ....

I don't, but I considered writing something that would consider how uniformly the mouse reported more counts as speed increased.

It was really surprising to me (I guess because I'm just unfamiliar with it) that mice can report counts in an extremely non-uniform way and you can barely notice it in-game during a "swipe" since a swipe takes place over so many counts at such a quick speed.

Maybe this is what the "smoothness" test is doing. Not sure how that would work though. I guess you could take a random swipe at an unknown DPI, record the data, see how many counts total were reported, then break up the data into small time frames and see how similar the number of counts reported was.

The problem is how it takes into account the speed/acceleration of the mouse motion. Obviously if you're moving faster you would have a spike in counts. Maybe it "guesses" what the velocity curve looks like, then compares it to some sort of ideal curve where the counts reported is extremely uniform, deriving a "smoothness" value that way.

Would that work? Not sure. It would help if I had some kind of special "diagnostic" mouse, that could report counts in any way I wanted, so I could deliberately make its reporting extremely unsteady, but still exhibit no acceleration.

Any soft to measure mouse real dpi?

Enotus test measure it, but also its a bit weird.

That should be easy to make, meh. I shouldn't say that because I'm very lazy and it would need a decent interface.

Since you actually mentioned it you would be my hero if ever done this :D as well as for many other users i know who are curious about their "true" mouse dpi. Dont care how ugly the interface will look

Ye would be great!

>Dont care how ugly the interface will look

Famous last words! :-)

In that case here you go:

https://www.dropbox.com/s/kozhrnl13om275t/MouseWhisperer.exe

You'll have to keep the mouse from moving after a swipe or it will reset. The timeout time is 350 ms. You'll have to decide on your own measurement and then take down the counts, either by writing them down on paper, or alt-tabbing to a text file whose window size is set not to obscure the program output. Also you can't move the mouse ;-)

It generates a couple data files right now in the directory that it's run in. Delete these if you use the program a lot as they could conceivably become quite large..

sx and sy would be what you would look at. So if + or - 1574 counts were reported over a 10 cm swipe you know there was about 157.4 counts per centimeter, or ~400 (157.4 * 2.54) counts per inch (CPI, aka DPI).

The thing is very sensitive, as even at 400 dpi one count occurs every 63.5 micrometers, so you'll very likely need some margin for error. Also don't bump the table when writing down the number :-)

Ignore x and y cm as they are based on 400 dpi, as are the other figures. Long story on those.

This all sucks royally, but you said you didn't care how bad the interface was! :-)

Just discovered this tool and its nice! Any plans for updating it? Now its waaay too sensitive so mb just little adjustment for testing start/stop by click would be great!
Also would be cool if those who is interested in their actuall mouse dpi and tried this software posted their results here.
Note. The greater distance your mouse passed on mousepad-the more accurate results you will get so i would suggest smth like 30cm for measurement.
So far i made a test for Logitech G5 and it gives me around 430 dpi on its standart setup instead of 400dpi, more to come for testing!

Well anything that captures the full mouse input is going to be sensitive. Even 400 dpi is a count every 63.5 micrometers.

I agree that something like a click would be good, but I mean so would a ton of other things, like an actually clickable 'x' button, and a menu or two, or a couple options.

There are also issues with the text data output that I'd like to address.

It took a TON of work for me to get it to this point though, which is hard to believe because it looks like such a crude/tiny program, but it really did. I haven't been in a hurry to bring up the code again even though I really should.

Allright i've got your point. Can you comeout with some mouse test results btw?

Enotus Mouse Test v0.1.4
Mouse: Microsoft PS/2 Mouse
Model: n/a
Resolution: 400 dpi \bad\
Polling speed: 104 Hz
Max speed: 0.68 m/s (10722 points/s) \ok\
Precision: 100.0 % (0.06 m/s) \excellent\
Smoothness: 2.6 % \excellent\
Debug data: [('103', '9.48'), ('105', '9.52'), ('103', '9.53'), ('103', '9.52'), ('103', '9.50'), ('103', '9.54'), ('100', '9.51'), ('101', '9.53'), ('101', '9.51'), ('100', '9.53')]

I always knew my ball mouse was best, but now I have the documentation to back it up.

found Outerspace's Max IPS logger
http://www.sendspace.pl/file/1537a54bef4bf98d945f3c3

btw. imo graphs > enotus when measuring max speed.

Very usefull tool thx!

Instead of using a mouse testing software, you can simply use an online mouse tester that will test your mouse without consuming unnecessary space. One of the online mouse testers that I use: http://www.keyboardtester.co/
There are few others too, that can be used.

Enotus Mouse Test v0.1.4
Mouse: @oem19.inf,%rzdev.devicedesc.005a%;Razer Lancehead
Model: Lancehead wireless in wireless mode
Resolution: 800 dpi \ok\
Polling speed: 996 Hz
Max speed: 3.80 m/s (119805 points/s) \excellent\
Precision: 99.6 % (0.26 m/s) \excellent\
Smoothness: 2.0 % \excellent\
Debug data: [('183', '0.97'), ('267', '0.91'), ('173', '1.00'), ('83', '1.00'), ('83', '1.00'), ('81', '1.01'), ('80', '1.05'), ('77', '0.94'), ('77', '1.00'), ('74', '0.96')]

Thanks @H1ghlander for sharing the link for us. I didn't know about the mouse testing software.

What other alternatives can I use (like a free mouse testing software)? I found one on OverClock forum. And here's a draebenstedt.de thread with the links: really cool program to test mouse, vid , accuracy, latency, do my essar on testing.

Will that program work to test my thinkpad's trackpoint mouse? Well, it has a problem, once in an hour or so the mouse starts to live its own life, moving to a random direction for five seconds. The problem was described here https://forums.lenovo.com/t5/ThinkPad-X-Serie...-p/4128099 high school writing

thank you!!!

there u go buddy bestest Mouse Test SW on Steam 2023

I guess you could take a random swipe at an unknown DPI, record the data, see how many counts total were reported, then break up the data into small time frames and see how similar the number of counts reported was.

8000hz compatible mouse tester - https://github.com/microe1/MouseTester/releas...ester_v1.4