How to best handle discrepancy

[CaptaPraelium]

I have noticed a behaviour. As an example let's say I use my desktop as the base for conversion. Then I get my hipfire viewspeed for the game, then other zoom levels for the game. All OK so far.
Now for the problem.... as the 'convert from' base for the conversion, I switch from using the desktop as above, to the hipfire sensitivity I got for the game. When I do this, the values I get for the other zoom levels, is different. It's very very close, but not the same. I suspected this was a rounding error or something, it's that close. I'll paste that example:

CALCULATIONS

Windows / Desktop

DPI:

800

Distance:

16.256 cm to move mouse cursor across screen

Base length:

40.6257 cm

 

Battlefield 1 (Config file - ADS FOV OFF) - Hipfire

Sensitivity 1:

GstInput.MouseSensitivity 0.006160

360° rotation:

44.689 cm

Base length:

40.624 cm

 

Discrepancy: -0.0042% (-0.0017 cm)

Config FOV:

GstRender.FieldOfViewVertical 80

Actual VFOV:

80 degrees

Actual HFOV:

112.33 degrees

 

CALCULATIONS

Windows / Desktop

DPI:

800

Distance:

16.256 cm to move mouse cursor across screen

Base length:

40.6257 cm

 

Battlefield 1 (Config file - ADS FOV OFF) - 4.00X Zoom Sensitivity

Sensitivity 1:

GstInput.MouseSensitivity 0.006160

Sensitivity 2:

GstInput.UniformSoldierAimingCoefficient 0

Multiplier 1:

GstInput.SoldierZoomSensitivityAll 1

Multiplier 2:

GstInput.SoldierZoomSensitivity4x00 1.294481

360° rotation:

223.0411 cm

Base length:

40.6257 cm

 

Discrepancy: 0% (0 cm)

Config FOV:

GstRender.FieldOfViewVertical 80

Actual VFOV:

14.8 degrees

Actual HFOV:

26 degrees

 

CALCULATIONS

Battlefield 1 (Config file - ADS FOV OFF) - Hipfire

Sensitivity 1:

GstInput.MouseSensitivity 0.006160

360° rotation:

44.689 cm

Base length:

40.624 cm

Config FOV:

GstRender.FieldOfViewVertical 80

Actual VFOV:

80 degrees

Actual HFOV:

112.33 degrees

 

Battlefield 1 (Config file - ADS FOV OFF) - 4.00X Zoom Sensitivity

Sensitivity 1:

GstInput.MouseSensitivity 0.006160

Sensitivity 2:

GstInput.UniformSoldierAimingCoefficient 0

Multiplier 1:

GstInput.SoldierZoomSensitivityAll 1

Multiplier 2:

GstInput.SoldierZoomSensitivity4x00 1.294535

360° rotation:

223.0318 cm

Base length:

40.624 cm

 

Discrepancy: 0% (0 cm)

Config FOV:

GstRender.FieldOfViewVertical 80

Actual VFOV:

14.8 degrees

Actual HFOV:

26 degrees

 

 

In fact, now, I suspect this is in fact a result of the discrepancy between the desktop-to-hipfire conversion. It strikes me that the 'correct' usage of the calculator, would be to do the desktop-to-hipfire conversion, and then do all other zoom levels in that game based on that hipfire, so that any discrepancy is consistent between zoom levels within the game, rather than being consistent with the desktop which we are not using during gameplay

I guess this is a matter of perception. Which discrepancy is best, 'this one' or 'that one'? Any thoughts?

 

 

Edited September 28, 2017 by CaptaPraelium

[Drimzi]

Edited January 28, 2018 by Drimzi

[CaptaPraelium]

Hmm, but would it not be more important, for there to be no discrepancy between hipfire and any zoom level in the same game, than to have no discrepancy between the desktop and hipfire but some discrepancy between hipfire and some zoom levels?
The discrepancy has to lie somewhere, it strikes me that it would be best to have zero within each game, so it's always consistent when playing that game, than to be inconsistent within the game but more consistent between games....
... Actually, I feel like I'm answering my own question here, and that answer is, it depends on what's more important between those two, consistency within the game or across games.
Thanks man