DPI Wizard

Can you post a link to your conversion?

It depends on your settings (FOV and conversion setup etc), what exactly are they? For instance using 360 distance or vertical match (if the vertical FOV is the same) will produce the same result regardless of resolution/aspect ratio. For vertical match the sensitivity in the 16:9 portion of your monitor will stay exactly the same, and for 21:9 the extra width is just added on without affecting your sensitivity, just how much you see.

Set the MDV percentage to 80 instead of 63.1 and all the numbers will be re-calculated.

It's says where to find it in the notes: You need to enter the total change in turning speed according to your armor as "Sensitivity 1".

Done

Added both single player and multiplayer sensitivity!

Ok, if you do like this you'll see that the setup calculates your Ashe sensitivity, and this is also used for Apex.

1. If you don't get any red warning in the output telling you that the FOV range is unknown, the auto FOV feature will use the rounding supported by the game. 2. Monitor Distance is generally preferred. 3. If the FOV is different you can only match one aspect of the sensitivity, and everything else will be different. MDV 0% is generally preferred since it keeps the tracking distance the same. 4. Yes, but make sure you also configure the game with the calculated sensitivity. 5. Some like it, others don't.

This game currently has a lot smoothing and no option to disable it, making calculations impossible.

Predator: Hunting Grounds is added

Another game where the devs thought a sensitivity slider with no numbers is a good idea...

Do you mean the sensitivity for Ashe is 53.79, or that you have 53 for Widowmaker/Ana and 79 for Ashe? The reason I ask is because 53.79 for Ashe is a bit slow, and 2.5 for 3X is Apex is very fast.

Tannenberg is added!

Hipfire and ADS sensitivity added!

Was an error indeed, updated it now

83.33 is rounded down to 83 because of how math naturally works. In-game sensitivity is inherently inaccurate because of the lack of decimals, so use config file sensitivity if the 0.4% difference is important This is a workaround to account for the fact that ADS maxes out at hipfire's 360 distance and can't be faster. In your example you are trying to match ADS in R6 to hipfire in CSGO using MDV 0%, but the ADS FOV in R6 (81 vdeg) is higher than hipfire in CSGO (73.74 vdeg). This results in the 360 distance for ADS in R6 being around 20 inches, but your hipfire is already set to 22.44 inches so the match is impossible. When this happens the calculation throws 101 in there to trigger an out of range error indicating it is an impossible calculation.

This will be the same distance to turn 360 degrees. The speed, i.e. how fast stuff move on your screen compared to how fast you move your mouse will be different.

Still a ton of smoothing in this game unfortunately, not possible to do any calculation

Last Oasis is in!

You can do like this to convert ADS to ADS using 360 distance and ACOG to scopes using MDH 180% which is what your 83 ADS sensitivity is.