DPI Wizard

MDH and MDV is essentially the same, but you have to convert between them using the aspect ratio of the monitor. So for instance MDV 100% on 16:9 is the same as MDH 16/9=177.7778%.
The benefit of using MDV is that you usually want to keep your vertical sensitivity the same regardless of aspect ratio. Imagine a square box that covers the middle of your monitor, you want the sensitivity within this box to be the same. If your aspect ratio is wider, then there's just more to view, but the sensitivity within this box stays the same.
If you use horizontal, then going from 16:9 to 21:9 will drastically change your sensitivity, instead of just keeping the same sensitivity within the 16:9 portion of the 21:9 monitor.
The reasons for going above 100% is usually just to match your preference. If 100% is too slow, there's no reason you can't try 200%. It's correct that it's matching a point outside of your monitor, but it's still a valid and consistent conversion.

Thanks for notifying me, I've updated this now.

The unit will default to inches if your browser language or site language selection (in the bottom) is set to "English (USA)". In all other cases it will default to cm.

Switch to default mode, it's hidden i simple mode because it confuses a lot of people

It depends on the game and which axis you measure the movement on.
Some keep a persistent horizontal FOV, some vertical FOV, some changes both, some keep the same 360 distance, others have the 360 distance either affected by the change in FOV or in some cases even the change in horizontal or vertical resolution.
There's a lot of different ways this can work, so using the calculator is the best way to see what actually happens.

The FOV option is added now.

3x is added and FOV is updated for all the scopes.

Yes, they are the same

Reload and try again now

The calculator can't guess your sensitivity settings, so obviously you have to enter it somewhere... And for the conversion to be correct, the closest matching conversion method has to be reverse-calculated.
This is correct yes, but if you set the coefficient to 1.33 instead the zoom sensitivity values will be closer to 1 and more consistent across all the different aims.

A lot of games, especially those based Unreal Engine 4/5, have smoothing enabled by default. And if you don't disable it, 125 Hz is in most cases the only accurate option. Using 1000 Hz results in extreme negative acceleration and terrible accuracy.
But in normal cases the accuracy should be exactly the same, but with a (theoretical) less smooth motion.

The one with the highest accuracy (the top one) is the best.
Correct, this way the accuracy is much higher.

Wasn't too much to update, so it's already done.

Sorry, my bad I was looking at the FOV Type in the game section, not the Auto FOV one. I found an issue there so it should be resolved now

Riotfall is updated and scope sensitivity added.

This is mentioned in the game info section.

 

It won't work, as the available zoom levels varies widely. Some games might have 2 low zoom ADS scopes and one 40x scope for instance, where the average will be completely useless.

The text is a bit misleading. Monitor Distance Vertical is showing the vertical distance from top to bottom, while Viewspeed Vertical is showing left to right. It might be a bug that Viewspeed Vertical is showing the horizontal distance and not the vertical, I'll have to look into that.
Either, this does not affect the actual  calculations as it is displayed just for information.

All these parts are correct.

The calculator suggest the lowest possible DPI based on the sensitivity range of the game, as in the first link where it suggests 1440 DPI. But the calculator doesn't know you have the possibility to configure 1440, so it can't just assume you are using it. Some users might have to go to 1400 DPI, others 1000 DPI etc depending on the driver and supported DPI resolution. The DPI used for the calculation is the one entered, there is no way around this without causing a ton of confusion.
 
The multiplier is based on the entered DPI. If the entered DPI is causing the sensitivity to be out of range, the only solution as it is right now is to suggest a DPI that causes the sensitivity to fall within a valid range. Technically it could also suggest a multiplier, but there's no way to enter a DPI multiplier into the calculator, you need to enter the effective DPI.
For this to work the way I think you want we would need a new DPI multiplier field, but I'm a bit reluctant to add more fields to the calculator covering rare edge cases, as it mostly causes confusion.

Hey! Answer is here  It is always shown for ADS and scopes in advanced mode.
And the original suggestion is here, but it doesn't contain any math regarding how it's calculated.

There's a link on the front page about what it is. It's for reverse calculating your existing sensitivity to find the correct (or closest) conversion method.
It's not linked to the swap button between the games, this button swaps the output game for the input game. Although this swap button is somewhat confusingly also labelled as reverse in some cases, it will be re-labelled swap in the up upcoming updates.

Which weapon are you using in Crossfire? I've added a few snipers now, but the sensitivity relative to your conversion is about the same.
Also, how is the sensitivity too slow? Are you expecting the same 360 distance for the zoom in crossfire as in CS2?

This required some thinking since the vertical sensitivity can be different than the horizontal for the closest match, but I managed to figure it out! Coming in the next update:

I just tested all the scopes, and everything is spot on. If the calculation is out of range there's not much you can do other than try to tweak the base mouse sensitivity, but that has a limited impact.