For some reason you can’t have any other input than round numbers at the moment.
So you can’t have any decimals until it’s fixed.
What you can do to correct any aiming issues, is compensating this difference against your mouse resolution.
Go to Logitech’s G Hub, Razer Synapse, or any other, and make the adjustments from there, understanding that what you experience when gaming, is a combination between Mouse DPI and Sensibility.
As Sensibility is nothing but a multiplier on top of real DPI, what you get is the Relative DPI.
Previous Example:
800dpi x 3.64sen = 2912 relative ingame dpi
So you are gonna end up with either 2400 or 3200, if using 3 and 4% respectively from one another. And that’s not good.
.
Solution until patch:
2912 / 3 = 970 dpi
Basically you grab your Relative Ingame DPI, and divide the number for the Sensitivity value you are allowed to use.
The result is the DPI resolution you need to enter in whatever Software your mouse uses.
And of course, you might still need a few minor adjustments because not all Mouse sensors deliver the same behavior when changing resolutions. The actual feeling and result are not linear.
So you may just add or subtract a few points from the reference.
3 Likes
(You made a mistake in the second calculation. It should be divided by 3, not 3.64.)
IMO easier way to count this is to just start off with dividing the old in-game sensitivity by the new one. You’ll want to end up on a whole number, so 2 works for me since I need to go up from 1.25 (if you increase in game sens you lower mouse dpi, if you decrease in game sense you increase mouse dpi).
2 / 1.25 = 1.6
From there you can go to look at your DPI settings, and divide that by the number we just got.
4000 / 1.6 = 2500
Now we can set the in game sensitivity to 2, and mouse DPI to 2500 to get about the same result. In your example it would be
800 / (3 / 3.64) = ~971 DPI
If you wanted to go up to 4 instead if you can’t raise your mouse DPI any more
800 / (4 / 3.64) = 728 DPI
1 Like
You’re right!
I even got the calculation correct, but then also made the wrong description somehow xD
Thanks!
1 Like
It’s a nice post. I hope it helps someone, and that Blizz fixes it soon! I got used to 4000 DPI, but it just doesn’t feel quite the same on 2500.
Definitely not the same, but at least is not a tragedy while we get a correction patch.
Which is very likely to be on its way
1 Like
i just dont open the settings page. it seems to work fine for me
based on the 2-3 tests i did, it resets when you reopen the settings page. so if i log in ill go into the settings, set my sens back to 2.12 and then close it and play and all is fine.
but really if it did change id prolly not notice since i have played on 2 before
I have my mouse set on 1200, ‘cause usually mice work on 400dpi increments for best performance, right?
I set my sens to 4.5 and now I will have to put it on either 4 or 5 but my mouse won’t have a dpi that’s a multiple of 400 anymore. Not sure if this will be noticeable though.
I simply use rawaccel/interaccel which is a mouse accel program but I use it as a global mouse sensitivity control without accel.
rawaccel is a new one but interaccel is easier to use.(It can automatically adjust the sensitivity per active process)