[SOLVED] Is this a bug? Different multiplier if converting TO or converting FROM

[ThisIsFlorianK]

Hi,,

I discovered a weird behavior of the calculator, I was wondering if it was a bug or if I didn't understand how it's supposed to work.

The result of converting FROM Overwatch TO Apex, is different than the result of converting FROM Apex TO Overwatch (for the same 360 distance hipfire). Isn't the calculator supposed to be reversible? I mean the settings are supposed to be equivalent, so whether we go in one direction or another it shouldn't affect the results if I understood correctly.

For example, for a 360 dist of 48.5613 cm, and a DPI of 900: Overwatch sensitivity is 3.17 and Apex sensitivity is 0.951. And that's fine, if I convert from Overwatch 3.17 I do get 0.951 for Apex and vice versa. BUT, depending on whether I convert FROM Overwatch or FROM Apex, I get different sensitivity multiplier. This doesn't make any kind of sense to me.

I've attached screenshots showcasing the issue, the green part is what is working as expected, and the red part is what differs depending of the direction of the conversion. Could you help me figure out if it's a bug or if I missed something entirely?

Best,

Florian Kempenich

 

Edited May 26, 2020 by ThisIsFlorianK

[DPI Wizard]

You don't have the same FOV for Overwatch and Apex, and all the ADS and scopes will be matched to the hipfire 360 distance and FOV of the input game. So that's the reason there's a difference.

Aims are generally matching using FOV so the sensitivity is related to what you see rather than how you navigate. This is why you should use the same game as source for all your conversions, to keep the aims consistent.

[ThisIsFlorianK]

YES! That's it! Nice catch. I tried artificially reducing the target FoV so that it is within the limit of Overwatch (so that they both have the same FoV), and yes it works as expected. Thanks for your response!

Now, it does raise another, related, question: Because I'm using different Fov in Apex and Overwatch (can't set high enough FoV in Overwatch), am I really training the same aim in both games? Let's say I want to replicate the exact aim I have in Apex, but in Overwatch (with the lower fov): Should I be using Monitor distance  instead of 360 distance for Hipfire?

By default it is set to 360 distance, but considering we're talking about 2 different FoVs. . . I'm starting to wonder what would be best

[DPI Wizard]

That depends on what you want really. If you use 360 distance you will have the exact same navigational sensitivity, while using monitor distance gives you the same on-screen sensitivity, i.e. aim.

[ThisIsFlorianK]

Hi again,

Yes, yesterday I had some time to think about it. I still haven't decided which way to go but now I can wrap my head around how everything work.

I really lke the way you described it: 'navigational sensitivity' vs 'aim sensitivity'. Not only did it help me confirm I understood things properly, I also think 'navigational sensitivity' is in itself a great way to help understand what keeping the same 360 distance means. I still have to think which one I'll rather keep, I'll do some more tests tonight, but that answers my question

Thanks a lot

EDIT: I marked the title as [SOLVED]

Edited May 26, 2020 by ThisIsFlorianK