Alcatraz

Possible bug? When converting from Windows to OW, Ana sens results in 37.92 and Ashe sens results in 51.51. When converting from OW hipfire to OW ADS, Ana sens results in 37.89 and Ashe sens results in 51.47. (Those are the results that seem to be correct.) Both times 0%MM was used. EDIT: Previous poster seems to be describing a similar phenomenon.

Yup, it seems you're right. It got me very close with a workaround using the data you provided. There still seems to be a small discrepancy of like 2-3%, but that could be caused by something else entirely I suppose. Thanks!

Did you manage to find out what the issue was?

I've set it to 3 in the registry.

If you are using PayPal, you can do it on the PayPal website.

I've tried different configurations but this one made the most sense to me. I've also tried converting from Overwatch with the same results. I've been tweaking the ingame settings a bit and it seems that a value close to 0.061243 would be correct, if I read the config correctly. None of the calculator configurations I tried led me to something that would be close to this.

I believe something is wrong with this one, I don't seem to be able to get the sens right (88.6314cm @ 360°; 16:9; 103 HFOV; 1100 DPI). Using 23.76 FOV Offset (103 Hdeg 16:9). If I use 3 WPS (my windows settings), it's way too fast. If I use 10 (default), it's way too slow. If I use 3 WPS and leave FOV at default in the calculator, it's still too fast. Any idea what the matter is with this one?

If you choose "Vehicle" as "Aim", the FOV in the calculator is stuck at 50 VFOV (I believe the default isn't even 50 but 55). The VFOV remains stuck at 50 if you attempt to change it.

Interesting. So the rounding limitations have more of an impact in the auto method due to the different nature of the formula? Also I always assumed that if one constantly uses different baselines for the calculations, the discrepancies would eventually add up and create bigger differences (A > B > ... > X > Y vs A > Y) so I've always been using the same baseline for the most "clean" results.

Any plans on adding 2D to 3D support and vice versa for the "Match At: Auto" method? Unless it's not possible? I wouldn't know since my understanding is limited.

Had the same issue but couldn't find a workaround. Ended up lowering my DPI to 400 and adjusting other settings accordingly. Please let me know if you find a solution.

Or am I on the wrong page here and the sensitvity remains the same, even when the FoV in-game changes? Because it's cropped for instance?

I frequently read about discussions going on in this forum and something that I've noticed is, that people always consider 360°/cm to be the worst of all the methods (same FoV conversions aside) and therefore not worth using. But in my opinion this isn't entirely true. What if I for instance want to match my muscle memory to be the same for a 180° turn as in another game with entirely different FoV? I mainly see this being useful in games where the ability to execute quick and precise turns (FPS/TPS melee combat?) is of great importance (e.g.: dashing through an enemy and turning 180° to face them again, all that as quick as possible). I'd therefore always use this method in games where the ability to make precise character-turns (usually to a point that is off-screen/off-monitor) is frequently required. Am I missing something or is it just an aspect that people seem to overlook when talking about the 360°/cm method?

Are you sure that the default killer FoV is 85? Just wondering since the wiki states 87. Also can you please activate the FoV setting in the calculator? It currently doesn't change the result but it IS possible to change the killer FoV through perks (up to +15°). Thanks in advance!

I see. I wouldn't mind doing the testing work if it doesn't involve having advanced knowledge of maths. I'd like to use viewspeed, that would be 0.7 then, right? I'm using 45 zoom-sens in Overwatch (1080p, 103FOV), which is supposed to be viewspeed I believe?