DPI Wizard

I've replied in the game thread.

You can't do it directly, but if you start with this: https://www.mouse-sensitivity.com/?share=f841456ba2a9f19e80648584759ed7e6 and adjust the sensitivity until you get your desired "X inches mouse movement" in the output you will get there. Then you can use this for all conversion with MDH 100%.

Just change there and update the FOV, that's all.

Sounds like maybe an issue with either your mouse driver loading a different DPI, or maybe some game setting you have modified that impacts the sensitivity (like m_yaw?). Are you using any mods to change FOV or something like that?
These games use the same "standard" sensitivity as CSGO etc, so it's a well known formula.

No problem, I hope you enjoy our service!

This is what I assumed yes, with this you get 4:3 Stretched, to set up the calculator to match this, do like this:

It's not very normal or intentional by the developers of the game, but it happens in quite a few games. It's the same issue if you use a mouse.

Correct on the ADS. For best hipfire accuracy, use the config file calculation and set both the MouseYawSensitivity, MouseSensitivityMultiplierUnit and DefaultFOV based on the output from this:
https://www.mouse-sensitivity.com/?share=185fdd1e576e2de9925e1abea3b78d28

This is added now.

You have done it correctly. The FOV for ironsight is less than half of hipfire FOV, so the 360 distance is over twice as long. It might feel slow if you're used to turning around while ADS'ing, as MDH 0% is optimized for tracking a moving target. If you use ironsight while e.g. going inside buildings and turning around corners etc, 360 distance might be a better option. It all depends on how you play and what you prefer though.

Correct, but depending on your preference, hipfire with MDV 0% will either feel very slow or very good since the FOV difference is so big. If it feels slow, stick to 360 distance instead.

If you mean the fields with "Monitor Distance", then no. Just in this field: 
Ps, check out the Instructions, everything is explained there

Everything in your calculation is essentially already matched, they all have the same tracking speed.
If you want to match them differently to the 6x, set the 6x as the source aim with the sensitivity from the calculation, and set the conversion methods to what you want to use.

It uses MDV 0% with a fixed base FOV of 65 Hdeg 4:3.
The easiest way to use this for other games is to set the "Convert from" game to this FOV and use MDV 0% like this:
https://www.mouse-sensitivity.com/?share=7d531ae54b158d0b6044fda9cf9615cd
So just change the "Convert to" game here and you should be good!

My Spanish ain't too good, but if you're asking what I recommend for ADS and scope, it would be MDV 0%.

Sorry for this, working on some fixes and this was an unforeseen effect. I've rolled it back now

Check the game notes

 

Usually the recommended way to match ADS and scopes is using a different method than 360 distance. All the other methods are matching the sensitivity based on what you can see on you monitor, for instance MDV 0% will match the tracking speed between all aims. MDH 100% will match the flick distance to aim at something at the edge of your screen.
However, for low powered ADS aims it some prefer to use 360 distance as you in many cases run around while ADS'ing, and by matching 360 distance you have the same movement when turning around corners etc.

What do you mean by actual numbers? The ADSMouseMultiplierunit? You can only set one ADSMouseMultiplierunit, it can't be set for each scope. So you can select to calculate this in the special options, the purpose of this is to get one scope perfect while the others have to be off by a small amount due to the lack of decimal support for the individual scope sensitivity values.

That's mostly up to what you feel is best. 360 distance for consistent navigation (turning around corners etc), MDV for consistent aim based on what you see on the monitor.

I think you have messed up your conversion from old to new somewhere, it seems like you have doubled the ADS values.
Here's from the official R6 conversion:

And here's the equivalent in the calculator (the 12x is off because it scales differently than the other scopes):
https://www.mouse-sensitivity.com/?share=c1100b086a36d32e097df1e5564e3984

You just need to set it to MDH 100% instead of 0% and it will do what you want:
https://www.mouse-sensitivity.com/?share=92946bdbdc96eccd481c73ff9ca7f0ea

You need to measure the 360 distance in counts, and the exact field of view in counts and do the math. The game needs to be completely free of smoothing and acceleration, and if the view is 3rd person or the center of rotation is slightly behind or in front in 1st person it needs to be done a place where you can see very far.
It can be quite tricky. If this is a Chinese game I can get access to I can add it to the calculator if possible.

You already asked and got an answer in this thread, no need for a new one 

Ok, you can try like this: https://www.mouse-sensitivity.com/?share=59344ba00b7f6766f32f9995f67a0f4b
For hipfire sensitivity you have to choose either MDV 133.3333%, or 360 distance.