Leaderboard

The pixel ratio is a function of the in-game sensitivity, the FOV, and the screen resolution only. No other variables affect it. Given that it is not very convenient to change your screen resolution or FOV for this issue alone (given that there are pervasive consequences attached to those changes) you would simply reduce the game's sensitivity value instead, as this can be compensated directly for with DPI increase with the only other action requiring reduction in windows cursor speed slider if it bothers you.

You have to increase your DPI if you want 11 cm with a lower pixel/count. If you double it from what you have now (and keep the 360 distance at 11 cm) you will get just about 1 pixel/count.

About 0.14.

As the output says, it's not possible since it's out of range. The hipfire sensitivity is too low, so the tank sensitivity can't match it. Note that the sensitivity values in the error can sometimes be wrong simply to avoid division by zero since the target distance in the calculation is out of range.

You are using 360 distance to match ADS and scopes, and this is generally not recommended for this reason, in addition to it being impossible to achieve for the 4x to 12x in this game. To fix this use instead one of the other matching methods for ADS and scopes. MDV 0% will actually match the pixel ratio to your hipfire.

I see the issue, 0 is technically not a valid sensitivity, so while it's possible to set it in the game, it will lead to a division by zero in the calculator. So the reason you get the seemingly same result was due to a protection to avoid this. I've instead adjusted the minimum allowed sensitivity now.

Can you please share links to the two conversions?