How to Use Track Triggers: Difference between revisions

From TrainzOnline
Jump to navigationJump to search
Pware (talk | contribs)
mNo edit summary
Pware (talk | contribs)
mNo edit summary
 
(3 intermediate revisions by the same user not shown)
Line 280: Line 280:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipAddTrigger10"></span>
===Adding a Track Trigger (S10)===
===Adding a Track Trigger (S10)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipSetName10]][[image:SkipMinorUp.png|link=#skipAddS10]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table bgcolor=#000000 cellpadding=2>
<table bgcolor=#000000 cellpadding=2>
Line 415: Line 427:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipSetName10"></span>
===Set its Name and Layers (S10)===
===Set its Name and Layers (S10)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipSetDirection10]][[image:SkipMinorUp.png|link=#skipAddTrigger10]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 537: Line 561:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipSetDirection10"></span>
===Change its Direction (S10)===
===Change its Direction (S10)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipMove10]][[image:SkipMinorUp.png|link=#skipSetName10]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 583: Line 619:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipMove10"></span>
===Move it Along the Track (S10)===
===Move it Along the Track (S10)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipSetRadius10]][[image:SkipMinorUp.png|link=#skipSetDirection10]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 643: Line 691:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipSetRadius10"></span>
===Set its Effect Radius (S10)===
===Set its Effect Radius (S10)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipAddS20]][[image:SkipMinorUp.png|link=#skipMove10]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 851: Line 911:
</table> <!-- END Nav Buttons Table -->
</table> <!-- END Nav Buttons Table -->
<br>
<br>
<table width=1000>
<table width=1000 bgcolor=#000000 cellpadding=2>
<tr valign="top">
<tr valign="top">
<td>'''Surveyor 2.0''' (or '''S20''') is the latest '''Surveyor''' interface and is supplied with '''TRS22PE''' and '''Trainz Plus'''.</td>
<td>
<table width=996 bgcolor=#ffffff cellpadding=2>
<tr valign="middle">
<td width=35>[[image:Information.png|35px|link=]]</td>
<td><span style="font-size: 15px;">'''Surveyor 2.0''' is currently only available for '''Trainz Plus''' and '''TRS22 Platinum'''.</span></td>
</tr>
</table>
</td>
</tr>
</tr>
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipAddTrigger20"></span>
===Adding a Track Trigger (S20)===
===Adding a Track Trigger (S20)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipSetName20]][[image:SkipMinorUp.png|link=#skipAddS20]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor=#000000 cellpadding=2>
<table width=1000 bgcolor=#000000 cellpadding=2>
Line 1,161: Line 1,240:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipSetName20"></span>
===Change its Name (S20)===
===Change its Name (S20)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipSetLayer20]][[image:SkipMinorUp.png|link=#skipAddTrigger20]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 1,223: Line 1,314:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipSetLayer20"></span>
===Assign it to Another Layer (S20)===
===Assign it to Another Layer (S20)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipSetDirection20]][[image:SkipMinorUp.png|link=#skipSetName20]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 1,307: Line 1,410:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipSetDirection20"></span>
===Change its Direction (S20)===
===Change its Direction (S20)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipMove20]][[image:SkipMinorUp.png|link=#skipSetLayer20]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 1,342: Line 1,457:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipMove20"></span>
===Move it Along the Track (S20)===
===Move it Along the Track (S20)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipMoveVertically20]][[image:SkipMinorUp.png|link=#skipSetLayer20]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 1,402: Line 1,529:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipMoveVertically20"></span>
===Move it Vertically (S20)===
===Move it Vertically (S20)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipMoveHorizontally20]][[image:SkipMinorUp.png|link=#skipMove20]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 1,433: Line 1,572:
<tr valign="top">
<tr valign="top">
<td width=25>[[image:Ablue.png|link=]]</td>
<td width=25>[[image:Ablue.png|link=]]</td>
<td>Using the [[image:S20_FineAdjustmentToolIcon.png|link=|20px]] '''Fine Adjustment Tool''' (press the <span style="font-weight: 700; font-size: 15px; color: white; background-color: black;">&#160;D&#160;</span> key) <span style="font-weight: 700; font-size: 15px; background-color: lightcyan;">&#160;Left Click and Drag&#160;</span> '''Forward''' or '''Backward''' on the <span style="font-weight: 700; font-size: 15px; color: white; background-color: blue;">&#160;Blue&#160;</span> '''Vertical Axis Line''' (labelled as [[image:DotPoint7Blue.png|link=]] in the image) to move it up or down '''OR'''</td>
<td>Using the [[image:S20_FineAdjustmentToolIcon.png|link=|20px]] '''Fine Adjustment Tool''' (press the <span style="font-weight: 700; font-size: 15px; color: white; background-color: black;">&#160;D&#160;</span> key) <span style="font-weight: 700; font-size: 15px; background-color: lightcyan;">&#160;Left Click and Drag&#160;</span> '''Forward''' or '''Backward''' on the <span style="font-weight: 700; font-size: 15px; color: white; background-color: blue;">&#160;Blue&#160;</span> '''Vertical Axis Line''' (labelled as [[image:DotPoint7Blue.png|link=]] in the image) to move it up or down.</td>
</tr>
<tr valign="top">
<td>&#160;</td>
<td><span style="font-weight: 700; font-size: 15px;">OR</span></td>
</tr>
</tr>
<tr valign="top">
<tr valign="top">
Line 1,479: Line 1,622:
</table>
</table>
<br>
<br>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipMoveHorizontally20"></span>
===Move it Horizontally (S20)===
===Move it Horizontally (S20)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#skipSetRadius20]][[image:SkipMinorUp.png|link=#skipMoveVertically20]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 1,518: Line 1,673:
<td width=25>[[image:DotPoint8Blue.png|link=]]</td>
<td width=25>[[image:DotPoint8Blue.png|link=]]</td>
<td>Select the [[image:S20_FineAdjustmentToolIcon.png|link=|20px]]&#160;'''Fine Adjustment Tool''' (the <span style="font-weight: 700; font-size: 17px; color: white;background-color: black;">&#160;D&#160;</span> key) and <span style="font-weight: 700; font-size: 15px; background-color: lightcyan;">&#160;Left Click and Drag&#160;</span> '''Forward''' or '''Backward''' on the <span style="font-weight: 700; font-size: 15px; color: white; background-color: red;">&#160;Red&#160;</span> '''Horizontal Axis Line''' attached to the '''Track Trigger''' to move it left or right of the track</td>
<td>Select the [[image:S20_FineAdjustmentToolIcon.png|link=|20px]]&#160;'''Fine Adjustment Tool''' (the <span style="font-weight: 700; font-size: 17px; color: white;background-color: black;">&#160;D&#160;</span> key) and <span style="font-weight: 700; font-size: 15px; background-color: lightcyan;">&#160;Left Click and Drag&#160;</span> '''Forward''' or '''Backward''' on the <span style="font-weight: 700; font-size: 15px; color: white; background-color: red;">&#160;Red&#160;</span> '''Horizontal Axis Line''' attached to the '''Track Trigger''' to move it left or right of the track</td>
</tr>
<tr valign="top">
<td>&#160;</td>
<td><span style="font-weight: 700; font-size: 15px;">OR</span></td>
</tr>
</tr>
<tr valign="top">
<tr valign="top">
Line 1,558: Line 1,717:
</table>
</table>
<br>
<br>
<span id="S20EffectRadius"></span>
<table width=1000> <!-- BEGIN Section Nav Buttons -->
<tr valign="top">
<td width=629><span id="skipSetRadius20"></span><span id="S20EffectRadius"></span>
===Set its Effect Radius (S20)===
===Set its Effect Radius (S20)===
</td>
<td width=50>&#160;</td>
<td width=50>&#160;</td>
<td width=46>[[image:SkipMinorDown.png|link=#stepCreating]][[image:SkipMinorUp.png|link=#skipMoveHorizontally20]]</td> <!-- for Top and Minor Up/Down -->
<td width=75>&#160;</td>
<td width=75>&#160;</td>
<td width=75>&#160;</td> <!-- for Bottom -->
</tr>
</table> <!-- END Section Nav Buttons -->


<table width=1000 bgcolor="lightcyan" cellpadding=2>
<table width=1000 bgcolor="lightcyan" cellpadding=2>
Line 2,014: Line 2,184:
<tr valign="top">
<tr valign="top">
<td width=25>[[image:Ablue.png|link=]]</td>
<td width=25>[[image:Ablue.png|link=]]</td>
<td>Scroll down the Texture Asset Selection List (shown below) to find a suitable icon, <span style="font-weight: 700; font-size: 15px;">OR</span></td>
<td>Scroll down the Texture Asset Selection List (shown below) to find a suitable icon</td>
</tr>
<tr valign="top">
<td>&#160;</td>
<td><span style="font-weight: 700; font-size: 15px;">OR</span></td>
</tr>
</tr>
<tr valign="top">
<tr valign="top">

Latest revision as of 07:28, 6 September 2026

Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 The information in this Wiki Page describes how to install, configure and use Track Triggers in TRS22 and Trainz Plus using both Surveyor 2.0 (S20) and Surveyor Classic (S10). The Surveyor Classic sections provide a basic guide only for TRS19 and T:ANE.


          Next Down Bottom
Key Points:-
Track Triggers are markers that are invisible in Driver but visible in Surveyor
They work on BOTH AI and manually controlled trains
They are used to activate certain Session Rules and Driver Commands
They can be placed in a Route or in a Session


Navigation Icons used in this Document
Top Bottom at Chapter Headings to jump to the top/bottom of the document
Next Up Next Down at Chapter Headings to jump to the next or previous Chapter
e.g. 1. to 2. to 3., etc
Next Up Skip Down within Chapters to jump to the next or previous Section
e.g. 3.1 to 3.2 and back to 3.1, etc
Up Down within Sections to jump to the next or previous Sub-section
e.g. 3.1.1 to 3.1.2 to 3.1.3, etc
 Link Internal link to another section within this document
 Link External link to another document


What are Track Triggers?

    Top   Next Down Bottom
Track Triggers can be programmed to respond when a train (any train or a specific train) passes over them in Driver Mode. The response comes from executing a set of Session Rules that have been attached to a Trigger Check Rule (or a similar rule) or a Driver Command that is monitoring the trigger.
Shown below left is a standard Track Trigger and below right is a Directional Track Trigger. They are just two examples of several types of Track Triggers. In both cases:-
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 they are visible in Surveyor and invisible in Driver
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 the "green wings" show their Effect Radius, the region where a consist will trigger an "event". The number in brackets show that radius in metres
the Directional Track Trigger will normally only be triggered if the consist is moving in the direction indicated by the arrow
the standard Track Trigger will be triggered regardless of the direction of movement although this can be modified in the triggers properties

"Standard" Track Trigger

Directional Track Trigger


Route or Session?

    Top Next Up Next Down Bottom
Track Triggers can be placed in a Route Layer or in a Session Layer


Notes:

Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Placing Track Triggers in a Route layer (e.g. in the same layer as the track) will save them with the Route and they will be available in all Sessions created using that particular Route
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Placing Track Triggers in a Session layer will save them with the current Session and they will only be available in that particular Session. This can be useful if two or more Sessions are being created and you do not want to use the same Track Triggers in each Session.


Information on Route Layers and Session Layers can be found at:-


Adding a Track Trigger

Skip Down   Top Next Up Next Down Bottom
Notes:

A Track Trigger has two important properties:-

Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 its name which is needed for all commands and rules that use the Track Trigger, and
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 its Effect Radius (the green "wings" shown in the image above with the radius value, in metres, shown below the Track Trigger name). This controls how closely a consist (AI or manually controlled) has to approach the marker to activate it (smaller radius = closer to the marker)
A "standard" Track Trigger has no visible direction and, while it can be rotated, this has NO EFFECT on its operation. The Directional Track Trigger does have a direction because it is only triggered by trains travelling in a specific direction


In Surveyor Classic (S10)

Skip Down Skip Up        
Surveyor Classic (or S10) is the original Surveyor interface supplied with every version of Trainz and is available as an option in TRS22PE and Trainz Plus.
The Surveyor Classic interface used here is the one found in Trainz Plus and TRS22PE. There are some differences from the Surveyor Classic interface found in older versions of Trainz.


Adding a Track Trigger (S10)

         
Track Triggers are Track Objects and have to be attached to a track segment. They can be moved along the track and to other tracks.


Steps: To Add a Track Trigger:-
Open the Tracks Tool Flyout (the  F4  key) and  Left Click  on the Trackmark Mode button (the  V  key)
 Left Click  on the Trigger object shown in the asset list
 Left Click  the  +  Add Object button - it may already be selected - or press the  A  key
 Left Click  on the track location where the Track Trigger is to be placed
Avoid placing a Track Trigger on a junction. You could accidentally place the Track Trigger on the wrong junction branch which means that it will have NO EFFECT if the targetted train is directed to the other branch
This will place the Track Trigger on the track and open its Properties Window (shown below). It will be given a default name and assigned to the currently active Layer.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You can edit the Name. This WILL affect its operation. See the section  Set its Name and Layers (S10) below.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127
You can change its Layer and/or Bound Layer. See the section  Set its Name and Layers (S10) below. Information on the Layer and the Bound Layer settings can be found at:-
 How to Use Layers.
WARNING:
Switching an objects Layer between a Route Layer and a Session Layer will change where it is saved (in the Route or the Session).
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You can reverse the direction it points. For a Directional Track Trigger this WILL affect its operation but for a "standard" non-Directional Track Trigger this does NOT affect its operation. See the section  Change its Direction (S10) below.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You can adjust its position on the track by dragging it along the track or to another track. See the section  Move it Along the Track (S10) below.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You can also adjust its Effect Radius. This WILL affect its operation. See the section  Set its Effect Radius (S10) below.


Notes: Deleting a Track Trigger

Steps: To Delete a Track Trigger:-
If they are not already open and selected, open the Track Tools Flyout (the  F4  key) and the Trackmark Mode (the  V  key).
 Left Click  on the Delete icon.
 Left Click  on the Track Trigger.


Set its Name and Layers (S10)

         
The name of a Track Trigger is important. It is used to identify the marker for Session Rules and Driver Commands
The Layer it is assigned to will decide if will be saved in a Route or in a Session


The Name and Layer Settings for a Track Trigger are in its Properties Window.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 The Properties Window will open as soon as a new Track Trigger has been added to a track segment.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 To open the Properties Window for an existing Track Trigger:-
Steps: To Open the Properties Window for an Existing Track Trigger:-
In the Track Tools Flyout (the  F4  key) select Trackmark Mode (the  V  key)
 
 Left Click  on the  ?  icon.
 Left Click  on the Track Trigger to open its Properties Window.


Track Triggers are used in Driver Commands and Session Rules so they MUST be given unique names.


To change the Track Trigger name  Left Click  on the name text entry box, delete the current name and enter a new name.
Use a simple but recognisable name for the Track Trigger. It will help locate it in the Route or Session and make it easy to remember when used in Session Rules and Driver Commands.
To change its Layer and/or its Bound Layer  Left Click  on the approprite layer text entry box (or use its scroll arrowheads) and select a new layer. Information on the Layer and the Bound Layer settings can be found at:-
 How to Use Layers
WARNING:
Switching an objects Layer between a Route Layer and a Session Layer will change where it is saved (in the Route or the Session).
To confirm the changes  Left Click  on the icon or the  Save Changes  button (depending on your Trainz version) at the bottom of the window OR click on the icon or  Cancel  button to cancel the changes. Both actions will close the Properties Window.


Change its Direction (S10)

         
Except for the Directional Track Trigger, the direction a Track Trigger is pointing has NO EFFECT on its operation.


If you need to change the direction of a Track Trigger then:-
Steps: To Reverse the Direction of a Track Trigger:-
In the Track Tools Flyout (the  F4  key) select Trackmark Mode (the  V  key)
Then select the Rotate Trackmark Tool (the  R  key)
 Left Click  on the Track Trigger
 


Move it Along the Track (S10)

         
Track Triggers can be dragged along the track and moved to other tracks.


If you need to move a Track Trigger then:-
Steps To Move a Track Trigger to a New Position or to Another Track:-:
In the Track Tools Flyout (the  F4  key) select Trackmark Mode (the  V  key)
Then select the Move Trackmark Tool (the  M  key)
 Left Click and Drag  on the Track Trigger to its new position.
It will follow track curves and height changes as it moves.
 


When dragging a marker from one track to another it will not move until the mouse pointer is over, or very close to, the second track when the marker will instantly jump across.


Set its Effect Radius (S10)

         
The Effect Radius sets how close a consist has to approach the marker to activate its operation. The default value is 20m.


The Effect Radius controls for a Track Trigger are in the Tools Menu Advanced Window.


Steps: To Open the Advanced Tools Window:-
In the Track Tools Flyout (the  F4  key) select Trackmark Mode (the  V  key)
 Left Click  on the  Advanced  label at the bottom of the Track Tools Flyout.
This will open the Advanced Tools Window (shown below).


The Effect Radius is the size of the green "effect wings" attached to both ends of the marker. This sets how close a consist has to approach the marker to activate the trigger. The smaller the radius the closer it must approach.



Other Track Objects that have an Effect Radius include:-
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127  Track Direction Markers
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127  Track Markers
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127  Priority Markers
Steps: To Set a Track Triggers Effect Radius:-
In the Advanced Tools popout (see Steps above) you will have a choice of 4 methods to set and adjust the Effect Radius
Options: Choose one of:-
To copy the Effect Radius of an existing Track Trigger
 Left Click  the Get Effect Radius icon
 Left Click  on the Track Trigger whose radius you want to copy - the radius will be copied into the Effect Radius Value text box (the default value is 20.00 metres)
To apply the new value see option below
To manually alter the Effect Radius value
Type the new value (in metres) into the Effect Radius Value text box
To apply the new value see option below
To apply a value in the Effect Radius Value text box (from methods , or ) to another Track Trigger
 Left Click  the Copy Radius Value icon
 Left Click  on the Track Trigger that is to receive the new value (you can click on more than one)
To adjust the Effect Radius value up or down
 Left Click  the Adjust Effect Radius button
Select the Track Trigger
 Left Click and Drag  Forward (to increase the value) or Backward (to reduce the value)
The new value will be immediately applied to the selected Track Trigger as the mouse moves (but only one Track Trigger at a time)


Once you have an Effect Radius entered in the value box, you can apply it to any number of Track Triggers by using method shown above


In Surveyor 2.0 (S20)

Skip Down Skip Up        


Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Surveyor 2.0 is currently only available for Trainz Plus and TRS22 Platinum.


Adding a Track Trigger (S20)

         
Track Triggers are Track Objects and have to be attached to a track segment. The Track Trigger object can be moved along the track and off the track (left, right, above, below) but its attachment point is always connected to a track segment.


Steps: To Add a Track Trigger:-
In the Filter Palette either:-
 Left Click  on the Track Objects icon

OR
 Left Click  on the Content Drop Down Box


Then select Track Objects

 Shortcut  If you already have a Track Trigger placed in your route then:-
move the tool pointer over the existing Track Trigger object and hold down the  Alt  key. The object name will appear in a ToolTip attached to the pointer
while holding down the  Alt  key  Left Click  on the Track Trigger to identify it in the Assets Palette and to select the Placement Tool. Release the key.
Jump to Step below.
Notes:

If the Filter Palette and the Assets Palette are not shown on the screen, then:-

Windows Menu
Steps To Display Palettes:-:
open the Window Menu from the menu icons at the top of the screen
 
visible palettes have ticks next to their names
invisible (hidden) palettes have no ticks next to their names
if any required palette does not have a tick next to its name then  Left Click  on the name of the palette or on the empty box next to its name. This will add a and make the palette visible

There is a Trainz Wiki Page specifically covering the S20 Palettes at
 How to Use the Surveyor 2.0 Palettes


In the Assets Palette to narrow down the filter list, type "trigger" (UPPER/lower case does not matter) in the Search Text Box


Both pallets shown docked


This will list all the Track Objects containing the text "trigger" in their names or descriptions.
 Left Click  on the item named Trigger (or another Trigger object) in the list - you may have to scroll down the list to find the asset.


If you are not sure about an asset then  Double Left Click  on the name to bring up its image and description.

When you select any Track Object asset in the Assets Palette list it will automatically select the Placement Tool so the next  Left Click  on a track will add that asset to your Trainz World

Place the Track Trigger on the track.


Notes: Deleting a Track Trigger

Steps: To Delete a Track Trigger:-
select either the:-
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Free Move Tool (or press the  S  key) OR
the Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Fine Adjustment Tool (or press the  D  key)
 Left Click  on the Track Trigger to be deleted
press the  Delete  key
Steps: To Add a Track Trigger:-
If, for some reason, the Placement Tool has not been selected then:-
 Left Click  on the Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Placement Tool (or press the  E  key).
 Left Click  on the track at the position where you want to place the Track Trigger.
Avoid placing a Track Trigger on a junction. You could accidentally place the Track Trigger on the wrong junction branch which means that it will have NO EFFECT if the targetted train is directed to the other branch.
This will place the Track Trigger on the track. It will be given a default name and assigned to the currently active Layer.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You can edit its Name. This WILL affect its operation. See the section  Change its Name (S20) below.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127
You can open its Layer and/or its Binding Layer and select new layers. See the section
 Assign it to Another Layer (S20) below.
See  How to Use Layers for information on the Layer and Binding Layer settings.
WARNING:
Switching an objects Layer between a Route Layer and a Session Layer will change where it is saved (in the Route or the Session).
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You can reverse the direction it points. For standard (non-directional triggers) This does NOT affect its operation but for a Directional Track Trigger this WILL affect its operation. See the section  Change its Direction (S20) below.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You can adjust its position on the track by dragging it along the track or to another track. See the section  Move it Along the Track (S20) below.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You can adjust its Effect Radius. This WILL affect its operation. See the section  Set its Effect Radius (S20) below.


Once you have added a Track Trigger and set its properties it can be quickly duplicated (Cloned) in Surveyor 2.0 with those properties and moved to a new location. You can then easily edit the name and properties of the clone at the new location. See  How to Use S20 Tools - Cloning Objects for the details.


Change its Name (S20)

         
The name of a Track Trigger is used to identify it for Driver Commands (e.g. Wait on Trigger) and Session Rules (e.g. Trigger Check Rule).


Track Triggers can be renamed to give them a more recognisable identity (e.g. ""East Branch Down" instead of "Trigger 4608").


Steps: To Change the Name of a Track Trigger:-
using either the Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Free Move Tool or the Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Fine Adjustment Tool select ( Left Click  on) the Track Trigger to be renamed
in the Info Palette (you may need to make this palette visible - see the Notes: for Step  1  above)  Left Click  in the Name: entry box. Enter a name for the Track Trigger and press the  Enter  key.
Use a simple but recognisable name for the Track Trigger. It will help locate it in the Route or Session and make it easy to remember when used in Session Rules and Driver Commands.


Track Triggers used for Driver Commands and Session Rules MUST be given unique names.


Assign it to Another Layer (S20)

         
The layer assigned to a Track Trigger will control where it is saved, in the Route or the Session.


The Info Palette will show the layer assigned to the currently selected object. To the left of the layer name is a small arrowhead object.
Info palette

Layer control
Steps: To Assign a Track Trigger to a Layer:-
In the Info Palette:-
 Left Click  the small arrowhead next to the layer name. This will open the layer properties for the selected object
 Left Click  the Layer drop down box to select a new layer for the object
if required,  Left Click  the Binding drop down box to select a new binding layer for the object. It cannot be bound to its own layer
if required,  Left Click  the  Lock Layer  button to lock the selected layer. If the layer is already locked then this will be shown as an  Unlock Layer  button


WARNING:
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 You will not be allowed to place a track object in a layer that is higher up the list than the layer containing the track
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Moving an object from one layer group to another (e.g. from the Route Layer Group to the Session Layer Group) will change where the object is saved (in the Route or in the Session)


Information on layers can be found at:-


Change its Direction (S20)

         
Except for the Directional Track Trigger, the direction a Track Trigger is pointing has NO EFFECT on its operation.


If you need to rotate a Track Trigger to face the opposite direction then:-
Steps: To Reverse the Direction of a Track Trigger:-
select the Track Trigger then  Left Click  on its  Context Menu Icon (or press the  T  key)
from the popup menu select the  Rotate Trackside  option


Move it Along the Track (S20)

         
Track Triggers can be moved along the track or to other tracks.


Steps: To Move the Track Trigger:-
 Left Click and Drag  Forward or Backward on the Yellow Dot, its Attachment Point, next to the Track Trigger or on the object itself (see Notes: below), to move it along the track or to another track


Notes:

Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 If you drag the object itself and not its Attachment Point then it will stay at its original height as it is moved along the track. If the track is on a grade then the object will rise above or fall below the track as it is moved. To return the object to its correct height on the track see the next section Move it Vertically (S20) below.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Dragging it by the attachment point will force it to stay at the height of the track as it is moved.


Move it Vertically (S20)

         
Track Triggers can be physically placed above or below the track.


This feature allow a marker to be placed, for example, above the track so that it will not be hidden in Surveyor if a consist is parked on the marker. A change in height will have NO EFFECT on its operation.
Steps: To Move a Track Trigger Vertically Choose Option OR :-
Using the Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Fine Adjustment Tool (press the  D  key)  Left Click and Drag  Forward or Backward on the  Blue  Vertical Axis Line (labelled as in the image) to move it up or down.
  OR
In the  Info Palette  enter a value in the  Height  setting and press the  Enter  key.
NOTE: the height is measured from the absolute 0m level and not from the current height of the object or the track.



If you need to return the Track Trigger to its original height then:-
Steps: To Correctly Reattach the Track Trigger to the Track:-
select the object and open ( Left Click  on) its  Context Menu Icon (or press the  T  key)
from the popup menu select  Reattach to Track 


Move it Horizontally (S20)

         
Track Triggers can be physically placed left or right of the track.


This feature allow a marker to be placed so that it will not be hidden in Surveyor if a consist is parked on the marker. A change in position left or right will have NO EFFECT on its operation.
Steps: To Move a Track Trigger Horizontally:-
Track Objects can be moved along the track using the method shown in the section  Move it Along the Track above OR sideways from the track using steps OR listed below.
Select the Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Fine Adjustment Tool (the  D  key) and  Left Click and Drag  Forward or Backward on the  Red  Horizontal Axis Line attached to the Track Trigger to move it left or right of the track
  OR
Select the Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Fine Adjustment Tool (the  D  key) and  Left Click and Drag  Forward or Backward on the  Green  Horizontal Axis Line attached to the Track Trigger to move it forward or back in a straight line that will ignore any curves in the track


If you need to return the Track Trigger to its original position then:-
Steps: To Correctly Reattach the Track Trigger to the Track:-
select the object and open ( Left Click  on) its  Context Menu Icon (or press the  T  key)
from the popup menu select  Reattach to Track 


Set its Effect Radius (S20)

         
The Effect Radius sets how close a consist has to approach a Track Trigger to activate or complete its operation. The default value is 20m.


The Effect Radius is the size of green "effect wings" attached to both ends of the trigger. This sets how close a consist has to approach the trigger to complete certain Driver Commands (such as Wait on Trigger) or activate certain Session Rules (such as Trigger Check Rule). The smaller the radius the closer it must approach.


In the image shown below, the approaching vehicle will "reach" the Track Marker when it is 20m away from it.
Steps: To Adjust the Effect Radius Of a Track Trigger:-
 Left Click and Drag  on the Green Dot next to the Track Trigger.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Drag it Left or Right (at 90° to the direction of the track) to change its Effect Radius.
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 The speed at which you drag it will set the speed at which the radius value will change - faster movements will give larger value changes.
For the best results when adjusting the Effect Radius of any track object, move your camera POV (point of view) to directly above the object


Other Track Objects that have an Effect Radius include:-
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127  Track Direction Markers
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127  Track Markers
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127  Priority Markers


Once you have set the Effect Radius of a Track Trigger it can be quickly duplicated (cloned) in Surveyor 2.0 with those settings and moved to a new location. You can easily edit the name and properties of the clone at the new location. See  How to Use S20 Tools - Cloning Objects for the details


Creating a Track Trigger Event

  Skip Up Top Next Up Next Down Bottom
When a consist enters the Effect Radius of a Track Trigger it will create an "event" that can be detected and responded to by some Session Rules and some Driver Commands. One such rule is the Trigger Check Rule which is added to a Session in the Session Editor.

More information on the Trigger Check Rule can be found on the Trainz Wiki Rules Page at:-


Steps: To Create a Trigger Event:-
Open the Session Editor:
To add the Trigger Check Rule to a session:-
Open the Surveyor Main Menu in TANE (shown below left) or the Surveyor Edit Menu in TRS19 and later Trainz versions (shown below right)
Select the option  Edit Session  from the drop down menu list

Add the Trigger Check Rule:
 
In the Edit Session window (shown below left)  Left Click  on the  Add  button
In the Rule Selection window (shown below right):-
Scroll down the list to select the Trigger Check rule, and
 Left Click  on the icon
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127

This will add the Trigger Check Rule to the session.
Open the Trigger Check Rule Properties:
With the Trigger Check Rule highlighted (shown below)  Left Click  the  Edit  button. This will open the rule Properties Window
Configure the Rule:
For this example we will leave all settings unchanged and simply identify the Track Trigger to be used.
In the Trigger Properties Window (shown below):-
 Left Click  on the Add Trigger link

More information on the settings and options in this rule can be found on the Trainz Wiki Rules Page at:-

Select the Track Trigger:

The Trigger Selection Window will open and list all the Track Triggers in your Route.

Select the Track Trigger you have just added
 Left Click  on the icon at the bottom of the selection window
Once the Track Trigger has been added to the rule,  Left Click  on the icon in the Trigger Check Properties Window to accept the change and close the Session Editor.


Adding an Instruction to the Trigger Event

Skip Down   Top Next Up Next Down Bottom

Adding a Child Rule

To test your Trigger Event you will need to add some Session Rules.

Steps: To Test a Trigger Event:-
Add A Message Popup Rule:
When you are back in the Session Editor window:-
Make sure that the new Trigger Check Rule is selected (highlighted)
 Left Click  the  Add  button to add another new rule
Scroll down the rule selection window to find and select the Message Popup rule
 Left Click  on the icon
The Message Popup Rule should now appear directly below the Trigger Check rule. It will display a red cross because it has not yet been configured.
Indent the Popup Message Rule:
The Message Popup Rule has to be indented so that it becomes a Child of the Trigger Check Rule and is controlled by that rule.
With the Message Popup Rule highlighted  Left Click  on the Indent (right arrow) button. This should indent the Message Popup rule one level inwards (as shown below).

The Message Popup Rule is now a Child Rule of the Trigger Check Rule and will only be executed after the Track Trigger has been activated by a train.


Configuring the Message and Testing

Skip Down Skip Up        
Steps: To Use the Message Popup Rule:-
Open the Message Popup Rule for Editing:
With the Message Popup Rule highlighted and indented (as shown above)  Left Click  the  Edit  button. The Message Popup Rule Properties Window will appear (as shown below)

Configure the Message:
Set the properties as shown:-
Check ON Close previous message popup windows
Select Option Button Custom text
Enter a short text message
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127
(Optional) Add a Message Icon:
 Left Click  the link click here to set (shown left) and either:-
Scroll down the Texture Asset Selection List (shown below) to find a suitable icon
  OR
Simply type "icon stop" in the text box to use one of the builtin icons
 Left Click  on the icon to select the icon
 Left Click  on the icon to exit the Message Popup Rule and return to the Session Editor
The completed Message Popup Rule


More information on this rule can be found on the Trainz Wiki Page at:-


 Test the Trigger Event:
Exit the Session Editor
Add a consist to your layout a short distance from the Track Trigger (but further away than its Effect Radius), save the Surveyor Session, and then test in Driver


Another example of using the Trigger Check Rule can be found in the Trainz Wiki Page How to Use Message Popup Rule (Applications).

Alternatives to the Trigger Check Rule

  Skip Up Top Next Up   Bottom
There are other Session Rules that can be used in place of the Trigger Check Rule and Track Trigger. A few possibilities are listed below:-
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Directional Trigger Check Rule - identical to the Trigger Check Rule but adds the ability to test the train direction. Requires the use of a special Directional Trigger. For an example of its use see the Trainz Wiki Page Controlling Signals in Sessions
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Trackside Check Rule - very similar to the Trigger Check Rule but provides some different options
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Navigation Points (see the How to Guides below) are more complex but provide more advanced controls and options
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Multiple Resource Check Rule - monitors and acts on changes in multiple industry or multiple wagon resource (commodity) levels
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Resource Verify Rule - monitors and acts on changes in a single industry or wagon resource (commodity) level
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Timecheck Rule - triggers an event at a set time.


There is a driver command that can be used in place of the Trigger Check Rule:-
Error creating thumbnail: /bin/bash: line 1: /usr/bin/convert: No such file or directory Error code: 127 Wait For Trigger - forces an AI controlled train to wait until a specified Track Trigger has been activated by another train
  Top Next Up    


Trainz Wiki

More Tutorials and Guides to Using Trainz

Related Links


This page was created by Trainz user pware in May 2018 and was last updated as shown below.