![]() I'm not going to answer questions about these drivers because, really, to do so would require me to googe it.ĥ) If you are madly in love with your windows mouse setting, and want to know what the equivalent setting is in starcraft2 - multiply the windows mouse speed by 9.09 to get the equivalent.Īnother 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, and nothing in sc2 is 1 pixel =p) These other drivers will probably affect in-game settings. (this is why the thread has its title - people might go to a LAN and set their mouse to 50% and unwittingly be using 46~49 due to rounding).ģ) Windows' mouse setting has no impact on the in-game setting (this is all mentioned in the thread I linked to though).Ĥ) RAZER/SETPOINT/WHATEVER drivers are not windows' drivers. I personally use 82%.ġ) There are only 20 mouse settings (the 100 percentages are divided into chunks of 5), even though there are over 100 notches on the setting (there are invisible decimal points).Ģ) The 'edges' of these 20 settings are the numbers that are multiples of 5 (50,55,60,etc.) so you should avoid these numbers because you might land on a decimal point that secretly rounds up/down your setting to a setting you don't like. I linked to the thread that deals with that sort of stuff. I actually wasn't intending to tell people to use 1:1 ratio sensitivity or even discuss it. I actually think it might be that the displayed whole number percentage isn't rounded, but rather only displays a new figure once the slider arrives at a new whole number (so if you're at 55 and you slide it right by 0.9 it will still display "55", while the computer interprets it as 56). This stuff is surprisingly hard to express =p I just hope it is clear for everyone.Īnd not least, great findings, gg to the op. This was a lot more difficult to explain than I thought. But just to make sure it will actually be 65%, in the game menu set it to 66% (65+1). In order to avoid this, add +1 to the value you ended up with, after you calculate the value needed to get your dpi equivalent.Īs an example if you have an 800dpi mouse but you want to play at 1000dpi you will need 65% (65/50*800=1040 - the closest value to 100dpi you can get to). So it will use 45% although it will display 50% in the game menu. So if you actually select, lets say, 49.6 with the slider the interface will display 50% (rounding it up) but the value used by the system will still be 49.6 and rounded down to 45%. The SC 2 user interface use another rounding by itself. So that brings us back to 100/11=9.09 I guessĢ. Should we assume 0% is the same as 1%? It makes no sense for ZERO TO MOVE. I'm testing the difference between 0% and 1% and I can't see any (though I admit it's really hard to tell). I assumed there was no 0%, as IT IMPLIES ZERO MOVEMENT. I had trouble expressing myself though.Ģ) Yeah my bad. Starcraft 2 sensitivity is not n/100, it is n/101ġ) I was just trying to say that if you know your comfortable settings for windows, you can use some simple math to calculate the equivalent in sc2 land. It has nothing to do with the windows mouse settingsĢ. I don't want to sound rude, but the way he tries to explain it is overcomplicated and to some extent wrong, therefore leading to misunderstandings.ġ. I would simply suggest having your windows speed comfortable to you, up to 6/11, if you need your mouse any faster then you need a higher DPI mouse.Īlthough the issue brought up by the op is valid, the post contains some useless affirmations. (Xai)īut mouse marketed as 6000DPI doesn't mean you should use it at 6000DPI. I use 1000hz polling rate, it's got it's benefits. Your precision is entirely down to the hardware sensor of the mouse and relevant hz counts, polling rate. Having a higher DPI does not in any way mean you have more precision. I personally use 3/11 (I enjoy this speed on my desktop), with a 1800DPI mouses, thats technically 450dpi, but.Ģ) DPI does not mean accuracy. IE, it will ignore your mouse registering a right up up right (4 counts) and might do right right instead, missing out on 2 up counts.ĭon't be fooled by "1:1" as a magic number. At lower values it, for example, doubles the counts required to produce a single count. ![]() You shouldn't use above 7+, the pixel skipping raw input being lost.īetween 1-6, you are not losing input. 1) You do NOT need to use 6/11 windows sensitivity. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |