$FG SCENERY: Difference between revisions
m (corrected: scenery paths separated by colon, not semicolon (http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438&start=360#p182311)) |
(Clean up.) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
'''$FG_SCENERY''' | '''$FG_SCENERY''' defines the scenery directories for [[FlightGear]]. It can be set with the <code>--fg-scenery=</code> option (from the [[command line]] or in the [[fgfsrc]] file) or via the FlightGear launcher. | ||
===Common paths=== | Scenery other than the default airport and surrounding area that is shipped with FlightGear should not be placed inside the scenery directory of [[$FG_ROOT]]. Separate directories should be created. To use these, [[#Multiple directories|see below]]. | ||
* '''Mac OS X:''' < | |||
* '''Ubuntu:''' < | === Common paths === | ||
* '''Windows:''' < | * '''Mac OS X:''' <code>Applications/FlightGear.app/Contents/Resources/data/Scenery</code> | ||
* '''GNU Linux (e.g. on Ubuntu):''' <code>/usr/share/games/flightgear/Scenery</code> | |||
* '''MS Windows:''' <code>%ProgramFiles%/FlightGear/data/Scenery</code> | |||
== Multiple directories == | == Multiple directories == | ||
Directories are | Directories are read from left to right. For each scenery tile, FlightGear will check if it exists within the first directory. If not, it will move on to the second directory and so on. Directories should be separated by colons (on *nix) or semicolons (on MS Windows, Mac OS X), such as: | ||
--fg-scenery=Scenery/Custom | --fg-scenery=Scenery/Custom;Scenery/TerraSync | ||
FlightGear searches these scenery paths sequentially. The first terrain found for each tile is loaded. Objects for a tile are loaded from all directories visited before (and including the one where) the terrain was found. | |||
The path can contain objects only, terrain only or combined scenery directories. The Airports and Model directories (which are late additions) complicates the scheme a bit as they can only be in combined terrain and objects directories | The path can contain objects only, terrain only or combined scenery directories. The Airports and Model directories (which are late additions) complicates the scheme a bit as they can only be in combined terrain and objects directories. | ||
[[Category:Special directories|SCENERY]] | [[Category:Special directories|SCENERY]] | ||
[[de:$FG_SCENERY]] | [[de:$FG_SCENERY]] | ||
Revision as of 08:54, 30 May 2016
$FG_SCENERY defines the scenery directories for FlightGear. It can be set with the --fg-scenery= option (from the command line or in the fgfsrc file) or via the FlightGear launcher.
Scenery other than the default airport and surrounding area that is shipped with FlightGear should not be placed inside the scenery directory of $FG_ROOT. Separate directories should be created. To use these, see below.
Common paths
- Mac OS X:
Applications/FlightGear.app/Contents/Resources/data/Scenery - GNU Linux (e.g. on Ubuntu):
/usr/share/games/flightgear/Scenery - MS Windows:
%ProgramFiles%/FlightGear/data/Scenery
Multiple directories
Directories are read from left to right. For each scenery tile, FlightGear will check if it exists within the first directory. If not, it will move on to the second directory and so on. Directories should be separated by colons (on *nix) or semicolons (on MS Windows, Mac OS X), such as:
--fg-scenery=Scenery/Custom;Scenery/TerraSync
FlightGear searches these scenery paths sequentially. The first terrain found for each tile is loaded. Objects for a tile are loaded from all directories visited before (and including the one where) the terrain was found.
The path can contain objects only, terrain only or combined scenery directories. The Airports and Model directories (which are late additions) complicates the scheme a bit as they can only be in combined terrain and objects directories.