DPI Wizard

Added.

Can't be added due to acceleration and smoothing.

Added now. Was already added Couldn't find a Modernizer for this one, so it can't be added.

Note that you need the Modernizer mod for the sensitivity to work correctly. View full update

Absolutely

I can't make it do 3 decimals for just values below 1, so it will probably cause some confusion for users when the sensitivity is above 1 and output is more decimals than the game supports. I think for these cases it's best to just use the config file calculation instead.

No, you can still achieve MDV 133% by using the calculator as long as it is within the range of the game. The fact that it doesn't scale to MDV 133% by default doesn't really matter as long as you have a sensitivity setting for each scope.

Correct for Widowmaker/Ana compared to Battlefield with USA on and coefficient set to 0 and the FOV set to the same as Overwatch, like this: https://www.mouse-sensitivity.com/?share=0f80832ee4a494a7fc322dcf9d8f1cf1

Overwatch doesn't scale the scopes with FOV, instead it scales with 360 distance. So with the relative zoom sensitivity set to 100 the 360 distance is the same as hipfire. At 50 it is twice the 360 distance and so on. This is for all scopes regardless of their FOV.

Having the same 360 distance for scopes is a bad idea, they will be insanely sensitive and the smallest movement will make the crosshair skip a huge distance making aiming basically impossible. It's also not possible to achieve in most games since it's way above the maximum scope sensitivity. For low powered ADS it might makes sense in some games, and it's just about achievable for the 1.4X in Halo with your settings: https://www.mouse-sensitivity.com/?share=0add873ffe1a7cb36c17110a37f83624 All other scopes will be out of range as you can see. For scopes you typically want to match the movement on screen rather than your 360 distance, as this will make aiming consistent between different zoom levels. The default setup of the calculator matches the tracking speed, so tracking a moving target requires the same speed regardless of zoom:

65 is 200% vertical sensitivity: https://www.mouse-sensitivity.com/?share=8849acd2a92a20c92873064143e9c009

16:10 is already in the calculator

You have to use a whole number yes.

I do still have it, and have been wanting to do more testing for the last four years. But I haven't had the time, as my priority has been analyzing games, updating calculator features and maintaining the site in general. It's still something I want to do though!

Can you be a bit more specific? What are you converting from and how, and how is it different? I checked and verified pretty much everything in Valorant six weeks ago.

This game can't be added due to a lot of acceleration.

Too much acceleration in this game unfortunately, can't be added.

Correct, legacy is there for... well legacy reasons. So you can get your weapons to feel exactly like they did in the old games.

Legacy is MDV 0% with a locked source FOV of 65 4:3 Relative at 0 coefficient will instead scale the scopes to your configured FOV. For 0% it's the same. For any other value it is different, as MDV 100% is targeting the top/bottom of your monitor while MDH 100% is targeting the left/right edges.

Use the whole number in parenthesis when using the config file calculation, so in this example it would be 20:

You have to adjust the scale for ADS and Scope to match your 1x, 2x and 3x sensitivity etc: https://www.mouse-sensitivity.com/?share=7101305e07fd8255634c8fa35a99b0e0

This is a big mistake and will make all calculations invalid. The fact that an aim is unaffected by FOV refers to the 360 distance. Meaning in MW2019 you will have the same 360 distance for hipfire regardless of FOV setting. Ironically for MW 2019 you will not see any change in the output when changing FOV and using the ALL conversion with MDV 0%, since they all scale the same to the hipfire FOV. But there will be a difference if you convert to another game, or if you enable Advanced mode to see all the 360 distances. Not all aims have updated info about this, but aims will in any case be affected by the FOV and 360 distance of the source (hipfire) as well as their own FOV which may or may not be derived from the hipfire FOV.

Ok, if all ADS sensitivity is set to the default 1.0, this is how you should convert it: https://www.mouse-sensitivity.com/?share=b0fe26697baedc883b6c2ddf0213f9aa

What is your zoom sensitivities in Apex?