?
?
700405
1 - 8 of 8 Posts
I have a question (a different question than the one I asked above, which has been solved already (obviously lol)):
Which value should be put into the CPI field - is it the DPI setting you've selected in your mouse software? (Counts Per Inch = Dots Per Inch)?
I guessed yes, but when I put 12000 in the field to match my mouse, the speed results I got in m/s seemed way too slow. Like 10-20x (est.)
Enhance pointer precision - this.. thing... should have disappeared once standard optical mice became able to allow accurate movement (within a pixel or two) over the entire desktop without the user having to pick up their hand and/or move their wrist the entire time. Obviously I disable this, because, for some odd reason, 20 years after capable optical mice became ubiquitous, this relic is still on by default! Side note: determining how far the mouse will travel by a combination of both distance and speed traveled over that distance, seems like a way to screw up one's coordination, especially if unaware of the "enhancement" process
Next, also, although I have my mouse set to 12000DPI, I have my mouse speed setting in Windows set to 5 (options are 1 through 20, but settings over 10 are like digital zoom, so not useful). I do this separately from the Control Panel page where the pointer precision option is, because the precision of the cursor speed slider in that area isn't as precise (lol). You only get 2, 4, 6, 8, 10, etc. there. Does this need to be set to something specific?
I was thinking yes, but when I changed the program's setting from 400CPI to 12000CPI, the x count and y count seemed to show the same values for the same movement, so I don't know...
Joined
·
1,208 Posts
Thanks for the pointer (pun intended lol)
Ah, I see what you mean - you count the lowest option as 1 and not 0, so 6 is middle. Yes, I've heard any further up than middle (6/11, 10/20) reduces mouse accuracy. I always thought that lowering the sensitivity below center in Windows while increasing sensor resolution fed more data to the process that controls the cursor - basically using sub-pixel accuracy. You're saying that's not the case?
Joined
·
1,208 Posts
@mike7877
Yeah we usually start counting the notches from 1 hence 6/11 is how it's always been referred to in this and other mouse communities. Above that you will get pixel skipping.
Below, windows will divide the mouse data to recalculate speed by not moving the mouse on certain counts effectively giving a less consistent mouse response.
Cmos mouse sensors are not accurate at high cpi due to optic limitation in relation to signal to noise ratio, so the lower the better.
Also you need to differentiate between a 2d and 3d game environment. In 2d there is obviously no such thing as sub pixel accuracy.
In 3d there is no direct correlation between pixels and camera movements.
The camera moves in angular values that may or may not be smaller to the angle represented by specific pixels.
So don't think about pixels in the first place, and don't worry, 99.9% of the times the minimum camera movement is smaller than the first pixel next to the center of the screen on current day setups (for what that is worth, which is not much in the first place lol).
Anyway that is based on cpi/in-game sens. Leave windows pointer speed out of it as it's just multiplying/dividing cpi.
On top of that, most modern games use raw input and bypass pointer settings in the first place.
Yeah we usually start counting the notches from 1 hence 6/11 is how it's always been referred to in this and other mouse communities. Above that you will get pixel skipping.
Below, windows will divide the mouse data to recalculate speed by not moving the mouse on certain counts effectively giving a less consistent mouse response.
Cmos mouse sensors are not accurate at high cpi due to optic limitation in relation to signal to noise ratio, so the lower the better.
Also you need to differentiate between a 2d and 3d game environment. In 2d there is obviously no such thing as sub pixel accuracy.
In 3d there is no direct correlation between pixels and camera movements.
The camera moves in angular values that may or may not be smaller to the angle represented by specific pixels.
So don't think about pixels in the first place, and don't worry, 99.9% of the times the minimum camera movement is smaller than the first pixel next to the center of the screen on current day setups (for what that is worth, which is not much in the first place lol).
Anyway that is based on cpi/in-game sens. Leave windows pointer speed out of it as it's just multiplying/dividing cpi.
On top of that, most modern games use raw input and bypass pointer settings in the first place.
1 - 8 of 8 Posts
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
-
?
