I tried converting Desktop to Apex Legends and got this weird deviation in the ADS sensitivities for all scopes:

Can anyone explain what's going on here? It seems strange.

Edited June 24, 20223 yr by heckminth

First off, cl_fovScale 1.7 does not work unless there's some kind of workaround I'm not aware of. The game maxes out at 1.55

As for the deviation, the hipfire is off by 0.0002% due to rounding, the ADS calculation accounts for this so they are perfectly matched.

17 hours ago, DPI Wizard said:

First off, cl_fovScale 1.7 does not work unless there's some kind of workaround I'm not aware of. The game maxes out at 1.55

cl_fovScale 1.7 works and is explicitly allowed by Respawn, you just have to set it in both profile.cfg and autoexec.cfg.

17 hours ago, DPI Wizard said:

As for the deviation, the hipfire is off by 0.0002% due to rounding, the ADS calculation accounts for this so they are perfectly matched.

I see, thank you.

Edited June 25, 20223 yr by heckminth

I have a follow up question, is the minimum sensitivity in Apex really 0.01 as is stated by your calculator? The sensitivity value in the in-game menu always rounds up to a minimum of 0.2 when I input any value lower than 0.2.

10 hours ago, heckminth said:

cl_fovScale 1.7 works and is explicitly allowed by Respawn, you just have to set it in both profile.cfg and autoexec.cfg.

I tried now, and it does go above 1.55. However it maxes out at 1.642857, which might seem like a weird number, but it's equal to exactly 115 hdeg in 4:3. Going above this does not increase the FOV, unless I'm doing something wrong  I've updated the max FOV for the config file calculations.

10 hours ago, heckminth said:

I have a follow up question, is the minimum sensitivity in Apex really 0.01 as is stated by your calculator? The sensitivity value in the in-game menu always rounds up to a minimum of 0.2 when I input any value lower than 0.2.

It used to go down to 0.01, but it does indeed reset to 0.2 now so I've updated the minimum.