Overwatch scoped monitor match 0% to PUBG possible anomaly

[sonorciff]

Hi~

I was converting the Overwatch monitor match 0% scoped value of 37.94 to PUBG's various FPP aim types.

I noticed out of the 10 aim types in PUBG, only ADS (AR/LMG/DMR/Sniper) showed a different value when converting from Overwatch 37.94 scoped than Overwatch hipfire. Every other conversion between FPP PUBG and Overwatch shows the same mm 0% value to 4 decimal places, yet this one conversion shows a small difference. At 2.42 Overwatch sensitivity, hipfire to PUBG ADS (AR) returns 64.2359cm/360, and Overwatch scoped to PUBG ADS (AR) returns 64.25cm/360.

I am aware Overwatch's 37.94 scoped sensitivity isn't a precise value as the game only supports 2 decimal places for sens, and also that .141mm/360 discrepancy is humanly imperceptible. Still, I wouldn't sub here if I weren't anal about these things ^^. I tried 2.4 and 2.39 instead of 2.42, and they actually returned same values to PUBG ADS (AR) from both hipfire and scoped, to 4 decimal places. From what I can tell it's just this specific combination of sensitivity and aim type which shows an anomaly. Could you please let me know what the cause of this difference might be?

Edited August 30, 2018 by sonorciff

[Drimzi]

Why not just convert from your Overwatch hipfire sensitivity? Converting from 37.94 is just using a low precision version of your hipfire sensitivity

The actual number would be this, but the decimals are infinite.

The different results will be due to rounding. That change in precision was just enough to round upwards.

[sonorciff]

I already do as you suggest, and in practice I don't care about the difference. I figured it could be rounding, but there was another specific and odd number anomaly in the calculator a while back and I wondered if this could be a similar situation ^^