How to Use Track Triggers: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 924: | Line 924: | ||
</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> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:SkipMinorDown.png|link=#skipSetName20]][[image:SkipMinorUp.png|link=#skipAddS20]]</td> <!-- for Top and Minor Up/Down --> | |||
<td width=75> </td> | |||
<td width=75> </td> | |||
<td width=75> </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,228: | 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> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:SkipMinorDown.png|link=#skipSetLayer20]][[image:SkipMinorUp.png|link=#skipAddTrigger20]]</td> <!-- for Top and Minor Up/Down --> | |||
<td width=75> </td> | |||
<td width=75> </td> | |||
<td width=75> </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,290: | 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> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:SkipMinorDown.png|link=#skipSetDirection20]][[image:SkipMinorUp.png|link=#skipSetName20]]</td> <!-- for Top and Minor Up/Down --> | |||
<td width=75> </td> | |||
<td width=75> </td> | |||
<td width=75> </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,374: | 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> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:SkipMinorDown.png|link=#skipMove20]][[image:SkipMinorUp.png|link=#skipSetLayer20]]</td> <!-- for Top and Minor Up/Down --> | |||
<td width=75> </td> | |||
<td width=75> </td> | |||
<td width=75> </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,409: | 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> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:SkipMinorDown.png|link=#skipMoveVertically20]][[image:SkipMinorUp.png|link=#skipSetLayer20]]</td> <!-- for Top and Minor Up/Down --> | |||
<td width=75> </td> | |||
<td width=75> </td> | |||
<td width=75> </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,469: | 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> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:SkipMinorDown.png|link=#skipMoveHorizontally20]][[image:SkipMinorUp.png|link=#skipMove20]]</td> <!-- for Top and Minor Up/Down --> | |||
<td width=75> </td> | |||
<td width=75> </td> | |||
<td width=75> </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,550: | 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> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:SkipMinorDown.png|link=#skipSetRadius20]][[image:SkipMinorUp.png|link=#skipMoveVertically20]]</td> <!-- for Top and Minor Up/Down --> | |||
<td width=75> </td> | |||
<td width=75> </td> | |||
<td width=75> </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,633: | 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> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:SkipMinorDown.png|link=#stepCreating]][[image:SkipMinorUp.png|link=#skipMoveHorizontally20]]</td> <!-- for Top and Minor Up/Down --> | |||
<td width=75> </td> | |||
<td width=75> </td> | |||
<td width=75> </td> <!-- for Bottom --> | |||
</tr> | |||
</table> <!-- END Section Nav Buttons --> | |||
<table width=1000 bgcolor="lightcyan" cellpadding=2> | <table width=1000 bgcolor="lightcyan" cellpadding=2> | ||
Latest revision as of 07:28, 6 September 2026
|
What are Track Triggers? |
| 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 |
||||||||
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:-
|
||||||||
|
||||||||
Route or Session? |
| Track Triggers can be placed in a Route Layer or in a Session Layer |
|
| Information on Route Layers and Session Layers can be found at:- |
Adding a Track Trigger |
|
In Surveyor Classic (S10) |
| 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) |
|
|
||||||||||||||||||||||||||||||||||||||||
|
||||||||||
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:- | |||||||||||||
|
||||||||||||||
![]() |
|
|
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:-
|
![]() |
||||||||||
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:-
|
![]() |
||||||||||
|
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. |
|
|||||||||
| 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. |
![]()
|
|
||||||||||||||||||||||||||||||||||||||||||||||||
|
In Surveyor 2.0 (S20) |
|
Adding a Track Trigger (S20) |
|
| Steps: To Add a Track Trigger:- |
|
|
||||||||||||||||||||||||||||||||||||
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 |
|
Place the Track Trigger on the track.
|
|
||||||||||||||||||||||||||||||||||||||||
| 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 |
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"). |
![]() |
|
||||||||||||
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. | |||||||||||||||||||||||
![]() ![]() |
|
||||||||||||||||||||||
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:-
|
|||||||
Move it Along the Track (S20) |
| Track Triggers can be moved along the track or to other tracks. |
![]() |
|
||||||||||||||
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. |
![]() |
|
||||||||||||||||||||
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. |
![]() |
|
||||||||||||||||||||||
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. |
![]() |
|
||||||||||||||||||||||
| 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 |
Creating a Track Trigger Event |
| 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 |
|
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:
|
|||||||||
| Add the Trigger Check Rule: | ||||||||||
|
|
| 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:
|
|||||
Configure the Rule:
|
|||||||||||
| Select the Track Trigger: The Trigger Selection Window will open and list all the Track Triggers in your Route.
|
|||||||||
Adding an Instruction to the Trigger Event |
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:
|
||||||||||||||
Indent the Popup Message Rule:
|
Configuring the Message and Testing |
| Steps: To Use the Message Popup Rule:- | |||||
Open the Message Popup Rule for Editing:
|
|||||
|
|
|||||||||||||||||||||||||
| Left Click on the |
| The completed Message Popup Rule |
|
More information on this rule can be found on the Trainz Wiki Page at:- |
|
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 |
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:-
|
![]() |
There is a driver command that can be used in place of the Trigger Check Rule:-
|
Trainz Wiki
|
|
This page was created by Trainz user pware in May 2018 and was last updated as shown below.























