FOV doesn't change

[WallyTheBoogieBug]

I have an autoexec to set FOV to 110, and although when typing FOV in the console to check what it currently is tells me it's set to 110, this change isn't reflected until I manually enter in the FOV in-game.

This same problem persists into the config, where trying to add fov 110 into the config causes ZDoom to delete the line from the config, in addition to not properly executing the command.

I didn't post this into the bugs section because it appears to affect all versions of ZDoom I can find, including Zandronum, as well as old versions, and I'm not exactly sure if it's a bug with this in mind.

I was able to "solve" this by making my WASD movement keys execute 'fov 110' in addition to moving, but it's a weird fix for something that appears unintentional.

Is this intentional?

[edward850]

FOV is not an archived value. In fact, it's not a value at all, it's a CCMD. All it does is change the "DesiredFOV" (the same thing value for weapon/teleport zooming) of the consoleplayer to the specified value (if allowed)*, and because it's stored in player_t it gets reset every time player_t is (re)built (new games, new levels or re-spawning).

* What the FOV CCMD actually does is write a command to the network buffer indicating a change for the next live gametic, as this change needs to be reflected in demos/netgames.

[Kappes Buur]

You cannot set a value for FOV directly in autoexec.cfg, but you can bind a key to it.

That's the example from http://zdoom.org/wiki/CCMDs :

Code: Select all

alias zoomout "fov 90; eval * $mouse_sensitivity 4.5 mouse_sensitivity; rebind zoomin"
alias zoomin "fov 20; eval / $mouse_sensitivity 4.5 mouse_sensitivity; rebind zoomout"
bind F zoomin

Just toggle F.

[WallyTheBoogieBug]

Thanks, I assumed it was a permanent variable like a lot of other games.