DPI Wizard

That's what is in the calculator now, but given scope/aim names instead of the config file variable name. But I'll look into making a whole separate calculation for in-game only, as a lot of people probably prefer that.

BF4 should already have calculations for all aims. Or did I miss any?

Excellent, thank you! Added it as separate aim, so people can choose in-game settings (quite inaccurate because it is in steps of 5), or file settings.

America has fallen! View full update

Halo 5: Forge has a ton of mouse acceleration at the moment, event with "raw" mouse input on. So much that I can't make any sensible calculations :/

Thanks a lot, this was the problem! Had to manually get it, but now Halo 5 is downloading

Tried, and just get this

Why is it not available to me? Is it only released certain places?

Basically you should fill out the calculator like this (monitor size is not important for the sensitivity calculation, just the ratio): But change the "Match At" value to your liking. What that means is: at 1% small movement around the cursor will be equal to 103 FOV, while at 100% moving all the way to the edge of the monitor will be equal. 50% is then obviously a middle between the two. It kinda depends on what you prefer, snapping to a player at the edge of the monitor, or tracking a player in your sight.

When you change FOV in Overwatch, the 360 distance remains the same, which is why it feels too fast. You can keep the same feel with the Monitor Distance calculation, but you have to choose where on the monitor to match the sensitivity, from 1% to 100% between the crosshair and the edge (see the Monitor Distance video on the front-page for more info). Tell me the % and I'll tell you the magic number

Looking into this... ...and this now. Paragon is unfortunately in a poor state sensitivity-wise at the moment, with a broken slider and acceleration. It will probably be fixed at some point though, will check it now and then. As soon as my Windows Store starts working, I'll take a look at this...

I've chosen to set the coefficient to 0 just to eliminate the variable. As soon as you start matching with different percentages the coefficient doesn't scale the same with all sights, but it is true that it does a fairly good job with the default settings. Regarding BF1, haven't looked at the aims and USA yet.

I will look into it tomorrow, only checked the base hipfire sensitivity so far! But for ADS, also note that you have the scale with FOV option. Also, are you matching 360 distance or monitor distance (which is recommended!)?

Yeah, Overwatch have a minimum sensitivity of 1, so when the calculated result is below that, it tells you the maximum DPI to stay above the minimum

This is exactly why you should play with a high DPI, but the benefit is diminishing. By that I mean there is not much to gain going from 6000 to 8000 DPI (although it is in theory smoother), but going from 400 to 2000 is huge in terms of smoothness. It also depends on your 360 distance/ratio though. Increasing DPI while maintaining the sensitivity is actually why this calculator was created in the first place. In some games the sensitivity scales directly with the DPI, so if you're doubling the DPI, you can just half your sensitivity. This is not true for all games though (like BF 3, 4 and 1).

The game for some reason calculates the HFOV for 4:3 resolution, and does not take into account your actual aspect ratio. If you select Horizontal Deg. | Res Base and enter 102 as you want, you'll get GstRender.FieldOfViewVertical 69.57 which is what you should configure (Assuming you play with a 16:9 resolution)

It should be exactly the same. How are you feeling it being different?

I know, adding it to remove any doubt. Will also add all aims eventually

Added support for all aims, multipliers and coefficients, as well as calculations for both in-game and config file sensitivities. View full update

Added with the in-game sensitivity. This setting is quite unaccurate, a HEX calculator is in the works. View full update

Try 75, that's matching movement from hipfire at 50% of the monitor distance.

Only MouseYawSensitivity and MousePitchSensitivity. The MouseSensitivity should disappear from the config file when changed in-game I think. Also make sure bot MouseSensitivityMultiplierUnit and XFactorAiming are set to the default 0.02 if you are using the simple calculations.

Working on this now, problem is that each percentage on the sensitivity scale has several notches.