WhoCares?

Added it now.

This is the "FOV Scaling Axis" option in the calculator. It changes from horizontal degrees based on resolution when set to off, to horizontal degrees locked to 4:3 (like cs2 etc) when on.

Nice, makes the list a bit more manageable. Although we still have a couple of outliers with the Minigun and Recurve Bow iron sights.

Hello, please update for Season 6! (new sights were added)

Killing Floor 3  plz

Hello @DPI Wizard.
Newest Update added a FOV slider.

All scopes are added and verified now.

I will hopefully get it done by the weekend!

8X is based on the beta as I haven't unlocked it yet. If it's significantly changed it will be wrong, so I'll remove it until I get it unlocked.

One of the hipfire entries was missing the update, it should be fixed now.
No, it uses MDV 0% now, so going above 0% isn't possible with Mouse Focal Length Sensitivity Scaling on. I'm updating to support it being off now.

Correct, 1 is MDV 100%, and you can't set it above 1 even in the config file.

I've added a "Decimals" special option now where you can select 2 or 3

would it be possible to add calculations for metro 2033/"last light" redux while using Metro Mouse Fix 1.2

Added along with a few other scopes!

A couple of notes just reiterating and confirming what the devs have said:
Hipfire is exactly the same as in MW. Relative coefficient works exactly like in MW. Scopes above 4X works exactly like in MW (meaning they have locked FOV not affected by anything), but they do not match in terms of their power, so a 4X in MW is not the same as a 4X in CW.
CW uses correct optical zoom for the FOV based on a locked FOV of 80 (or almost, it's off by a tiny bit), while MW uses seemingly arbitrarily assigned FOV values. Scopes below 4X and ADS have a very weird scaling when set to "affected", meaning they do not scale the FOV in an expected manner (they are less affected than in MW). This does however not affect the sensitivity, which still behaves as expected based on the FOV. Legacy works differently, as it is simply MDV 0% calculated based on your FOV. In MW it is MDV 0% to an FOV of 65 in Hdeg 4:3.  If you use Relative in MW you can use the exact same settings (including FOV) in CW and everything will be the same. For those not experiencing the same sensitivity in MW and CW based on the above there must be a bug in CW affecting some users.

😄
Support for different horizontal and vertical sensitivity is a feature I'm working on btw, the drawback is that a lot of games lack support for this.

This wasn't actually a limitation on decimals, but how many characters the box supports. For various reasons it's sensible to limit it, but I've increased it to 10 characters now

Is it possible to add this in both parts of the calculator?
It already supports one decimal place. I understand you may think "well, you can't have half a count" and that's true, but I use accel software which downscales dpi and uses math to carry the remainders with the interception driver, so the cursor velocity can be the equivalent of it (albeit with a bit of rounding).
It would just mean I could end up with slightly more accurate calculations. Esoteric request it may be, but I'm presuming it's a very easy change to make.

not support game singularity

No decimal support even in the config file as of now unfortunately, so the in-game sensitivity will have to do.

FOV can be adjusted via hex editing as well.
The value is listed in the config file twice, so you have to edit both.
If you use HxD, you can actually edit Sensitivity and FOV as float32 values directly, as long as you have the corresponding hex bytes highlighted:

shouldn't be afraid of voicing your ideas in regards to aim im pretty sure that most of the active users here are more than interested in optimizing their setup / alternatives
crowd sourcing ideas is the fastest way to achieve progress after all
 
out of interest does your setup look like this then ?
https://www.mouse-sensitivity.com/?share=c4e4d2bcac8450a57fb351583346e199
or do you manually convert desktop to hipfire with 110
then on another instance match hipfire with focal length 0% to not get the scopes affected by windows 100+ 0%
in theory the scopes should have the same number unless they get affected by 100%
 
btw i just noticed that the value i keep going back to when it comes to hipfire 41/43 cm/360 is pretty close to 100/110% mdh on 400dpi
ironic

I also wonder what's so special about 110% MDH :D

I also wonder what's so special about 110% MDH :D

did you just trial and error all options until you hit %110 mdh ?