|
Hi! Awesome poset, it really cleared out some stuff.
Although, im a bit confused by one thing. I use 11/11 as my windows sensitivity, because having a fast mouse sensitivity and being able to control is the best for RTS in my head.
"8/11 is not as bad as 7/11 or 9/11, and definitely 11/11", i would like to know, why it is, that u think those exact numbers/notches are "bad". Thanks!
|
On April 17 2011 20:38 Krasso wrote: "8/11 is not as bad as 7/11 or 9/11, and definitely 11/11", i would like to know, why it is, that u think those exact numbers/notches are "bad". Thanks!
8/11 interprets one unit of mouse movement into 2 pixels of screen movement. It consistently skips one pixel. 7/11 is a 1.5x multiplier, and 9/11 is a 2.5x multiplier. However, you can't move half a pixel on the screen so sometimes 7/11 will move 1 pixel and sometimes 2. It's inconsistent. 11/11 is a 3.5x multiplier, which is also inconsistent and skips huge numbers of pixels. You're much better off buying a mouse with 3.5x your current mouse's DPI and playing at 6/11 for accuracy's sake.
|
Im playing with 11/11 and lowest DPI settings (1/3). (i dont know much, if anything about mice)
So you're saying im much better off by playing with 6/11 (or 8/11 if i want it faster) and then my highest DPI setting?
..and im guessing 10/11 is just a 3x multiplier?
|
I'm glad this thread exists but I was wondering one thing. If I have my deathadder on 6/11 windows and highest DPI do I lose accuracy when I change the sensitivity on the razer driver? I did some trials in paint painting lines and it seems like it's still a 1:1 tracking, anyone know for certain what happens there?
|
On April 17 2011 21:19 Krasso wrote: Im playing with 11/11 and lowest DPI settings (1/3). (i dont know much, if anything about mice)
So you're saying im much better off by playing with 6/11 (or 8/11 if i want it faster) and then my highest DPI setting?
..and im guessing 10/11 is just a 3x multiplier?
Yes and yes.
|
Does 51-54 Set it to 6/11 (EQUIVALENT SPEED as windows 6/11) or does it simply retain the 1:1 properties of 6/11?
|
On April 17 2011 21:22 storm8ring3r wrote: I'm glad this thread exists but I was wondering one thing. If I have my deathadder on 6/11 windows and highest DPI do I lose accuracy when I change the sensitivity on the razer driver? I did some trials in paint painting lines and it seems like it's still a 1:1 tracking, anyone know for certain what happens there?
Which way do you change it? If you want to change your sensitivity down it might be advisible to do this via the DPI. Lowering the DPI to suit your sensitivity is generally the best. If you want a higher sens you are already capped on DPI so you'd have to do this with the software settings anyway. And then we aren't even taking into account that DPI should actually be pretty low because if your more mouse is more precise, every little bump will get noticed and make your cursor really jiggely and thus inaccurate, you want stability so lower DPI is generally the most desired. But you could make an argument for personal preference, if you are already comfortable and don't want to swap or don't like it when you swap etc.
On April 19 2011 16:42 alewares wrote: Does 51-54 Set it to 6/11 (EQUIVALENT SPEED as windows 6/11) or does it simply retain the 1:1 properties of 6/11?
I believe it retains the 1:1 properties, where it doesn't modify the input again by accounting for the scaling of the sensitivity. I think the speed, as in the feeling is gonna depend on the resolution. If your desktop is in 1920x1200 but you game in 1200x800 then I feel like the speed is gonna differ but if the resolutions are the same, I see no reason not to conclude the speed will be the same, apart from needing to actually try it out to be sure.
|
What if I have windows at 6/11, sc2 at 51%, logitech setpoint 4/11 with 1600 dpi? Is my setup alright with a 1:1 ratio?
|
I read this thread a while ago and after that I always had the sens at like 81%. But then I remembered this last part, about the 1:1 pixel ratio. I knew my mouse would go 1 step higher in DPI, but I never really bothered about it, so I lowered windows sens to 6/11 and raised the DPI. Man what a difference! Everything is so smooth! I have never been fully comfortable with my mouse sens and I could never find the right sens in both SC2 and Quakelive. Now I'm in full control, gibbing everything~
|
I am getting no missed pixels in Windows but in Starcraft II I am getting lots of missed pixels using the mouse recording tool.
Any ideas?
Logitech G5 (no weights), SetPoint 5.10.9 6/11 No accel SCII Sensitivity 54%, windowed mode full screen Logitech drivers, 2000 dpi, 1000Mhz CPU polling rate 1900x1200
I wish SC2 wouldn't override windows and I wouldn't have this problem...
|
United Arab Emirates492 Posts
On May 07 2011 22:19 noproblem wrote: I am getting no missed pixels in Windows but in Starcraft II I am getting lots of missed pixels using the mouse recording tool.
Any ideas?
Logitech G5 (no weights), SetPoint 5.10.9 6/11 No accel SCII Sensitivity 54%, windowed mode full screen Logitech drivers, 2000 dpi, 1000Mhz CPU polling rate 1900x1200
I wish SC2 wouldn't override windows and I wouldn't have this problem...
everybody should be getting red pixels. after the last patch the settings at (51-54percent) are no longer being saved in the variable file. hence you have change it to 51-54percent every single time before you open sc2.
|
If I undrestood this correctly.
For the most precision you should have a 1:1 relationship between your windows sensitivity and your starcraft sensitivity. The thread doesnt say set your windows sensitivity to 6/11 and the starcraft one to 51-54% . What it does say however is that whatever sensitivity you have for windows you should multiply it by 9.090909090...
So if you have 7/11 in windows that is 7 * 9.0909090 = 63.63 and so you should set your Starcraft sensitivity anyways from 61 to 64 because they are essentially the same thing.
OKay, bye.
|
|
Well, so by fiddling around with the mouse motion recorder, with 94% sc2 sens it gives a 1:3 ratio. So like the mouse movement is 2x-1 but pointer movement is 6x -3. So this just means instead of moving 1 pixel it moves 3, right? Is the only drawback to this just how it skips a few pixels? The ratio is constant so the motion would be constant, and on my 2550 pixel wide screen is that really very noticeable compared to a true 1:1? Or are the 2 drastically different and i dont understand?
|
On May 07 2011 22:28 Gunman_csz wrote: everybody should be getting red pixels. after the last patch the settings at (51-54percent) are no longer being saved in the variable file. hence you have change it to 51-54percent every single time before you open sc2. Can you please elaborate?
|
United Arab Emirates492 Posts
On May 08 2011 03:23 Beardfish wrote:Show nested quote +On May 07 2011 22:28 Gunman_csz wrote: everybody should be getting red pixels. after the last patch the settings at (51-54percent) are no longer being saved in the variable file. hence you have change it to 51-54percent every single time before you open sc2. Can you please elaborate?
Well before you set the sensitivity at 51,52,53, or 54 percent in either the variable file or through the menu to get the true 50:50, but now it doesn't work because even if you have them set to those specific numbers the sc2 client just rounds them up to decimal after every restart. for-example 51 will turn into 51.3334, which is not what you want !
The only solution is to manually enter 51-54 in the variable before opening sc2 client, because once you close the client the settings get rounded to decimals.
|
On May 08 2011 07:13 Gunman_csz wrote:Show nested quote +On May 08 2011 03:23 Beardfish wrote:On May 07 2011 22:28 Gunman_csz wrote: everybody should be getting red pixels. after the last patch the settings at (51-54percent) are no longer being saved in the variable file. hence you have change it to 51-54percent every single time before you open sc2. Can you please elaborate? Well before you set the sensitivity at 51,52,53, or 54 percent in either the variable file or through the menu to get the true 50:50, but now it doesn't work because even if you have them set to those specific numbers the sc2 client just rounds them up to decimal after every restart. for-example 51 will turn into 51.3334, which is not what you want ! The only solution is to manually enter 51-54 in the variable before opening sc2 client, because once you close the client the settings get rounded to decimals.
Interesting. What is the file called and the variable name?
Edit: Nevermind found it! Thanks for the help man.
|
Okay I have tested it out trying out 51~54% and I am still getting red in SC2 despite pre-altering the mousesensitivity variable in the Settings.txt file, but no green. Any more ideas?
|
United Arab Emirates492 Posts
On May 08 2011 23:01 noproblem wrote: Okay I have tested it out trying out 51~54% and I am still getting red in SC2 despite pre-altering the mousesensitivity variable in the Settings.txt file, but no green. Any more ideas?
Well then it has to do with your mouse settings or windows settings. Make sure you uncheck "enhanced pointer precision" in control panel. Make sure anything labeled "acceleration" is disabled in you mouse program.
|
On May 09 2011 00:57 Gunman_csz wrote:Show nested quote +On May 08 2011 23:01 noproblem wrote: Okay I have tested it out trying out 51~54% and I am still getting red in SC2 despite pre-altering the mousesensitivity variable in the Settings.txt file, but no green. Any more ideas? Well then it has to do with your mouse settings or windows settings. Make sure you uncheck "enhanced pointer precision" in control panel. Make sure anything labeled "acceleration" is disabled in you mouse program.
Sigh...
Nope it isn't this as I have previously mentioned in my posts above I have I don't have any accel and I am getting no missed pixels at all in Windows, so it isn't my mouse settings or Windows settings..
Anything else?
|
|
|
|