How to Use Track Triggers

From TrainzOnline
(Difference between revisions)
Jump to: navigation, search
m (→‎Related Links)
m
Line 2: Line 2:
  
 
__TOC__
 
__TOC__
 +
<table> <!-- BEGIN Nav Buttons Table -->
 +
<tr valign="top">
 +
<td width=729><span id="stepWhat"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>&nbsp;</td>
 +
<td width=75>[[file:NextDown.png|link=#stepRoute|alt=Next Down|Next Down]]</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 +
</tr>
 +
</table> <!-- END Nav Buttons Table -->
 
='''What are Track Triggers?'''=
 
='''What are Track Triggers?'''=
 
<table cellpadding="4" bgcolor=#c1e7e7>
 
<table cellpadding="4" bgcolor=#c1e7e7>
Line 19: Line 28:
 
</tr>
 
</tr>
 
</table>
 
</table>
−
<br>
+
<table> <!-- BEGIN Nav Buttons Table -->
−
 
+
<tr valign="top">
 +
<td width=729><span id="stepRoute"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepWhat|alt=Next Up|Top]]</td>
 +
<td width=75>[[file:NextDown.png|link=#stepAdding|alt=Next Down|Next Down]]</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 +
</tr>
 +
</table> <!-- END Nav Buttons Table -->
 
='''Route or Session?'''=
 
='''Route or Session?'''=
  
Line 38: Line 54:
 
</tr>
 
</tr>
 
</table>
 
</table>
−
<br>
+
 
 
<table cellpadding="4" bgcolor="Aquamarine">
 
<table cellpadding="4" bgcolor="Aquamarine">
 
<tr valign="top">
 
<tr valign="top">
Line 47: Line 63:
 
</tr>
 
</tr>
 
</table>
 
</table>
−
 
+
<table> <!-- BEGIN Nav Buttons Table -->
−
<table width="100%">
+
 
<tr valign="top">
 
<tr valign="top">
−
<td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
+
<td width=729><span id="stepAdding"></span>&nbsp;</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:NextDown.png|link=#stepConfiguring|alt=Next Down|Next Down]]</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 
</tr>
 
</tr>
−
</table>
+
</table> <!-- END Nav Buttons Table -->
−
 
+
 
='''Adding a Track Trigger'''=
 
='''Adding a Track Trigger'''=
  
Line 82: Line 100:
 
</tr>
 
</tr>
 
</table>
 
</table>
−
<br>
+
<table> <!-- BEGIN Nav Buttons Table -->
−
<table width="100%">
+
 
<tr valign="top">
 
<tr valign="top">
−
<td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
+
<td width=729><span id="stepConfiguring"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepAdding|alt=Next Up|Top]]</td>
 +
<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>
 
</tr>
 
</tr>
−
</table>
+
</table> <!-- END Nav Buttons Table -->
−
 
+
 
='''Configuring a Track Trigger'''=
 
='''Configuring a Track Trigger'''=
  
Line 150: Line 170:
 
</tr>
 
</tr>
 
</table> <!-- END Steps Table -->
 
</table> <!-- END Steps Table -->
−
<table width="100%"> <!-- BEGIN Back-To-Top Table -->
+
<table> <!-- BEGIN Nav Buttons Table -->
 
<tr valign="top">
 
<tr valign="top">
−
<td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
+
<td width=729><span id="stepCreating"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepConfiguring|alt=Next Up|Top]]</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>
 
</tr>
 
</tr>
−
</table> <!-- END Back-To-Top Table -->
+
</table> <!-- END Nav Buttons Table -->
−
 
+
 
='''Creating a Track Trigger Event'''=
 
='''Creating a Track Trigger Event'''=
  
Line 303: Line 326:
 
</tr>
 
</tr>
 
</table> <!-- END Step Table -->
 
</table> <!-- END Step Table -->
−
<table width="100%"> <!-- BEGIN Back-To-Top Table -->
+
 
 +
<table> <!-- BEGIN Nav Buttons Table -->
 
<tr valign="top">
 
<tr valign="top">
−
<td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
+
<td width=729><span id="stepEvent"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepCreating|alt=Next Up|Top]]</td>
 +
