Sure. The way I currently have things set up, I have a config.cfg which has the single line
exec bnonn.cfg. I'm not sure if this is the best way; I suspect using autoexec.cfg is probably the recommended method, but anyway.
In bnonn.cfg, I have the following lines set aside for the fov bindings (note that I've changed these from my previous post, based on experimentation):
bind "1" "fov 120; sensitivity 8"
bind "2" "fov 105; sensitivity 6"
bind "3" "fov 85; sensitivity 5"
bind "4" "fov 60; sensitivity 4"
bind "5" "fov 30; sensitivity 3"
bind "6" "fov 10; sensitivity 2"
You'll want to make sure you don't have keys 1-6 bound to anything else in the config file; you could just do a search in the file, or otherwise just stick
unbind "1"; in front of the commands above (obviously replacing
1 with
2,
3 and so on as needed).
Once you load Nexuiz, and assuming you've execced this config file, you will be able to hit 1 to get fov 120, 2 for fov 105, etc. Bear in mind this isn't a toggle; it's an actual fov change. When I'm using the nex, I tend to hit 3 unless I'm in a very fast-paced area, in which case I'll use 2. The same goes for the machinegun or shotgun; any hitscan weapons require lower fov and sensitivity to get the most accurate aim. If I'm a long way from anyone, I'll hit 4 or 5 to snipe; and when I'm
really far away, and know that I'm not going to get taken from behind, I'll hit 6. When I'm using the rocket launcher or mortar or whatever, I tend to stick to 1 or sometimes 2, depending on the situation.
Hope this helps (: