DPI Wizard

You probably want the same 2D distance, right? Meaning same movement to move the crosshair to the edge of the screen. The same 3D distance (i.e. 360 distance) will probably feel to sensitive when aimed. Anyway, the update I'm working on will make this easier

No, both ADS and hipfire use the MouseSensitivityMultiplierUnit as a multiplier. XFactorAiming may be an additional multiplier, I'm not sure.

I've added Hipfire (simple) and ADS (simple) now, they just calculate the sensitivity assuming you have the coefficient set to the default 0.02 Updated it now, it had the wrong variable. "AimDownSightsMouse" is the correct one.

You must enter your current sensitivity, and the calculated value you get is the coefficient, MouseSensitivityMultiplierUnit.

Just added it!

Added with both hipfire and ADS sensitivity. View full update

Correct!

Note that variables like the exact ratio and real FOV may skew the accuracy, but this should be in the ballpark

I don't have zoomed sensitivity for BF3 added, but assuming it's exactly 50% of regular sensitivity (so I input half the DPI), this is what I get in the new calculator I'm developing, so you are not far off

Seems to be canceled now, so I guess you found it

Correct, but remember that you are matching the movement in-game from what you are aiming at to the edge of the screen, to moving the mouse from the middle of you desktop to the edge of the screen. And not a 360 rotation. This is because you are changing the aspect ratio as well I recon. Since the FOV in some games change when you change AR (say from 16:9 to 16:10), the sensitivity also change in desktop mode since it is matching your FOV to the desktop sensitivity

You are not far off! The correct value is 0.43757083. Anyway, I just added it, check the notes regarding the slow mouse movement (packet loss) and acceleration.

I should make a video explaining it, it's on my todo list! But basically, the DPI analyzer is not strictly necessary to consider when calculating sensitivity, just to know what the real DPI is compared to what you configured. This is useful for two things: 1. You can use the real DPI in the calculator to make it more accurate. For instance, if your configured DPI is 400, but real DPI is 440, use 440 in the calculator. 2. If you do not do as mentioned above, you know that the DPI is 10% off, hence the calculated distance will also be 10% off.

You should have a cancel link in the emails from paypal. Or I can cancel it for you

One time forever

I see, that difference of about half an inch is probably due to the mouse not being exactly the DPI you set it to

Did some tests now, it doesn't seem to affect it at all. What exact resolutions are you testing?

Coding is a curse! I get sidetracked all the time fixing small things here and there But I'm about 80% done now!

Couldn't find one, I'll look some more though.

Pretty much everything was changed with this game since I added it. Updated it now, give it a try

Added!

Early Access version added. View full update