You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like default_fov functionality is broken at least for regular TF mode.
This functionality was working following:
User prefer some fov. Let it be 105 for example.
To play TF he sets fov and default _fov variables.
When player affected by concussion grenade server sends command to set fov 120.
After a while concussion effect ends and server sends command "fov 90".
The idea of default_fov variable was that when player receives "fov 90" actual effect it to set fov to 105 ( value of default_fov in example )
Currently behaviour is completely weird.
Steps to reproduce the behavior (all steps done with console without server):
Connect to server and set fov and default_fov to 105'
Change fov to 110
check current value of default_fov
( just type /default_fov)
It is 110. Broken!
Expected is 105
Now enter:
/fov 90
Expected final result:
default_fov and actual fov must be 105'
The text was updated successfully, but these errors were encountered:
It looks like default_fov functionality is broken at least for regular TF mode.
This functionality was working following:
User prefer some fov. Let it be 105 for example.
To play TF he sets fov and default _fov variables.
When player affected by concussion grenade server sends command to set fov 120.
After a while concussion effect ends and server sends command "fov 90".
The idea of default_fov variable was that when player receives "fov 90" actual effect it to set fov to 105 ( value of default_fov in example )
Currently behaviour is completely weird.
Steps to reproduce the behavior (all steps done with console without server):
( just type /default_fov)
It is 110. Broken!
Expected is 105
/fov 90
Expected final result:
default_fov and actual fov must be 105'
The text was updated successfully, but these errors were encountered: