1476
« on: April 03, 2020, 09:06:03 PM »
When a client joins a server there is a moment when their client loads and their FOV can be accurately determined with the game's built-in FOV commands before it starts returning 90 for some handicapped reason nobody knows. If you try to capture this value too early or too late, FOV cannot be accurately determined. Tendon's FOV script attempts to resolve this issue by setting the client's FOV to 3.14 when they connect, and then running a loop to determine when FOV updates to the accurate value, and trying to capture it then.
On certain occasions I have noticed that:
- The client's default FOV is predicted to be 3.14 (setting FOV to 3.14 too late?)
- The client's default FOV is predicted to be 90 when it shouldn't (loop check not looping fast enough to catch the accurate value?)
Some things that can break your FOV:
- Joining the server while holding the zoom key
- Leaving the server while zoomed in with a weapon/holding the zoom key
The only remaining solution I can think of is to use the /SetDefaultFOV -fov command. This could probably be improved by then saving that value to a file, referenced by BL_ID, somewhere server-side and then accessing it again each time the client joins so they only have to do it once each time they update their FOV.