How to Use Track Triggers
m |
m |
||
Line 1: | Line 1: | ||
The information in this Wiki Page applies to '''TANE''', '''TRS19''', '''Trainz Plus''' and '''TRS22'''. | The information in this Wiki Page applies to '''TANE''', '''TRS19''', '''Trainz Plus''' and '''TRS22'''. | ||
− | + | <table> | |
+ | <tr valign="top"> | ||
+ | <td> | ||
__TOC__ | __TOC__ | ||
+ | </td> | ||
+ | <td width=800> | ||
+ | <table cellpadding=4 bgcolor=#c1e7e7> | ||
+ | <tr valign="top"> | ||
+ | <td colspan=2><span style="font-size: 17px; font-weight: 700;">In Summary:</span></td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</td> | ||
+ | <td>'''Track Triggers are track markers that are invisible in ''Driver Mode'' but visible in ''Surveyor Mode'''''</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</td> | ||
+ | <td>'''Track triggers are used to activate ''Session Rules'' and some ''Driver Commands'''''</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</td> | ||
+ | <td>'''Track Triggers can be placed in a Route layer or in a Session layer'''</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
<table> <!-- BEGIN Nav Buttons Table --> | <table> <!-- BEGIN Nav Buttons Table --> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 14: | Line 39: | ||
<table cellpadding=4 bgcolor=#c1e7e7> | <table cellpadding=4 bgcolor=#c1e7e7> | ||
<tr> | <tr> | ||
− | |||
− | |||
− | |||
</table> | </table> | ||
Line 87: | Line 109: | ||
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
<td width=75>[[file:NextUp.png|link=#stepRoute|alt=Next Up|Top]]</td> | <td width=75>[[file:NextUp.png|link=#stepRoute|alt=Next Up|Top]]</td> | ||
− | <td width=75>[[file:NextDown.png|link=# | + | <td width=75>[[file:NextDown.png|link=#stepCreating|alt=Next Down|Next Down]]</td> |
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
Line 93: | Line 115: | ||
='''Adding a Track Trigger'''= | ='''Adding a Track Trigger'''= | ||
+ | |||
+ | =='''In Surveyor Classic (S10)'''== | ||
<table> | <table> | ||
Line 121: | Line 145: | ||
</table> | </table> | ||
<br> | <br> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
As soon as a new track trigger has been placed, its properties window will open on the screen. It will be given a default name and assigned to the currently active layer. | As soon as a new track trigger has been placed, its properties window will open on the screen. It will be given a default name and assigned to the currently active layer. | ||
Line 203: | Line 216: | ||
<td width=729><span id="stepCreating"></span> </td> | <td width=729><span id="stepCreating"></span> </td> | ||
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
− | <td width=75>[[file:NextUp.png|link=# | + | <td width=75>[[file:NextUp.png|link=#stepAdding|alt=Next Up|Top]]</td> |
<td width=75>[[file:NextDown.png|link=#stepEvent|alt=Next Down|Next Down]]</td> | <td width=75>[[file:NextDown.png|link=#stepEvent|alt=Next Down|Next Down]]</td> | ||
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> |
Revision as of 09:38, 24 December 2022
The information in this Wiki Page applies to TANE, TRS19, Trainz Plus and TRS22.
|
|
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 Trigger Check Rule (or a similar rule) or a Driver Command that is monitoring the track trigger.
Shown at left is a Track Trigger placed on a track in Surveyor Mode. It is NOT visible in Driver Mode. The "5.00m" shown below the trigger name is the trigger detection radius |
Route or Session?
Track Triggers can be placed in a Route layer or in a Session layer |
|
Information on Route and Session layers can be found at:- |
Adding a Track Trigger
In Surveyor Classic (S10)
|
As soon as a new track trigger has been placed, its properties window will open on the screen. It will be given a default name and assigned to the currently active layer.
|
||||||||||
Steps |
Name the Trigger:
|
|||||||||
(Optional) Set the Trigger Detection Radius:
|
Creating a Track Trigger Event
Track trigger events are handled by the Trigger Check Rule (or a similar 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 |
Open the Session Editor:
|
|||||||||
Add the Trigger Check Rule:
|
||||||||||
Open the Trigger Check Rule Properties:
|
||||||||||
Configure the Rule:
|
||||||||||
Select the Trigger:
|
Adding an Instruction to the Trigger Event
To test your trigger event you will need to add at least one rule.
Adding a Child Rule
Steps |
Add A Message Popup Rule:
|
|||||
Indent the Popup Message Rule:
|
Configuring the Message and Testing
Steps |
Open the Message Popup Rule for Editing:
|
|||||||
Configure the Message:
|
||||||||
(Optional) Add a Message Icon:
|
||||||||
Test the Trigger:
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 rules that can be used in place of the Trigger Check Rule and triggers. A few possibilities are listed below:- |
- 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.
- Trackside Check Rule - very similar to the Trigger Check Rule but provides some different options.
- Navigation Points (see the How to Guides link below) are more complex but provide more advanced controls and options.
- Multiple Resource Check Rule - monitors and acts on changes in multiple industry or multiple wagon resource (commodity) levels.
- Resource Verify Rule - monitors and acts on changes in a single industry or wagon resource (commodity) level.
- 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. |
- Wait For Trigger - forces an AI controlled train to wait until a specified trigger has been activated by another train.
Related Links
Trainz Wiki
More Tutorials and Guides to Using Trainz |
This page was created by Trainz user pware in May 2018 and was last updated as shown below.