230
edits
List of file formats: Difference between revisions
Jump to navigation
Jump to search
m
add *.stg section (mostly copied from README.scenery)
m (another blender comment) |
m (add *.stg section (mostly copied from README.scenery)) |
||
| Line 39: | Line 39: | ||
This creates SGI images with RLE compression by default. | This creates SGI images with RLE compression by default. | ||
= *.stg = | |||
This entry is copied from $FG_ROOT/Docs/README.scenery, which is part of FlightGear >0.9.10. | |||
stg files ("static terragear") define the static elements of a scenery "tile", including the terrain elevation data, airport geometry, and all static objects placed on this tile. Four of the available key words are followed by a string and four numbers. The meaning of these numbers is always the same and described under OBJECT_SHARED. | |||
=== OBJECT_BASE === | |||
specifies the terrain elevation data file. These files are generated with the [http://www.terragear.org/ TerraGear] and have file extension ".btg" ("binary terragear"; there used to be an "*.atg" file, too, where | |||
the 'a' stood for ASCII). | |||
Example: | |||
OBJECT_BASE 942050.btg | |||
The entry may be anywhere in the 942050.stg file, on a separate line. | |||
=== OBJECT === | |||
specifies an airport geometry 'drop-in' file. The scenery elevation file has cut out holes for airports, that are filled with such objects. They are usually called after the airport ICAO id: | |||
Example: | |||
OBJECT KSFO.btg | |||
These files are, again, created by TerraGear tools and are usually gzipped, so you'll find that file stored as KSFO.btg.gz. | |||
=== OBJECT_SHARED === | |||
add static object to the tile. | |||
Example: | |||
OBJECT_SHARED Models/Airport/tower.xml -122.501090 37.514830 15.5 0.00 | |||
Syntax: | |||
OBJECT_SHARED <object-path> <longitude> <latitude> <elevation-m> <heading-deg> | |||
The <object-path> is relative to the data directory (FG_ROOT). <elevation-m> is in meter and relative to mean sea-level (in the fgfs world). <heading-deg> is in degree, counter-clockwise with North being 0.0. Note | |||
that this differs from about every other place in FlightGear, most notably the /orientation/heading-deg entry in the property system, which is clockwise. OBJECT_SHARED models are cached and reused. They are only once in memory and never freed. (See also the next section.) | |||
=== OBJECT_STATIC === | |||
add static objects to the tile, just like OBJECT_SHARED. There are three differences to OBJECT_SHARED (apart from the name): | |||
* the path is relative to the tile directory where the *.stg file with this entry is located. For example, relative to 130n30/w123n37/. This usually means that all 3D object files, textures, and XML animation files are in this tile directory, too. | |||
* these objects are *not* cached and kept loaded, but rather freed with the tile (that is, when you leave that area). | |||
* the animation XML files may contain Nasal blocks <nasal><load> and <nasal><unload> which are executed on loading/unloading. | |||
Example: | |||
OBJECT_STATIC ggb-fb.xml -122.4760494 37.81876042 0 105 | |||
=== OBJECT_SIGN === | |||
defines taxiway or runway sign. The syntax is like that of OBJECT_SHARED entries, except that the path is replaced with a sign contents specification. This specification will probably be changed. Look at $FG_ROOT/Docs/README.scenery if you need to use this entry. | |||
=== OBJECT_RUNWAY_SIGN === | |||
are experimental entries. Don't use them! | |||