1
0
Fork 0

TREE_LIST documentation updates

Thanks to Rick Gruber-Riemer for proof-reading.
This commit is contained in:
Stuart Buchanan 2020-11-19 14:22:58 +00:00
parent dbc7fc7827
commit 37110ad34a

View file

@ -19,6 +19,7 @@ Contents ----------------------------------------------------------------------
3.7 ROAD_ROUGH / ROAD_DETAILED
3.8 RAILWAY_ROUGH / RAILWAY_DETAILED
3.9 BUILDING_LIST
3.10 TREE_LIST
4 model manager ("/models/model")
4.1 static objects
@ -280,8 +281,8 @@ this is an expensive operation and is strongly discouraged.
---------------------------------
defines taxiway or runway sign. The syntax is much like that of OBJECT_SHARED
entries, except that the path is replaced with a sign contents specification
and that there is an additional size value at the end of the line.
entries, except that the <object-path> is replaced with a sign contents specification
and that <radius> is replaced with a size value at the end of the line.
Example:
@ -392,7 +393,7 @@ gradually fade in
3.7 ROAD_ROUGH / ROAD_DETAILED
-------------------------------
Identical to BUILDING_ROUGH / BIULDING_DETAILED above, except used for roads.
Identical to BUILDING_ROUGH / BUILDING_DETAILED above, except used for roads.
the material definition "OSM_Road" is applied.
3.8 RAILWAY_ROUGH / RAILWAY_DETAILED
@ -463,7 +464,7 @@ For example, the following entries generates 3 small, 2 medium and 2 large build
0 400 0 0 1
0 500 0 0 2
3.9 TREE_LIST
3.10 TREE_LIST
------------------
Defines a file containing tree coordinates that should be rendered using
@ -485,7 +486,7 @@ Where:
the point at which the material definition will be evaluated (for regional
materials).
See README.materials for details on configuring the random building parameters.
See README.materials for details on configuring the random vegetation parameters.
The referenced <filename> (in the example trees.txt.gz) contains lines of the form