"Attached-track" container
From TrainzOnline
(Difference between revisions)
(Re-structure to make page layout similar to others of this nature and to provide anchor links to tags. Information is largely unchanged.) |
m |
||
Line 20: | Line 20: | ||
===useadjoiningtracktype=== | ===useadjoiningtracktype=== | ||
:Type: Boolean | :Type: Boolean | ||
− | :Desc: | + | :Desc: If true (1) then the track type will change to match that of the first track joined to the object. |
===vertices=== | ===vertices=== |
Revision as of 16:36, 8 February 2014
The Attached-track container is used by KIND SceneryWithTrack to identify a list of track subcontainers. Each track derives its name from the subcontainer's tag name. These names are used from script. Each track is auto-generated spline track through attachment points located within the default mesh.
- Attached-tracks update automatically to the spline track connected to it in Surveyor. You may over-ride this auto-update feature by adding useadjoiningtracktype 0 (see below).
- Correct track end attachment orientation is essential. The Y axis must point ‘out’ at the correct angle. The Z axis must point ‘up’.
Contents |
Track subcontainer
Each track subcontainer supports the following tags and subcontainers. Each tag is shown here with its default value.
track (no default value, this must be track kuid) useadjoiningtracktype 1 vertices {}
track
- Type: Kuid
- Desc: Kuid of the track or spline to be used.
useadjoiningtracktype
- Type: Boolean
- Desc: If true (1) then the track type will change to match that of the first track joined to the object.
vertices
- Type: Vertices container
- Desc: This is a list of attachment points of where the track will be attached. Each entry must have a name.
Example Config.txt
Sample config.txt file for an industry asset, with the Standard Tags excluded for brevity:
{ kind industry attached-track { slc-spur { vertices { 0 "a.track0a" 1 "a.track0b" 2 "a.track0c" 3 "a.track0d" 4 "a.track0e" } track <kuid:-25:893> useadjoiningtracktype 1 } } attached-trigger { unload-trigger { att "a.unload-trigger" radius 2.00 track "slc-spur" } load-trigger { att "a.load-trigger" radius 2.00 track "slc-spur" } gate-trigger { radius 10.00 att "a.gate-trigger" track "slc-spur" } } }