1,746
edits
Howto:Install scenery: Difference between revisions
Jump to navigation
Jump to search
m
Add link for environment variable
m (1) Emphasise the normal way to download scenery is automatically through TerraSync. 2) Add a note that old OSM2City objects in custom sceneries are very likely obsolete with the rollout on TerraSync) |
m (Add link for environment variable) |
||
| Line 124: | Line 124: | ||
==Technical details== | ==Technical details== | ||
===Scenery lookup and $FG_SCENERY=== | ===Scenery lookup and $FG_SCENERY=== | ||
FlightGear determines what scenery to use by looking at the environment variable <code>[[$FG SCENERY]]</code>. There can be more than one scenery path in the variable, for example one path to to TerraSync scenery and one path to custom scenery. Scenery can be overlapping and a tile will be loaded from the first path in <code>$FG SCENERY</code> from which it is available. | FlightGear determines what scenery to use by looking at the [[Environment variables|environment variable]] (setting)<code>[[$FG SCENERY]]</code>. There can be more than one scenery path in the variable, for example one path to to TerraSync scenery and one path to custom scenery. Scenery can be overlapping and a tile will be loaded from the first path in <code>$FG SCENERY</code> from which it is available. | ||
Should the paths in <code>$FG_SCENERY</code> not be valid, FlightGear falls back to <code>[[$FG ROOT]]/Scenery</code>. | Should the paths in <code>$FG_SCENERY</code> not be valid, FlightGear falls back to <code>[[$FG ROOT]]/Scenery</code>. | ||