392
edits
No edit summary |
mNo edit summary |
||
Line 5: | Line 5: | ||
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: | 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'' | * 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 <code>cd $HOME</code>. | ||
<!-- ''Mac OS X'' = POSIX? --> | |||
* 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''. | * 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''. | ||
Line 12: | Line 14: | ||
===== Some 'rules' for the content: ===== | ===== Some 'rules' for the content: ===== | ||
* Each line contains one option only. | * Each line contains one option only. | ||
* If the first 'visible' character is a '#', ''fgfs'' | * If the first 'visible' character is a '#', ''fgfs'' totally ignores the line (comment). | ||
* | * Use comments following an option (<code>--some-option # some comment</code>) with care. At least with string containing''--prop='' options this will cause ''fgfs'' to fail. | ||
edits