DPI Wizard

Looking at it now, it has a really weird sensitivity scaling.

Added calculations for Scoped Assault Rifle as well!

Use Viewspeed since they have FOV's pretty close to eachother any way.

Targeting FOV is 80, and should be loaded automatically. If you have saved a Fortnite input earlier, it might have the old values saved, if so clear the input and select it again. The 45 degree FOV was only for aim calculations that used the same sensitivity as hipfire. I removed it when they added scope and targeting.

Lower is slower, 0.1 basically means "distance/0.1". Divisor would be a more appropriate name than multiplier

Added Save the World and Battle Royale as separate games. Will add more scopes when I get them analyzed.

I only checked BR, PVE might still have the old sensitivity and issues actually.

No, just the line in the output that actually says "Ratio:" (Only visible when selecting Monitor Distance).

Yes, you would just get a wrong ratio in the output, but the sensitivity calculations will be correct.

Aha, the Monitor Size for the game you are converting to is actually not in use, the input size will be used for the calculations. Note that the monitor size is not used in any sensitivity calculation, it's just used to give you ratio output like for instance: Ratio: 1 inch mouse movement = 2.7452 inches crosshair movement

The Monitor Distance percentage selection is only available when you have Monitor Distance selected. It's irrelevant for Viewspeed and 360 Distance. Viewspeed uses a somewhat dynamic formula so the result will be close to Monitor Distance 70%.

It's an option for the game you are converting to, in the heading that looks like this:

Updated! And they have fixed the report rate/acceleration issues it seems.

Nice, I'll update it later today.

Everyone has their own preference, but setting them to +3 means that actually nothing on-screen will be matched. The matching with +3 is beyond the edge of the screen.

All scopes and aims are by default in the game matched to 100% Monitor Distance. Meaning having the same value for targeting and 2x scope = 100% Monitor Distance match.

It's an issue like you say, for something like BF3 with FOV 85 or so to 120+ for a Quake game. You generally want to have the full range of turning when not aiming, so the actual aim is less important than knowing a 90 degree turn by muscle memory etc. Ideally for consistency you would want the same FOV in all games, but that is not always possible or even desirable.

If you are converting hipfire to hipfire (and targeting for PUBG) you can use 360 distance so you have a consistent movement for turning 180 degrees etc (others works as well, depening on your preference), but for scoping and scopes you must use Viewspeed or Monitor Distance.

Vehicle Mouse Sensitivity: 28 Cavalry Mouse Sensitivity: 43 Tank Sensitivity: 139

I would suggest trying 8.33 in Overwatch, this is matched to osu! using 75% monitor distance, which matches well with the play area of osu! Set the Widowmaker (sniper) sensitivity to 45 to achieve the same match: PS! I'm assuming you also play Overwatch with 1366x768 and with FOV 103, if not make the necessary adjustments based on these screenshots.

Start by calculating hipfire sensitivity for BF1. Since the FOV's are so close between these games and you are using zoom sens 38, I'm using Monitor Distance 0% for all conversions (which is essentially the same as 38) Next is the scopes. If you use USA, this is really simple, since we want all scopes to match Monitor Distance 0%. Simply input the hipfire sensitivity from the first calculation, set the coefficient to 0 and the multiplier to 100, and the zoom multiplier will also be calculated to 100% for all scopes: So to sum up, Calculate hipfire sensitivity, leave Soldier zoom sens and all the X.X0 Zoom sens at 100%, set USA coeff to 0% and you're good to go!

Added with hipfire, ironsights and scope sensitivity. View full update