Leaderboard

It's not wrong, Apex doesn't really use a set FOV Type in-game or in the config file. It's intended to use 4:3 in-game, but it's slightly off due to lazy coding as previously mentioned. When the FOV Type is set to multiplier it means that the value you put in must go through some kind of mathematical formula to calculate the actual FOV (which is important to the calculation). So Apex use Hdeg 4:3 as the base, but both in-game and config file values must go through a formula. BO4 uses Hdeg 16:9, which means the configured FOV is for 16:9 aspect ratio, any other ratio will have the FOV calculated based on this.

Hdeg 4:3 is simply the measurement method used by the game. This means that the FOV you configure is for the 4:3 portion of your resolution. If you play on 16:9, the extra width will be added on effectively expanding your FOV to almost 112 degrees. If it instead was Hdeg Res, then it would be 96 degrees for both aspect ratios. So as in the example image here, the red part (4:3) is what you configure in Apex. If you don't play in 4:3, the extra green (for 16:10) or blue (for 16:9) will be added on.

The calculator always switches to the correct FOV Type for the game and location you have selected. Apex uses a completely different FOV in-game and in the config file, so you when you switch location, you also have to enter the value from that location. So if you want a FOV of 96 Hdeg 4:3, but configure it in the config file you need to set the FOV Type to Hdeg 4:3 and enter 96, then check the output for the correct cl_fovScale to get this exact FOV.

You are entering 96 FOV for Apex as a multiplier, that's wrong. Switch the FOV Type to Hdeg 4:3, then enter 96. This will give you the correct cl_fovScale and fix both your problems Or switch the Location for Apex to In-game if you don't want to mess with the config file. Then enter 96 as a multiplier.

The ADS sensitivity in Titanfall 2 is not a multiplier of the hipfire sensitivity, but its own sensitivity. Also the ADS sensitivity scaling locked to 70, so any other FOV will result in a slightly different sensitivity than MDH 0% for hipfire. The FOV shown in-game in Apex is not the actual FOV, but is slightly off due to some lazy coding. So in the calculator it's shown as a multiplier by default, so when you enter the FOV value from the game, the actual FOV will be shown in the output.

GoD is in!

People shouldn't be thinking of monitor distance as a type of match, rather it's a just a measurement for a sensitivity change. No matter what system you use to attempt to maintain a perceived sensitivity of the game world at a different FOV, it will ALWAYS be equivalent to at least one monitor distance, therefore monitor distance itself can not be flawed. When people have a preference for 75% Mdh, for example,. its not because they want accurate flicks to a part of the screen; it;s nothing to do with that at all - it's the fact that the speed of the gameworld seems most consistent to them when calculating turn-rates across FOVs using that method. It's almost impossible for anyone to deny, that if using focal length or 0%, that when ADS'ing with a high zoom scope it always feels much slower than hipfire, therefore, with the exception of making slow tracking the most consistent, it doesn't have much value for sniping play styles. This is why approx 75% feels the most consistent across multiple FOVs, but if you only use small FOV changes when aiming, it starts to have less value.

0% mm match might be mathematically the best way, but for the practice it isnt good may it works for high sens player idk. If u already a low sens player and use 0% MM for ADS ur sensitivity is wayyyyyy to slow