Question about the calculation of ADS-Sensitivity

[Scca]

Hellow ^^

My thoughts are a bit difficult to explain so I made it into a picture seen in the attached file.

I always assumed that the ADS/Scope sensitivity of the output game is calculated the way the blue arrow indicates: First the Hipfire Sensitivtiy is calculated and then based on these results the sensitivity of the ADS/Scope is calculated.
But trying this out with a game that has a universal setting for all scopes like CoD with their coefficient setting, turns out that ADS/Sopes are calculated the way the green arrow shows: That the sensitivity for the scopes are based on the Hipfire FOV of the Input Game, not the Output Game. This can be seen here. Despite the Coefficient being calculated at 1.33, each scope still has a different value than 1, which I can only assume is because the calcualtor tries to match the sensitivity based on the 120 Hipfire HFOV of the Input Game rather than the 107 Hipfire HFOV of the Output Game because otherwise a value of 1 for each scope would suffice with the Coefficient already being at 1.33.

My question basically now is: Is all of this that I just said correct or am I missing something? And Is there a way to make the calculator use the way that the blue arrow shows?

Or to make it a bit more specific: Assuming that both Input and Output Games have different Hipfire FOV and a different Hipfire cm/360° BUT both games have a Scope that has the value of 100 HFOV, would the calculator make it so that the scopes have the same cm/360° in both games? 

Since I always matched FOVs on both games so far this never really mattered to me anyway but now that I start to play games with locked FOV (Shatterline/Destiniy 2) I thought I would need a big work-around to have the FOV calculated the green-arrows way since that would be my preffered way. But I guess if that is how the calculator already works then I would not need to worry.

Edited July 21, 2023 by Scca

[DPI Wizard]

1 hour ago, Scca said:

My question basically now is: Is all of this that I just said correct or am I missing something? 

What you said is correct, and it has to be this way to make any sense. If the scopes were matched to the hipfire of the output game you would not get any consistency unless you also match the hipfire FOV between the games.

Consider this example converting from Overwatch with FOV 103 to Overwatch with FOV 80: https://www.mouse-sensitivity.com/?share=43c8dace9347072001b6b2962b254eaf

The FOV change only affects hipfire, the zoom FOV stays the same. So the sensitivity (360 distance) for the zoom should also stay the same to keep it consistent. If they were matched based on FOV 80 instead, you would get a completely different sensitivity for identical zoom levels.

1 hour ago, Scca said:

And Is there a way to make the calculator use the way that the blue arrow shows?

Click the reverse calculation button between the input and output game