Leaderboard

Ok, did some tests now and figured out what's going on... If you enter a decimal number and press enter it rounds the value to the nearest whole number. But if you just enter the number and click apply the decimals are conserved. This method probably renders the config file sensitivity redundant as you have the same precision in-game and it's a lot easier to set it.

Yes, the variables in the .ini is changed. The calculator is updated to reflect this, but you need to make sure you have the correct variables if you are just copying the values into the file. Just checked this in-game, and it doesn't matter what the Scoping value is set to when you select Override.

I always measure sensitivity and FOV with scripts. Aims that have blacked out the edges can be measured in two ways. Either by figuring out how the game scales FOV and sensitivity through other tests. So for instance if the game scales sensitivity to 100% monitor match, I know that double the 360 distance equals half the horizontal FOV. Or by measuring the distance visible in the scope. If only 40% (between the crosshair and edge) of the screen is visible, I can measure how far moving this 40% is, compare this to the 360 distance and calculate how many degrees I moved to reach 40% monitor distance. From there some more math to find the FOV. The FOV in the calculator is for the entire screen regardless of what is blacked out.