DPI Wizard

If your source is CSGO, you should use that for all your conversion, so do like this:
https://www.mouse-sensitivity.com/?share=d737927808ab2249edac068db8b383ca

It's definitely a wrong representation in the game, the vertical FOV stays the same regardless of aspect ratio.
Maybe it's done because 16:10 is regarded as "tall" rather than "wide", but it's dead wrong.

Correct, and 24 in Super People is 50.4644, which is why there's a slight different.
The best method is to always use the same source, so if Warzone is your preferred source you should use this. You won't get MDH 0% anyway since Super People lacks any decimals so the precision is really bad.

This looks correct, but there's a bit of discrepancy due to the lack of decimals in the in-game sensitivity.
The only solution to this is to set the sensitivity in the config file instead.

The coefficient sets the sensitivity for all scopes, so it's just matching what CSGO uses. This way you don't really have to set the sensitivity for each individual scope, instead the coefficient controls it all.

79.586, the FOV shown in-game in Apex Legends is wrong.
Correct!

This is correct, there was a bug in the calculator with different aspect ratios after the game was updated to Overwatch 2. I've fixed this now so everything should be correct.

I don't have any issues here at the moment (Ubi version), but raw input has been bugged in the past so it wouldn't surprise if there's still issues in certain cases.

It should work now, I cleared some broken entries in the database. Your notification counter is reset for now though, but will show up again when you get new ones.

MDV 0% will do this, here's a random example: https://www.mouse-sensitivity.com/?share=8e46fc657b13babd0d367e985c64f59c

This is correct, but the exact MDH value you should use depends on the MDV value. For instance if you used MDV 100% you should use 100*16/9=177.7778% for MDH (if going from 16:9 resolution).

I found the issue, you need to make a new order as the Steam Gift Card option was recently added.

This is explained in the instructions. Basically all you do is to match the FOV Type and the value, and see the output for what to configure. If the FOV Type is Multiplier, use Vdeg.
Here's an example:

You have to change the conversion setup to match your settings. So you have to use Default mode instead of Simple, and adjust the ADS and scope conversions.
I've done it for you here to best match your settings (MDH 100% Scale 80%):
https://www.mouse-sensitivity.com/?share=f9e4d481a069bf5a040236a6705438d4

The "All" aim option is there so you don't have to do calculations for each scope individually.
So you need to figure out what your current game settings equate to in the calculator. In your case it's pretty easy, coefficient 1.33 with zoom sens 1 is MDV 133% with scale 100%. So just replicate this in the calculator, and everything else should be correct
https://www.mouse-sensitivity.com/?share=810a0f53d4370e27912784dc36b18592

At some point they have enabled smoothing in this game, so you get a lot of negative acceleration with high polling rates. I have updated the game info with instructions on how to disable it, this should solve your problems.

In the first one you are getting 40 cm for hipfire, while all the others are converted using MDV 0% (so the tracking speed is the same for all the aims).
In the last one you are directly calculating what 40 cm is for the aim.
Hope that clears it up

If you want to keep the horizontal pixel ratio the same, you can calculate it like this:
https://www.mouse-sensitivity.com/?share=206ff4da8ff6c5dd0658083c2b5c0554
For games with a regular sensitivity scaling like CSGO it's just to set it to 75% of the original value.
 

You are using the wrong FOV/location in Apex. The config file FOV is completely different from the in-game FOV, so switch location to "In-game" and it should work better

When you reverse the calculation, you also change the source for the calculation from FOV 103 to 120, and if you're using 360 distance for hipfire you will get the wrong sensitivity for scopes.
If two scopes are the same FOV you would expect them to also have the same 360 distance, so they are identical.
Since you can change the Zoom FOV in QC it's quite easy to show what's going wrong. Here's I've set the Zoom FOV the same FOV as Ashe ADS:
https://www.mouse-sensitivity.com/?share=b5a237f18164a96df153c2ddcfe3f9e9
So the FOV and 360 of Ashe ADS and Zoom FOV in QC is the same at 40 vdeg and 82 cm.
But if you reverse the calculation, both will change to about 101.5 cm since you change the source:
https://www.mouse-sensitivity.com/?share=e621b3807a008120fd609a583691649d
So the scopes are no longer like you want them in OW2, but completely different. Using the same source is key to keeping the scopes the same between games. But yes, you will get some weird results when the hipfire FOV is locked, especially when it's very low compared the the other game.

Actually I forgot how this game works. It will force 16:9 regardless of aspect ratio, so you should choose 16:9 in the aspect ratio field if you are playing with a different aspect ratio. There are workarounds to stretch the image though, like through the driver, so you have to choose the correct aspect ratio option.

There was a bug introduced with the latest update, try again now and it should work.
Thanks for reporting!

Monitor Distance - Dynamic is now live, let me know if you find any issues!

You can do like this: https://www.mouse-sensitivity.com/?share=511a55e13315803937c4b13988a5414d
This will keep the aim you convert from the same, and the hipfire and everything else will be adjusted to the conversion you select.

Fixed!