From FlightGear wiki
Revision as of 08:55, 9 October 2015 by Hamzaalloush (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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 cd $HOME.
  • On Mac OS X, the same as GNU/Linux. A Terminal window is placed on /Applications/Utilities/Terminal.app
  • on Windows systems the file is called fgfsrc and lives in $FG_HOME which, on a standard installation for FlightGear 3.0 and later, with Vista and later it can be found under C:\Users\{username}\AppData\Roaming\flightgear.org.

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.
  • Variables, such as $HOME or $FG_HOME, in paths are not resolved.

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
 ## Catalina, dhc3[A/F], p47d-30, F1-156-de, ZivkoEdge540 
 ## MPcarrier: nimitz, nimitz-ATC, nimitz_observer, foch, vinson, eisenhower
### Initial position
# In air:
# Coordinates:
 ## Oilrig Lennox:
### Environment
 ## limit fps to 30:
 ## rain/snow:
### Network
 ## nice terrasync -p 5505 -S -d /opt/fgfs/scenery.terrasync :
 ## fgcom -Sfgcom.flightgear.org.uk [-f910] :
### System
 ## alert,warn,info,debug
 ## disable mouse mode 'fly':

Some options (mostly properties) are only temporary of interest to the 'normal' user or even only for Git users:

  • --prop:/sim/traffic-manager/use-custom-scenery-data=true
    See forum and mailing list for more info on this.
  • --random-wind # not in 1.9.1 and former versions
    Nice turbulences during approaches ;-). Attention: with Git version (and probably 2.4.0 as well) this option can only be used together with option --disable-real-weather-fetch!

An example of a debug fgfsrc file:

for debugging purposes, like when using gdb, it might be easier for you to arrange a .fgfsrc with minimal options enabled. see Troubleshooting_crashes for further info, a template for a debug fgfsrc file would be:


note: you have to direct --fg-root towards your $FGDATA folder

Please feel free to add other useful options to the temporary and basic ones!!!

Also see