As this thread was mentioned on the day9 daily, I'm going to add this disclaimer:
When I set out to write this post I thought that it would be fairly straight forward to communicate what I was trying to say, however I was wrong and as a result this thread can be very confusing for non-mathematically minded people.
The general gist of it all is basically sc2 mouse settings that are multiples of 5 are inconsistent, and so you should avoid them. The other thing is that there are not as many different sensitivity settings as you think (there are not 100, as would be implied by a slider that works with percentages). You'll also find a lot of discussion on pixel precision and 1:1 ratios and stuff, and if you're interested you can read on, however I don't give a crap about pixel precision or 1:1 ratios or any of that stuff because as far as I'm concerned all of that is meaningless in the face of having a 'comfortable mouse speed'. However the findings are still relevant to myself, because although I don't care about pixel precision, I do care about having the same mouse speed today and tomorrow and the next day. If you're the sort of person that doesn't keep count of how many sugars they put in their coffee, then that's fine too.
Ideally you want your sensitivity as 6/11 (1:1 ratio of mouse movement to cursor movement):
http://www.teamliquid.net/forum/viewmessage.php?topic_id=142026, and the thread tells us that 50% is the same as windows' setting of 6/11.
I had to re-write this post a few times because I kept finding out new stuff. At first I wanted to test if 50% or 55% is 6/11 because:
windows sensitivity is n/11
starcraft2 sensitivity is n/100
100/11 = 9.0909090909090909...
If you want you sc2 sensitivity to be the same as your windows sensitivity..
windows sens x 9.09 = sc2 sens
6 x 9.09 = 54.54 (55% when rounded)
However I did some tests with MouseMovementRecorder (you can find it somewhere in here) and I kept getting weird results.
When set to 50% there were sometimes lost pixels and other times there weren't. (green means pixels mean lost pixels--movement that was picked up by the sensor but not performed with the cursor--this happens when you go below 1:1 ratio of mouse:cursor movement, a.k.a "6/11")
at 55% there were, again, sometimes lost pixels, sometimes no lost pixels. At this point I'm thinking maybe it rounds down decimal places?
at 51%--54% there were never lost pixels. (black=1:1 [6/11])
But this implies it also rounds up decimals :/
I kept playing around to see what was going on and I found that there are in fact fractions of percentages on this setting (i.e. there are more than 100 notches). I dragged the slider very carefully, and above ~50.5% you get a perfect 1:1 ratio, but below this you get lost pixels.
at 55% you get the same; on the lower end of the 55% setting you get perfect 1:1, and on the right-hand side you get red in the tester program=above 1:1=extra pixels thrown in.
This is pretty strange. They have a sensitivity slider with over 100 notches [probably as many notches as your horizontal resolution--in my case 1280 positions on the slider] but windows only recognises 20 different settings, so really the setting only functions at intervals of approx. 5%.
Another thing: if you're like me and have a 400dpi mouse (logitech mini wheel optical, etc.), I've found 8/11 to be a good setting (8/11 is not as bad as 7/11 or 9/11, and definitely 11/11, because 8/11 is an exact 1:2 ratio [skips every 2nd pixel in order to move twice as fast], and nothing in sc2 is 1 pixel =p)
8 x 9.09 = 72.72
There are as many notches as there are pixels drawn on your screen, yet windows only recognises 20 different mouse settings--that is, 5% intervals.
It's kind of hard to figure out the exact border lines of the intervals, so I suggest avoiding multiples of 5% (50%, 55%, 60%, 65%, etc.) because the borders will be fractions of these numbers. Set your sensitivity between multiples of 5 (theres no difference between 51%--54%; 71--74; 96--99 [and 100]; etc. There is no 100.0000000000001% or 0.9999999999% so it works out no matter what your screen resolution is).
The reason why multiples of 5% are inconsistent:
- There are fractions of percentages on the slider, however the displayed whole number percentage only changes when you hit a new whole number, whereas the computer rounds the numbers---so, you are at 49%.. you slide it up to 50%... then you slide it left a few pixels. It displays "50%", however you've actually set it to 49.1%. The computer rounds it down to 49 and you see "50".
People seem to be confused. I'll try to summarise some stuff.
- Your windows sensitivity doesn't matter at all. SC ignores it.
- There are only 20 mouse settings in starcraft2 (1--5, 5--10, 10--15, etc.), even though there more than 100 notches on the slider.
- for 1:1 ratio of mouse movement to cursor movement, set your in-game sensitivity to anything between 51%--54% [with "enhance pointer precision" turned off in windows] -- not 50% as people previously thought (although it sort of is 50%; it's just that you can't see what the decimal point on the number is so it's safer to use 51--54) (that is, 51%, 52%, 53%, and 54% are all exactly the same mouse speed).
If you just want 1:1 pixel ratio of mouse movement to cursor movement stop here.
If however 51--54 is too slow, you should sacrifice the negligible 1 or 2 pixels of accuracy for a comfortable mouse speed. However, be careful that you avoid multiples of 5 because there are invisible decimal places that can make a big difference. (Theres no such thing as "exactly 80%". You're either playing at about 76 or about 84).