fly/fgdata
1
0
Fork 0
Code Activity

updates/fixes

Browse source
This commit is contained in:
mfranz 2006-04-12 13:25:40 +00:00
parent 305001c033
commit ae7b90c439
1 changed files with 20 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
Docs/README.scenery
View file

@ -1,9 +1,10 @@
This file describes how to add static objects to the scenery as well as the
syntax of *.stg files.
This file describes how FlightGear searches and loads scenery, and how to
add static objects to the scenery as well as the syntax of *.stg files.
Contents:
Contents ----------------------------------------------------------------------
1 scenery path
2 terrasync
@ -149,7 +150,9 @@ so it may not be available/usable on MS Windows.
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. (See section 5 for how to find out which
geo coordinates belong to which tile.)
geo coordinates belong to which 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 in section 3.3.
@ -267,15 +270,16 @@ used directly. They have to be put in a pair of curly braces:
{right-down}
creates an arrow that points to the right and down. Single-letter-
glyph-names can be used that way, too, or in any mixture of both
methods:
creates an arrow that points to the right and down. Several glyph-names
can be put into a pair of braces, separated by commas (no space!).
Single-letter-glyph-names can be used that way, too, or in any mixture
of both methods:
EXIT
{E,X,I,T}
{E}{X}{I}{T}
EX{I,T}
E{X,I}T{right-down}
E{X,I}T{left-up,right-down}
Besides single- or multi-letter-glyph-names, there are also commands.
These always start with an '@'.
@ -289,7 +293,7 @@ the line is equivalent to
The following abbreviations are available -- all expand to arrows:
The following abbreviations are available -- all expand to arrow symbols:
abbrev. glyph-name
-----------------------------------------------------------------
@ -321,13 +325,13 @@ The following commands are available, for (A) sign properties:
and commands for (B) pre-defined sign types according to the FAA
specification (5345-44; see http://www.google.com/search?q=5345-44g).
@Y @Y1 @Y2 @Y3 yellow "Direction, Destination, Boundary" sign
@R @R1 @R2 @R3 red "Mandatory Instruction" sign
@L @L1 @L2 @L3 framed/black "Location" sign (yellow text/frame)
@B @B4 @B5 black "Runway Distance Remaining" sign
@Y @Y1 @Y2 @Y3 "Direction, Destination, Boundary" sign (black on yellow)
@R @R1 @R2 @R3 "Mandatory Instruction" sign (white on red with black outline)
@L @L1 @L2 @L3 "Location" sign (yellow text and frame on black)
@B @B4 @B5 "Runway Distance Remaining" sign (white on black)
The number versions define the panel heights according to the spec. If
they are omitted, then a default size is used (@Y3, @R3, @L3, @B4). If
the number is omitted, then a default size is used (@Y3, @R3, @L3, @B4). If
such a pre-defined sign type is used, then fgfs takes (more or less)
care of opening and closing frames, and of inserting the proper spaces.
(You can avoid this automatism by setting the sign properties yourself,
@ -401,8 +405,8 @@ are fixed and unchangeable at runtime.
4.1 static objects
-------------------
4.2 dynamic objects
--------------------
Any of the model properties can be made changeable at runtime by appending
"-prop" and using a property path name instead of the fixed value: