392
edits
$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)
m (specifing whgere to set the --fg-scenery option) |
m (corrected: scenery paths separated by colon, not semicolon (http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438&start=360#p182311)) |
||
| Line 7: | Line 7: | ||
== Multiple directories == | == Multiple directories == | ||
Directories are being read from left to right. For each scenery tile, FlightGear will check whether it exists in the first directory. If not, it will move on to the second directory and so on. Directories should be seperated by | Directories are being read from left to right. For each scenery tile, FlightGear will check whether it exists in the first directory. If not, it will move on to the second directory and so on. Directories should be seperated by colons, like: | ||
--fg-scenery=Scenery/Custom | --fg-scenery=Scenery/Custom:Scenery/TerraSync | ||
So, FlightGear searches the scenery path in order. 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. | So, FlightGear searches the scenery path in order. 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. | ||