Difference between revisions of "Fgfsrc"
|Line 1:||Line 1:|
= fgfsrc =
= fgfsrc =
Like all [http://www.catb.org/jargon/html/R/rc-file.html rc-files], the ''fgfsrc''s purpose is to contain [[Command Line
Like all [http://www.catb.org/jargon/html/R/rc-file.html rc-files], the ''fgfsrc''s purpose is to contain [[Command Line ]] which are read by ''fgfs'' at startup. This is for users who start FlightGear from the [[command line]], so users using a graphical user interface like [[fgrun]] don't have to bother with this at all. Anyhow, it is possible to use fgrun to create your personal set of options by copy-and-pasting them from the ''Show command line'' textbox (on the last page of FGRun) into ''fgfsrc''.
Revision as of 05:06, 13 October 2009
Like all rc-files, the fgfsrcs purpose is to contain Command Line Options which are read by fgfs at startup. This is for users who start FlightGear from the command line, so users using a graphical user interface like fgrun don't have to bother with this at all. Anyhow, it is possible to use fgrun to create your personal set of options by copy-and-pasting them from the Show command line textbox (on the last page of FGRun) into fgfsrc.
It is very likely that this file does not exist on your system yet, and therefore has to be created by the user, you. The contents of the file are handled the same way by fgfs on all operating systems, but the name and location is not:
- on GNU/Linux the file is called .fgfsrc (note the leading dot!). fgfs is looking for it inside the user's $HOME directory. To figure out where this is on your system, open a terminal window (shell) and enter
- on Windows systems the file is called system.fgfsrc and lives in $FG_ROOT which, on a standard installation, is C:\Program Files\FlightGear\data.
A simple way to have more than one setup is to replace fgfsrc by a link which can be changed according to the setup one wants to load. On a GNU/Linux system this could look like
ls -l ~/.fgfsrc* ... /home/user/.fgfsrc -> .fgfsrc.cvs ... /home/user/.fgfsrc.1.9.1 ... /home/user/.fgfsrc.cvs
Some 'rules' for the file and it's content:
- The file is plain text (ASCII), like saving a .txt-file with Wordpad.
- Each line contains one option only.
- If the first 'visible' character is a '#', fgfs totally ignores the line (comment).
- Use comments following an option (
--some-option # some comment) with care. At least with string containing--prop= options this will cause fgfs to fail.
An example of a basic fgfsrc file:
Have in mind, that *at least* the local paths (like fg-root and fg-scenery) and the Multiplayer options have to be altered to work on your system!
# $HOME/.fgfsrc ### Aircraft # --aircraft=ec135 ## Catalina, dhc3[A/F], p47d-30, F1-156-de, ZivkoEdge540 ## MPcarrier: nimitz, nimitz-ATC, nimitz_observer, foch, vinson, eisenhower ### Initial position # --airport=LOWI #--runway=08L #--parkpos=A11 # # In air: #--offset-distance=1.5 #--altitude=6000 #--vc=70 #--enable-freeze # # Coordinates: ## Oilrig Lennox: #--lon=-3.17547 #--lat=53.63305 #--altitude=205 ### Environment # --timeofday=noon #--enable-real-weather-fetch --enable-horizon-effect --enable-specular-highlight --enable-ai-models --enable-clouds3d --shading-flat --fog-nicest --enable-random-objects --prop:/sim/rendering/random-vegetation=true ## limit fps to 30: --prop:/sim/frame-rate-throttle-hz=30 ## rain/snow: --prop:/sim/rendering/precipitation-enable=true --ai-scenario=nimitz_demo --ai-scenario=clemenceau_demo #--ai-scenario=aircraft_demo ### Network # --callsign=I-FLY #--prop:/sim/remote/pilot-callsign=U-FLY --multiplay=out,10,mpserverXX.flightgear.org,5000 #--multiplay=in,10,localhost,5000 --httpd=5500 ## nice terrasync -p 5505 -S -d /opt/fgfs/scenery.terrasync : --atlas=socket,out,1,localhost,5505,udp ## fgcom -Sfgcom.flightgear.org.uk [-f910] : --generic=socket,out,10,localhost,16661,udp,fgcom ### System # #--log-level=info ## alarm,warn,info,debug --fg-root=/opt/fgfs/data --fg-scenery=/opt/fgfs/data/Scenery:/opt/fgfs/scenery.1.0.1:/opt/fgfs/scenery.terrasync --geometry=1280x1024 --bpp=24 --control=joystick --prop:/sim/traffic-manager/enabled=0 ## disable mouse mode 'fly': --prop:/input/mice/mouse/mode/button/binding/value=2
Some options (mostly properties) are only temporary of interest to the 'normal' user or even only for CVS users:
See forum and mailing list for more info on this.
--random-wind # not in 1.9.1 and former versions
Nice turbulences during approaches ;-).
Please feel free to add other useful options to the temporary and basic ones!!!