>So the question is, where to get exact numbers?

So you take only one pixel and you image it, because there is a lens and optical system, and you [determine how] big is this pixel on the table. Then you [determine] how many can you put in one inch? And this is the resolution. So if your pixel is 30 micron big in the matrix, how many times can you put 30 microns into one inch? This is the resolution. [In this example] it’s about 840 DPI.
- http://www.pcgamer.com/gaming-mouse-myths-busted

This is what I understand the "native" DPI to be. You can roughly figure that out for a given sensor by microscoping the array, taking the size of a pixel and multiplying with lens magnification... I think. But then apparently modern mice have dynamically native steps so... I dunno. Those might still be achieved by interpolation, but if the performance tests we have at our disposal are anything to go by they are certainly not "a lie" - on some modern mice (G502) there are hardly differences up to even 12kdpi.

Well, as you already have noticed it is not as simple as that, and to satisfy your curiosity:

A3090, A9500, A9800 and all of their offsprings are 30x30, AM010 and PMW3320 are 26x26, A3050 and offsprings are 19x19, PMW3366 im not allowed to say.

>:D
Thanks.

PMW3366 im not allowed to say

>:(

Very nice video, do you have more?

He does not explain the correlation between native matrix dots numbers and a sensitivity that would be too high to not skip pixels on the screen.

But it's interresting when he say the lower the DPI the lower the noise level. I have a Zowie FK 2 A with 3310 sensor. It is supoposed to be able to go to 3200 or more depending on the mouse brand. Some Mionix engineer said it was native 1600 DPI on Overclock.net.

I use it at 1600 and i don;t see any flaw compared to 400/800 and i like the fast speed on the desktop. I tested with Enotus mousetes and the results shows it works great at 1600.

Tho i once in a while see my mouse go crazy and look at the floor/roof and that could indeed be caused by noise/hairs on the mousepad. This never happened with MLT04 sensor which is in ie3.0 WMO and IMO.

I wonder what is the real native matrix of the mice using 3366 sensor.

I would not be surprised to know that the real native matrix is around 400/800 on any mouse.

e: he clearly explains that high frequency ripple/noise is due to sensor with too much facked DPI, this reminds me the Razer mouse like the Abyssus.

e2: if I may suggest you mice brand it would be Zowie or Logitech, everything else is very questionnable.

Here is result of Enotus mouse test with Zowie FK2A (3310 sensor at 1600 DPI).

Enotus Mouse Test v0.1.4
Mouse: Souris HID
Model: wefw
Resolution: 1600 dpi \good\
Polling speed: 997 Hz
Max speed: 3.38 m/s (212769 points/s) \excellent\
Precision: 96.6 % (0.10 m/s) \good\
Smoothness: 6.7 % \good\
Debug data: [('193', '0.13'), ('192', '0.87'), ('190', '1.00'), ('190', '0.99'), ('189', '1.00'), ('189', '1.01'), ('215', '1.01'), ('186', '0.99'), ('186', '1.00'), ('186', '1.01')]

Well, as in monitors segment, in mice one there are extremely high amount of problems.
Marketing conquered the world and as a result we have dozens of sh1tty mice, that just useless for competitive level. That has issues with tracking - the most important mouse attribute. But MOM! 12000 DPI! MUST BUY! LOLNOOB YOUR SHITTY MOUSE HAS ONLY 400 I OWN YOU WITH MY 12000!!11

I bought my abyssus 2014 because of sensor. But it seems to be a sh1tty mouse anyway (synapse problems, impossibility of setting 450 dpi, only 400 or 500).
Razer puts a nice sensor in this mouse, but f_king up everything by this glitchy synapse. LEL.

I think I need WMO...
I miss my WMO...

Or maybe this poor-builded G100S? I don't care much if it has poor plastic, but tracking is better than aby2k14, right?

It's like in racing or something. Want a good %DEVICENAME%? Build it four yourself. Ahahah. Where is my sensor and panel factories...

I recently swapped back to my wmo at 125hz after using a FK for a year, and it's amazing.

Why 125?

Portability. I want to be able to plug it in to any computer and just go, and not fuss around with if I can overclock the USB port or not.

why not run it at 200Hz? with ps/2 port.

Superstition.

great video, thanks a lot for sharing!

Not sure if anyone knows the proper answer to this:-

If I have 800 dpi, and my "estimated useful dpi" is higher than 800 when zoomed (as calculated via http://www.funender.com/quake/mouse/index.html ) , does this mean I'll skip any pixels when I zoom?

I assume that you do, but not sure how important that is if native dpi >>>>>> dpi above useful required

>:))))))))))

On my aby 2k14 with 1080p res and 28cm/360 (csgo for example):
A) sens 1@1800dpi = normal tracking
B) sens 4.5@400dpi = skipping tiny mouse movements
So-called "eDPI" is the same, "real sensitivity" is the same (28cm/360).
400dpi is not enough for 1080p@28cm/360?

I'm though about doing some science (sensor accuracy tests).. If I'll have enough spare time I'll do it.
I want to know how much would be noise deviation if we for example will move mouse 1000 times for 30cm(for example) in the same conditions and how much every run would differ from another => we can calculate mouse accuracy.

I LOVE MY ABYSSUS!
http://i.imgur.com/i4vvjRO.png
[img1]

ME TOO
http://i.imgur.com/jvzGxEI.png

What MAUZpad are you using, COMRADE? Synapse installed or not? Dpi?

i wont tell you

Alright, then go to huy you little vodka lover!11

By the way my Abyssus feels fine @synapse installed+400dpi
http://i.imgur.com/ytn7QJk.png
I don't know what the yebat is happening to my abyssus, COMRADE.

That's why its the worst 3888 implementation. (less jitter but it doesn't feel as raw as some DA's/old abyssus/salmosa's)

turn your mousepad 45degrees

It's partly helping but..
I think I just buy G100S. Even A4Tech X-718BK was better, despite it has hard-prediction.. I lost all my accuracy with this f_king Abyssus.
It's really mindf_king when you miss not because you're bad but because of sh1tty mouse..
LIGHTENED LOGO MOM!11 REYZER!111

g100s is good, until it breaks. I suggest you buy couple straight lol. I wish dat mouse was more durable, cus I really love it.

So my mouse doesn't have 12000 DPI? My life is a lie :O

One more FUNNY THING
CSGO for example.
Sens 28cm/360.

Abyssus works relatively well@1800DPI@ingame sens 1

But if I'll install synapse and set it@400dpi@ingame sens 4.5 (same 28cm/360)
Then it starts to SKIP tiny movements. WTF????????

If I'll do the same trick with my A4Tech X-718 BK IT WORKS FINE.
1600DPI@1 ingame sens all OK
400DPI@4 ingame sens all OK, not a single skip, absolutely niiiiice tracking.

WHY?

http://www.funender.com/quake/mouse/index.html

raw input?

Because you need more than 400 DPI if you play at 1920x1080 res with a sensitivity that high and a 90 FOV. Clearly stated at the link Ian215 posted.

Basicaly at higher DPI it will detects smaller moves. But it has a correlation with ingame mouse sensitivity, past a certain point of sensitivity the sensor does not have enough depth to see that you moved from pixel 399 to 400 in the sensor while on the sreen you should have moved from 1 or more pixels. It does not work exactly like that but the analogy is correct i belive.

The higher the DPI the higher the noise the sensor has to cop with. You have to find the right balance. I would say 800 to 1600 DPI.

Yes, I'm using raw_input 1.
And it seems that I need ~620+ from that calc.

But WHY X-718BK is absolutely OKAY with 400dpi@4 and 4,5 sens?
This is really strange..

EDIT: X-718BK starts to skip if I'll use it 400DPI@8+ game sens, for example (its close to 14cm/360).

Why a point when they are starting to skip is differs so much?

why u 2k14 instead of just 2014 ffs

coz of ut2k4 breh

im not ur bre, frend

im not ur frend, mate