If I set -fov to a low value, say 0.2, the all the targeting stuff (the brackets, missile lock etc) are too near to the center. If a ship is in the center of the screen, everything is fine, but if it is near the edge of the screen, the gauges are in the wrong position.
If I set -fov to 0.8, the gauges are still correct if a ship is in the center. However, if the ship is near the edge of the screen, the gauges are too far towards the edges of the screen.
So it seems there is a "magical" value where everything is fine...
The 3D radar still has the old background... It's easy to fix by putting an empty 2D_radar.ani (IIRC) into data/huds, but it would be nice to get rid of it automatically.
When using the -start_mission option, the name of the mission cannot contain a dash. For example when trying to start sm3-08.fs2, I get the error "Could not find sm3.fs2". Perhaps you should be using GNU geopts
Command line options:
-spec -glow -pcx32 -jpgtga -d3dmipmap -nomotiondebris -2d_poof -pcx2dds -dualscanlines -ship_choice_3d -targetinfo -3dwarp -tbpwarpeffects -ballistic_gauge -snd_preload -fps
I am using D3D, Geforce4 Ti4200 64MB. Media vps 3.6.6 except adveffects.