Closed nullsystem closed 1 week ago
@Rainyan I don't think it was consistent before either, but anyway it should be now be immediate when neo_fov setting gets applied.
@Rainyan I don't think it was consistent before either, but anyway it should be now be immediate when neo_fov setting gets applied.
This fixes the FOV change not being applied. But it seems our aim FOV is now somehow coupled to the base FOV. For example, if you set neo_fov 75
and try aiming, it pulls the viewmodel in but your actual FOV doesn't change at all, i.e. there is no "zooming" occurring. I'm assuming we'd want the zoom FOV change to be the same ratio as it is in original NT, decoupled from whatever value the FOV we're zooming from might be.
@Rainyan Whoops look like GetMinFOV
shouldn't been altered. Try it now. MIN_FOV
's only for neo_fov
setting now. The zooming in values is taken straight from the scripts so it should be those instead.
Description
neo_fov
ConVar fixed, now set to only define client-side and also used as such instead of the weird server->client routing before. However the server-side will still need to utilize it for server-player and for relay-modeneo_fov_relay_spec 1
neo_fov_relay_spec
new ConVar, defaults to disabled which uses client'sneo_fov
for 1st person spec. If enabled, relays spectated player'sneo_fov
to whoever spectating the player in 1st personneo_fov
min FOV changed from 60 to 75, default to 75Toolchain
Linked Issues