Posts by Glymbol

A9500 isn't good to measure absolute distance, it is too dependent on movement speed. On some surfaces A3090 tracks up to 4m/s.

2 * PI radians = 360 degrees 6.28... / 2 = PI With your second question we are returning to jayfkay's question about the table: http://www.overclock.net/t/1251156/an-overview-of-mouse-technology/50#post_20101884. Even at very high...

jayfkay Yes cm/360 should be the same at different FOV. HAGGARD 1. When sensitivity is lower there is more possible "directions" to aim. Try sensitivity: 1.0 m_yaw 90 - there will be 4 possible directions, but with sensitivity 2.0 there...

Quote:Originally Posted by HAGGARD How is this a matter of preference though?The difference is: the lower sensitivity, the higher aiming precision (potentially). Quote:Originally Posted by HAGGARD Where does this value come...

Quote:Originally Posted by jayfkay does this table actually mean that for 1920, the ideal pixel precise sens has to be between 1.357 and 2.713???It means you won't need sensitivity below 1.0 to be pixel precise even with very high...

Abyssus is better in this, it will start double clicking .

Don't you think that sensor 6000 or 9000 FPS isn't that important if mouse is polled only 125 times a second and you see on screen result even less frequently?

I don't use 800 DPI, claw grip my G400 mostly and it's good for me.

I like G400 more than Sensei but it's not very good at the highest 3600 DPI setting (some jitter). G400 is fine at 1800 DPI though, if it's enough for you.

Ah, there's even your post on the first page of that thread .