Fix FOV being applied twice from redundant fov->settings application.

[snowing64]

Description

Fix FOV being applied twice from redundant fov->settings application. Bump the main field-of-view variables to array's that correspond with the max amount of local players (4).

Changes

Previous Behavior

When the FOV would be changed in the settings menu, both m_fov and options->fov would be set, and would be multiplied twice.
(on 110fov)

Root Cause

m_fov and options->fov were being written to. getFov() reads both, causing field of view to be multiplied.

New Behavior

Field of view applications works as intended.
(on 110fov)

Fix Implementation

Refactored field-of-view logic to correctly apply once in single-player and split-screen environments.

AI Use Disclosure

None.

Related Issues

• Related to [Bug] FOV and Render Distance #802
• Fixes [Bug] FOV 110 causes everything to FLIP when sprinting? #838

[codeHusky]

Are you sure this is the right line to keep? It seems like the iPad line is the one that would be safe to use considering split screen

[snowing64]

I overlooked that, thanks. I redid the logic. It works on paper and with regular gameplay but I'm unsure if it works in a real split-screen environment. I wasn't able to test it with split-screen due to the logic for handling input being stubbed/nonexistent (didn't look into it comprehensively) on the Windows64 build.