<td width=75>[[file:NextDown.png|link=#stepAlternatives|alt=Next Down|Next Down]]</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 
</tr>
 
</tr>
−
</table> <!-- END Back-To-Top Table -->
+
</table> <!-- END Nav Buttons Table -->
−
 
+
 
='''Adding an Instruction to the Trigger Event'''=
 
='''Adding an Instruction to the Trigger Event'''=
−
To test your trigger event you will need to add at least one rule.<br><br>
+
To test your trigger event you will need to add at least one rule.
  
 
==Adding a Child Rule==
 
==Adding a Child Rule==
Line 369: Line 396:
 
</tr>
 
</tr>
 
</table> <!-- END Steps Table -->
 
</table> <!-- END Steps Table -->
−
<table width="100%"> <!-- BEGIN Back-To-Top Table -->
 
−
<tr valign="top">
 
−
<td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 
−
</tr>
 
−
</table> <!-- END Back-To-Top Table -->
 
−
 
 
==Configuring the Message and Testing==
 
==Configuring the Message and Testing==
  
Line 474: Line 495:
 
</table> <!-- END Steps Table -->
 
</table> <!-- END Steps Table -->
  
−
<table width="100%">
+
<table> <!-- BEGIN Nav Buttons Table -->
 
<tr valign="top">
 
<tr valign="top">
−
<td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
+
<td width=729><span id="stepAlternatives"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepEvent|alt=Next Up|Top]]</td>
 +
<td width=75>&nbsp;</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 
</tr>
 
</tr>
−
</table>
+
</table> <!-- END Nav Buttons Table -->
−
 
+
 
='''Alternatives to the Trigger Check Rule'''=
 
='''Alternatives to the Trigger Check Rule'''=
  
Line 520: Line 544:
 
</tr>
 
</tr>
 
</table>
 
</table>
−
<table width="100%">
+
<table> <!-- BEGIN Nav Buttons Table -->
 
<tr valign="top">
 
<tr valign="top">
−
<td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
+
<td width=729><span id="bottom"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepAlternatives|alt=Next Up|Top]]</td>
 +
<td width=75>&nbsp;</td>
 +
<td width=75>&nbsp;</td>
 
</tr>
 
</tr>
−
</table>
+
</table> <!-- END Nav Buttons Table -->
 
----
 
----
 
----
 
----

Revision as of 09:12, 19 August 2021

The information in this Wiki Page applies to TANE, TRS19 and Trainz Plus.

Contents

  Top   Next Down Bottom

What are Track Triggers?

DotPoint.JPG Track triggers are track markers that are invisible in Driver Mode but visible in Surveyor Mode. They are used to activate Session Rules and some Driver Commands

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 WikiLink.PNG Trigger Check Rule (or a similar rule) or a Driver Command that is monitoring the track trigger.

TrackTrigger.JPG

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

  Top Next Up Next Down Bottom

Route or Session?

DotPoint.JPG Track Triggers can be placed in a Route layer or in a Session layer


NotePad.PNG Notes:
  • Placing Track Triggers in a Route layer (e.g. in the same layer as the track) means that they will be available in all Sessions created using that particular Route.
  • Placing Track Triggers in a Session layer means that they will only be available in that Session. This can be useful if two or more Sessions are being created and you want to use different Track Triggers in each Session.
LinkWiki.PNG Information on Route and Session layers can be found at:-
  Top Next Up Next Down Bottom

Adding a Track Trigger

TrackTriggerMode.JPG
Steps.PNG Steps:

A Track Trigger is placed on the track by:-

  1. clicking the Track tool,
  2. clicking the Trackmark Mode button,
  3. selecting the Trigger object from the list of installed objects,
  4. clicking the Add Object button,
  5. clicking the track position where the track trigger is to be placed.
  Top Next Up Next Down Bottom

Configuring a Track Trigger

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.PNG

Steps		 DotPoint1.JPG Name the Trigger:
TrackTriggerProperties.JPG
  • To change the track trigger name click on the name box, delete the highlighted default name and enter a new name
  • To change the assigned layer click on the layer box and select a new layer
  • Leave the "Bound Layer" at <none>. (See the Trainz Wiki Page WikiLink.PNG Using Layers for information on layers)
  • To confirm the changes click on the Tick.PNG icon on the bottom right of the window
  DotPoint2.JPG (Optional) Set the Trigger Detection Radius:
Track triggers have a "detection radius" that controls how close a train has to approach to trigger the event. The default radius is 20 metres. The smaller the radius the closer the train has to be to the track trigger to be detected. This radius is set in the Advanced Properties section of the Tools window (shown below).
TrackTriggerRadius.JPG
  1. Click the Advanced Tab to open its properties
  2. Enter a new radius value in metres
  3. Click the Set Trigger Radius button
  4. Click on the track trigger to assign its new radius


PencilTips.PNG A small radius should only be used for slower moving trains. Short fast trains may pass over a small radius track trigger without being detected.
  Top Next Up Next Down Bottom

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 WikiLink.PNG Session Editor.

LinkWiki.PNG

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


Steps.PNG

Steps		 DotPoint1.JPG Open the Session Editor:

To add the Trigger Check Rule to a session:-

  1. Open the Surveyor Main Menu in TANE (shown below left) or the Surveyor Edit Menu in TRS19 and Trainz Plus (shown below right)
  2. Select the option Edit Session from the drop down menu list
EditSessionMenu.JPG SessionEditMenuSP1.png
  DotPoint2.JPG Add the Trigger Check Rule:
In the Edit Session window (shown below left):-
  • Click the Add button

In the Rule Selection window (shown below right):-

  1. Scroll down the list to select the Trigger Check rule
  2. Click on the Tick.PNG icon
EditSessionWindowX.JPG RuleSelect.JPG

This will add the Trigger Check rule to the session.
  DotPoint3.JPG Open the Trigger Check Rule Properties:
With the Trigger Check rule highlighted (shown below):-
  • Click the Edit button. This will open the rule properties window
TriggerCheck.JPG
  DotPoint4.JPG 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):-

  • Click the Add trigger link
TriggerCheckProperties.JPG
LinkWiki.PNG

More information on the settings and options in this rule can be found on the Trainz Wiki Rules Page at:-
  DotPoint5.JPG Select the Trigger:
The Trigger Selection Window will list all the Track Triggers in your layout.
  1. Select the trigger you have just added
  2. Click on the Tick.PNG icon at the bottom of the selection window
TriggerList.JPG
Once the trigger has been added to the rule, click on the Tick.PNG icon in the Trigger Check properties window to accept the change.
  Top Next Up Next Down Bottom

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.PNG

Steps		 DotPoint1.JPG Add A Message Popup Rule:
When you are back in the Session Editor window:-
  1. Make sure that the new Trigger Check Rule is selected (highlighted)
  2. Click the Add button to add another new rule
  3. Scroll down the rule selection window to find and select the Message Popup rule
  4. Click on the Tick.PNG icon
TriggerAddMesPopup.JPG
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.
  DotPoint2.JPG 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.

SessionRuleIndent.JPG
With the Message Popup Rule highlighted:-

  • Click the Indent (right arrow) button.

This should indent the Message Popup rule one level inwards (as shown below).

SessionRuleIndented.JPG

This 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

Steps.PNG

Steps		 DotPoint1.JPG Open the Message Popup Rule for Editing:
With the Message Popup Rule highlighted and indented (as shown above):-
  • Click the Edit button. The Message Popup Rule properties window will appear (as shown below)
  DotPoint2.JPG Configure the Message:
Set the properties as shown:-
  1. Check ON Close previous message popup windows
  2. Select Option Button Custom text
  3. Enter a short text message (you are limited to about 6 lines of text)
MessagePopupText.JPG
LinkWiki.PNG

More information on this rule can be found on the Trainz Wiki Page at:-
  DotPoint3.JPG (Optional) Add a Message Icon:
  • 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.
  • Click on the Tick.PNG icon
IconStop.JPG
  • click on the Tick.PNG icon to exit the Message Popup Rule and return to the Session Editor

The completed Message Popup Rule
MessagePopupStop.JPG

  DotPoint4.JPG Test the Trigger:
  • Exit the Session Editor
  • Add a consist to your layout a short distance from the track 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 Trainz Wiki Page WikiLink.PNG How to Use Message Popup Rule (Applications).

  Top Next Up   Bottom

Alternatives to the Trigger Check Rule

RulesWiki.PNG 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 WikiLink.PNG 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.


CommandsWiki.png 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

LinkWiki.PNG
  Top Next Up    

Trainz Wiki

TrainzWiki.png

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.

Retrieved from "https://online.ts2009.com/mediaWiki/index.php?title=How_to_Use_Track_Triggers&oldid=29997"
Personal tools