I noticed that in the calculator, the ADS sens for 360 conversion is 83, which although widely used, is wrong, because its slightly slower than 1:1, using 84 is better because the game is hardcoded such that ads sensitivity doesnt go above 83.33 which means settings 84 means an ADS sens of 83.33 for 1x scopes and ironsight.

With Monitor Distance-Vertical, it recommends 101 ADS which is wrong because the ADS simply doesnt go above 84. I'd like the know the admin's opinion on this.

3 hours ago, LordVeyo said:

I noticed that in the calculator, the ADS sens for 360 conversion is 83, which although widely used, is wrong, because its slightly slower than 1:1, using 84 is better because the game is hardcoded such that ads sensitivity doesnt go above 83.33 which means settings 84 means an ADS sens of 83.33 for 1x scopes and ironsight.

83.33 is rounded down to 83 because of how math naturally works. In-game sensitivity is inherently inaccurate because of the lack of decimals, so use config file sensitivity if the 0.4% difference is important

4 hours ago, LordVeyo said:

With Monitor Distance-Vertical, it recommends 101 ADS which is wrong because the ADS simply doesnt go above 84. I'd like the know the admin's opinion on this.

This is a workaround to account for the fact that ADS maxes out at hipfire's 360 distance and can't be faster. In your example you are trying to match ADS in R6 to hipfire in CSGO using MDV 0%, but the ADS FOV in R6 (81 vdeg) is higher than hipfire in CSGO (73.74 vdeg). This results in the 360 distance for ADS in R6 being around 20 inches, but your hipfire is already set to 22.44 inches so the match is impossible. When this happens the calculation throws 101 in there to trigger an out of range error indicating it is an impossible calculation.