How to Use Track Triggers
m (→Creating a Trigger Event) |
m (→Creating a Trigger Event) |
||
Line 83: | Line 83: | ||
<td rowspan="2">[[file:EditSessionWindowX.JPG]]</td> | <td rowspan="2">[[file:EditSessionWindowX.JPG]]</td> | ||
<td><br> | <td><br> | ||
− | In the Edit Session window:- | + | In the Edit Session window (shown left):- |
− | * | + | *Click the '''Add''' button |
− | + | In Rule Selection window (shown below):- | |
− | * | + | *Scroll down the list to select the '''Trigger Check''' rule |
+ | *Click the '''Tick''' icon. | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 99: | Line 100: | ||
<td>[[file:TriggerCheck.JPG]]</td> | <td>[[file:TriggerCheck.JPG]]</td> | ||
<td><br> | <td><br> | ||
− | + | With the '''Trigger Check''' rule highlighted (shown left):- | |
+ | *Click the '''Edit''' button. This will open its properties window. | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 107: | Line 109: | ||
<table> | <table> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td rowspan="2">[[file:TriggerCheckProperties.JPG]]</td> | + | <td rowspan="2">[[file:TriggerCheckProperties.JPG]]<br> |
+ | <br> | ||
+ | Click the '''Tick''' icon '''Trigger Check''' properties window (shown above) to accept the changes.</td> | ||
<td><br> | <td><br> | ||
− | + | In the Trigger Properties window (shown left):- | |
− | + | *Click the '''''Add trigger''''' link | |
− | * | + | In the Trigger Selection window (shown below):- |
+ | *Select the trigger you have just added | ||
+ | *Click the '''Tick''' icon on the selection list | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 119: | Line 125: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | <br> | |
− | + | ||
==='''Giving the Trigger Event a Purpose'''=== | ==='''Giving the Trigger Event a Purpose'''=== |
Revision as of 12:02, 21 May 2018
Contents |
What are Triggers?
Triggers are invisible markers (invisible in Driver Mode but visible in Surveyor Mode) that are placed on a track. They can be programmed to "trigger an event" when a train (any train or a specific train) passes over them in Driver Mode.
The "event" is a message that is transmitted by the trigger to certain Session Rules that have been programmed to "listen" for the message. When one of those listening rules detects the message, it can be forced into action by executing preset instructions.
(left) A Track Trigger in place on a track visible in Surveyor Mode. The "5.00m" is the trigger detection radius |
Adding a Trigger
Configuring a Trigger
As soon as a new 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.
Triggers have a "detection radius" that controls how close a train has to approach to trigger the event. The smaller the radius the closer the train. This radius is set in the Advanced Properties section of the Tools window.
Creating a Trigger Event
Trigger events are handled by the Trigger Check Rule which is added to a session in the Session Editor.
The Trainz Wiki Link Trigger Check Rule contains detailed information on this rule.
To add the Trigger Check Rule to a session:-
|
In the Edit Session window (shown left):-
In Rule Selection window (shown below):-
|
|
This will add the Trigger Check rule to the session.
With the Trigger Check rule highlighted (shown left):-
|
For this example we will leave all settings unchanged and simply identify the trigger to be used.
Giving the Trigger Event a Purpose
To test your trigger event you will need to add at least one rule.
The Message Popup Rule has to be indented so that it becomes a Child of the Trigger Check Rule.
This should indent the Message Popup rule one level in (below). |
|
The Message Popup Rule is now controlled by the Trigger Check Rule but it still has to be configured to show a message.
- With the Message Popup Rule highlighted, click the Edit button.
Again, click the Tick icon to exit the Message Popup Rule then exit the Session Editor.
Add a consist to your layout a short distance from the trigger (but further away than its radius), save the surveyor session, and then test in Driver Mode.
Another example of using the Trigger Check Rule can be found in the Message Popup Rule Applications link below.