The new settings doesn't work yet! At least not when I try in training mode. It's still only the 1x Scope / Iron Sight setting that affects the scopes, and it seems to scale differently than before. I assume this is just bugged at the moment...
You are using MDH 0%, this is the fastest matching method for 2D to 3D. While MDH 0% is usually the most preferred method for aims and scopes, from 2D to 3D MDH 100% seems to be more favorable, so try that.
If you change the DPI for both the game and the desktop the sensitivity will be exactly the same. If you change just windows to 800 and keep Overwatch at 400 you will get a different result
Game added
Darkest Hour: Europe '44-'45
Games updated
World of Warcraft - Added support for Windows Display Scale, as this setting affect the sensitivity.
No Man's Sky - Added FOV calculations and config file support.
Some games have the camera directly in the center of rotation, then it doesn't matter how you measure. But as soon as it is a little bit in front or behind you'll need to measure against object further away. The extreme case is obviously third person where the camera is far behind the center, and to measure the FOV you need to do it against object ideally kilometers away in-game.
The match with 4:3 is actually a coincidence yes
Ok, I see what's going on now. You're standing too close to the wall you are measuring against. The camera is slightly off the center of rotation, so you need to measure against an object far away, at least about 50-100 meters. Try that
With 4.884 cm I end up short of the 100% distance.
These are my settings:
DefaultFOV=90.000000
MouseYawSensitivity=10
MousePitchSensitivity=10
MouseSensitivityMultiplierUnit=0.019290
Is the 360 distance as calculated?
I'm getting different results than you, with those settings the 100% MDH is 5.5746 cm as calculated. Could you upload your entire config file and I'll try with that.
Just checked now to be sure, and it's still vertical degrees. I can't measure any discrepancy either, it's pretty much spot on what it should be.
What exactly is the issue you are having? What numbers and what measurements doesn't line up?
Ideally all your aims should be derived from the conversion setup and be calculated based on this. If your setting doesn't match a conversion method however, you have to select each scope individually for the conversion.