Leaderboard

Added FOV instructions and the missing games

If the FOV Type for a game is "Multiplier" in the calculator, you can never use this value directly. You have to see the output for the Actual FOV which will show you the correct actual FOV value. For some reason they assigned cl_fovScale 1 (70 actual hdeg 4:3) to in-game value 70 and cl_fovScale 1.55 (108.5 actual hdeg 4:3) to in-game value 110 and made it scale linearly between these points. There's absolutely no good reason for this other than them being lazy with their implementation.

MDV 177.78% with 90% scale.

In the first post, I explained what 100% MDV means. And that the mouse sensitivity is the same for only one point = one mouse distance = one monitor distance. All other mouse distances will result in a different monitor distance. And I was curious. How the rest of monitor distances are affected? And from 0% MDV? So I created 9x mouse distances in spreadsheet. To see how other monitor distances will be affected. And when I was manually changing sensitivity in steps of 0,05 from 0% to 100% MDV. I cloud visually see that at some sensitivity the deviation between points is much lower. But the problem was, how can I be sure that this sensitivity settings will give me lowest possible deviation for all monitor distances? In that time I didn't know how to build formula for that. So I did the simplest thing. I created in spreadsheet 4000x monitor distances and for each of them I received deviation. After that I converted this deviation to absolute deviation to be able count them all even if they will be negative. This gave me the Sum of the Deviations (SoD). After that I was able to find “magic” sensitivity settings that will give me the overall lowest possible deviation across whole screen. And you can be sure about that, because if you change sensitivity to anything else from that “magic” sensitivity the SoD will rise. Meaning overall deviation will rise. I made a short video with only 9x monitor distances. So you can see how I arrived to it: