How to Use Track Priority Markers
m (→What are Track Priority Markers?) |
m |
||
(2 intermediate revisions by one user not shown) | |||
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 width=1000> <!-- BEGIN Nav Buttons Table NO SKIPS --> | ||
+ | <tr valign="top"> | ||
+ | <td width=629> </td> | ||
+ | <td width=50> </td> <!-- Skip Down --> | ||
+ | <td width=50> </td> <!-- Skip Up --> | ||
+ | <td width=46> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75>[[image:NextDown.png|link=#stepWhat|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
+ | |||
<table width=1000> | <table width=1000> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 28: | Line 40: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table width=1000> <!-- BEGIN Nav Buttons Table --> | + | <table width=1000> <!-- BEGIN Nav Buttons Table NO SKIPS --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td width= | + | <td width=629><span id="stepWhat"></span> |
+ | ='''What are Track Priority Markers?'''= | ||
+ | </td> | ||
+ | <td width=50> </td> <!-- Skip Down --> | ||
+ | <td width=50> </td> <!-- Skip Up --> | ||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
<td width=75> </td> | <td width=75> </td> | ||
− | <td width=75>[[image:NextDown.png|link=# | + | <td width=75>[[image:NextDown.png|link=#stepRoute|alt=Next Down|Next Down]]</td> |
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
</table> <!-- END Nav Buttons Table --> | </table> <!-- END Nav Buttons Table --> | ||
− | |||
<table width=1000 bgcolor="lightcyan" cellpadding=2> | <table width=1000 bgcolor="lightcyan" cellpadding=2> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td width=10>[[image:BlueDot10x10.png|link=]]</td> | <td width=10>[[image:BlueDot10x10.png|link=]]</td> | ||
− | <td>'''Priority Levels''' have no set meanings but can be assigned to specific AI trains to force them through selected sections of track (the | + | <td>'''Track Priority Markers''' are track markers that are invisible in '''Driver''' but visible in '''Surveyor'''</td> |
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td width=10>[[image:BlueDot10x10.png|link=]]</td> | ||
+ | <td>They match the '''Priority Level''' assigned to AI consists with the level assigned to the marker on the track to decide if the consist is allowed to use that section of track</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td width=10>[[image:BlueDot10x10.png|link=]]</td> | ||
+ | <td>'''Priority Levels''' have no set meanings but can be assigned to specific AI trains to force them through selected sections of track (the sections are defined as the track between consecutive junctions)</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 90: | Line 113: | ||
</table> | </table> | ||
<br> | <br> | ||
− | + | <table width=1000> <!-- BEGIN Nav Buttons Table NO SKIPS --> | |
+ | <tr valign="top"> | ||
+ | <td width=629><span id="stepRoute"></span> | ||
='''Route or Session?'''= | ='''Route or Session?'''= | ||
+ | </td> | ||
+ | <td width=50> </td> <!-- Skip Down --> | ||
+ | <td width=50> </td> <!-- Skip Up --> | ||
+ | <td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
+ | <td width=75>[[image:NextUp.png|link=#stepWhat|alt=Next Up|Next Up]]</td> | ||
+ | <td width=75>[[image:NextDown.png|link=#stepAdding|alt=Next Down|Next Down]]</td> | ||
+ | <td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
<table width=1000 bgcolor="lightcyan" cellpadding=2> | <table width=1000 bgcolor="lightcyan" cellpadding=2> | ||
Line 132: | Line 166: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table width=1000> <!-- BEGIN Nav Buttons Table --> | + | <table width=1000> <!-- BEGIN Nav Buttons Table NO SKIPS --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td width= | + | <td width=629><span id="stepAdding"></span> |
+ | ='''Adding a Track Priority Marker'''= | ||
+ | </td> | ||
+ | <td width=50>[[image:SkipDown.png|link=#skipAddS10|Skip Down]]</td> | ||
+ | <td width=50> </td> <!-- Skip Up --> | ||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
− | <td width=75>[[image:NextUp.png|link=# | + | <td width=75>[[image:NextUp.png|link=#stepRoute|alt=Next Up|Next Up]]</td> |
<td width=75>[[image:NextDown.png|link=#stepAssigning|alt=Next Down|Next Down]]</td> | <td width=75>[[image:NextDown.png|link=#stepAssigning|alt=Next Down|Next Down]]</td> | ||
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
</table> <!-- END Nav Buttons Table --> | </table> <!-- END Nav Buttons Table --> | ||
− | |||
− | |||
<table width=1000 bgcolor=#000000> | <table width=1000 bgcolor=#000000> | ||
Line 177: | Line 213: | ||
</table> | </table> | ||
<br> | <br> | ||
+ | <table width=1000> <!-- BEGIN Nav Buttons Table SKIPS NO SECTIONS --> | ||
+ | <tr valign="top"> | ||
+ | <td width=629><span id="skipAddS10"></span> | ||
=='''In Surveyor Classic (S10)'''== | =='''In Surveyor Classic (S10)'''== | ||
+ | </td> | ||
+ | <td width=50>[[image:SkipDown.png|link=#skipAddS20|Skip Down]]</td> <!-- skip Down --> | ||
+ | <td width=50>[[image:SkipUp.png|link=#stepAdding|Skip Up]]</td> <!-- skip Up --> | ||
+ | <td width=46> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
===Adding a Priority Mark (S10)=== | ===Adding a Priority Mark (S10)=== | ||
Line 377: | Line 425: | ||
</table> | </table> | ||
<br> | <br> | ||
+ | <table width=1000> <!-- BEGIN Nav Buttons Table SKIPS NO SECTIONS --> | ||
+ | <tr valign="top"> | ||
+ | <td width=629><span id="skipAddS20"></span> | ||
=='''In Surveyor 2.0 (S20)'''== | =='''In Surveyor 2.0 (S20)'''== | ||
+ | </td> | ||
+ | <td width=50>[[image:SkipDown.png|link=#stepAssigning|Skip Down]]</td> <!-- skip Down --> | ||
+ | <td width=50>[[image:SkipUp.png|link=#skipAddS10|Skip Up]]</td> <!-- skip Up --> | ||
+ | <td width=46> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
'''Surveyor 2.0''' is currently only available for '''Trainz Plus''' and '''TRS22 Platinum'''.<br> | '''Surveyor 2.0''' is currently only available for '''Trainz Plus''' and '''TRS22 Platinum'''.<br> | ||
Line 1,018: | Line 1,078: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table width=1000> <!-- BEGIN Nav Buttons Table --> | + | <table width=1000> <!-- BEGIN Nav Buttons Table SECTION w SKIPS --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td width= | + | <td width=629><span id="stepAssigning"></span> |
+ | ='''Assigning Priority Levels to Trains'''= | ||
+ | </td> | ||
+ | <td width=50>[[image:SkipDown.png|link=#skipAssignS10|Skip Down]]</td> | ||
+ | <td width=50>[[image:SkipUp.png|link=#skipAddS20|Skip Up]]</td> | ||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
− | <td width=75>[[image:NextUp.png|link=#stepAdding|alt=Next Up| | + | <td width=75>[[image:NextUp.png|link=#stepAdding|alt=Next Up|Next Up]]</td> |
<td width=75>[[image:NextDown.png|link=#stepOperation|alt=Next Down|Next Down]]</td> | <td width=75>[[image:NextDown.png|link=#stepOperation|alt=Next Down|Next Down]]</td> | ||
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
</table> <!-- END Nav Buttons Table --> | </table> <!-- END Nav Buttons Table --> | ||
− | |||
<table width=1000 bgcolor="lightcyan" cellpadding=2> | <table width=1000 bgcolor="lightcyan" cellpadding=2> | ||
Line 1,064: | Line 1,127: | ||
</table> | </table> | ||
<br> | <br> | ||
− | ==''' | + | <table width=1000> <!-- BEGIN Nav Buttons Table SKIPS NO SECTIONS --> |
+ | <tr valign="top"> | ||
+ | <td width=629><span id="skipAssignS10"></span> | ||
+ | =='''Surveyor Classic (S10)'''== | ||
+ | </td> | ||
+ | <td width=50>[[image:SkipDown.png|link=#skipAssignS20|Skip Down]]</td> <!-- skip Down --> | ||
+ | <td width=50>[[image:SkipUp.png|link=#stepAssigning|Skip Up]]</td> <!-- skip Up --> | ||
+ | <td width=46> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
To assign a priority level to a consist.<br> | To assign a priority level to a consist.<br> | ||
Line 1,128: | Line 1,203: | ||
[[image:PriorityTrain.png|link=]]<br> | [[image:PriorityTrain.png|link=]]<br> | ||
<br> | <br> | ||
− | ==''' | + | <table width=1000> <!-- BEGIN Nav Buttons Table SKIPS NO SECTIONS --> |
+ | <tr valign="top"> | ||
+ | <td width=629><span id="skipAssignS20"></span> | ||
+ | =='''Surveyor 2.0 (S20)'''== | ||
+ | </td> | ||
+ | <td width=50>[[image:SkipDown.png|link=#stepOperation|Skip Down]]</td> <!-- skip Down --> | ||
+ | <td width=50>[[image:SkipUp.png|link=#skipAssignS10|Skip Up]]</td> <!-- skip Up --> | ||
+ | <td width=46> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | <td width=75> </td> | ||
+ | </tr> | ||
+ | </table> <!-- END Nav Buttons Table --> | ||
'''Surveyor 2.0''' is currently only available for '''Trainz Plus''' and '''TRS22 Platinum'''.<br> | '''Surveyor 2.0''' is currently only available for '''Trainz Plus''' and '''TRS22 Platinum'''.<br> | ||
− | To assign a priority level to a | + | To assign a priority level to a consist.<br> |
<table width=1000> | <table width=1000> | ||
Line 1,195: | Line 1,282: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table width=1000> <!-- BEGIN Nav Buttons Table --> | + | <table width=1000> <!-- BEGIN Nav Buttons Table SECTION w SKIPS --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td width= | + | <td width=629><span id="stepOperation"></span> |
+ | ='''Priority Marker Operation'''= | ||
+ | </td> | ||
+ | <td width=50> </td> | ||
+ | <td width=50>[[image:SkipUp.png|link=#skipAssignS20|Skip Up]]</td> | ||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
− | <td width=75>[[image:NextUp.png|link=#stepAssigning|alt=Next Up| | + | <td width=75>[[image:NextUp.png|link=#stepAssigning|alt=Next Up|Next Up]]</td> |
<td width=75>[[image:NextDown.png|link=#stepModifying|alt=Next Down|Next Down]]</td> | <td width=75>[[image:NextDown.png|link=#stepModifying|alt=Next Down|Next Down]]</td> | ||
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
</table> <!-- END Nav Buttons Table --> | </table> <!-- END Nav Buttons Table --> | ||
− | |||
− | |||
<table width=1000 bgcolor="lightcyan" cellpadding=2> | <table width=1000 bgcolor="lightcyan" cellpadding=2> | ||
Line 1,315: | Line 1,404: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table width=1000> <!-- BEGIN Nav Buttons Table --> | + | <table width=1000> <!-- BEGIN Nav Buttons Table NO SKIPS --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td width= | + | <td width=629><span id="stepModifying"></span> |
+ | ='''Modifying Train Priority Levels'''= | ||
+ | </td> | ||
+ | <td width=50> </td> <!-- Skip Down --> | ||
+ | <td width=50> </td> <!-- Skip Up --> | ||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
− | <td width=75>[[image:NextUp.png|link=#stepOperation|alt=Next Up| | + | <td width=75>[[image:NextUp.png|link=#stepOperation|alt=Next Up|Next Up]]</td> |
<td width=75>[[image:NextDown.png|link=#stepMap|alt=Next Down|Next Down]]</td> | <td width=75>[[image:NextDown.png|link=#stepMap|alt=Next Down|Next Down]]</td> | ||
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
Line 1,325: | Line 1,418: | ||
</table> <!-- END Nav Buttons Table --> | </table> <!-- END Nav Buttons Table --> | ||
<br> | <br> | ||
− | |||
− | |||
<table width=1000 bgcolor="lightcyan" cellpadding=2> | <table width=1000 bgcolor="lightcyan" cellpadding=2> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 1,455: | Line 1,546: | ||
</table> | </table> | ||
<br> | <br> | ||
− | <table width=1000> <!-- BEGIN Nav Buttons Table --> | + | <table width=1000> <!-- BEGIN Nav Buttons Table NO SKIPS --> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td width= | + | <td width=629><span id="stepMap"></span> |
+ | ='''Track Priority in Map View'''= | ||
+ | </td> | ||
+ | <td width=50> </td> <!-- Skip Down --> | ||
+ | <td width=50> </td> <!-- Skip Up --> | ||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
− | <td width=75>[[image:NextUp.png|link=#stepModifying|alt=Next Up| | + | <td width=75>[[image:NextUp.png|link=#stepModifying|alt=Next Up|Next Up]]</td> |
− | <td width=75>& | + | <td width=75> </td> |
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
</table> <!-- END Nav Buttons Table --> | </table> <!-- END Nav Buttons Table --> | ||
− | |||
<table width=1000> | <table width=1000> | ||
Line 1,474: | Line 1,568: | ||
Tracks that have not been given a priority marker will be shown as dark blue indicating that they have the '''default priority level 2'''.</td> | Tracks that have not been given a priority marker will be shown as dark blue indicating that they have the '''default priority level 2'''.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
Line 1,492: | Line 1,573: | ||
<table width=1000> <!-- BEGIN Nav Buttons Table --> | <table width=1000> <!-- BEGIN Nav Buttons Table --> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td width=729><span id="bottom"></span>& | + | <td width=729><span id="bottom"></span> </td> |
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | <td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | ||
<td width=75>[[image:NextUp.png|link=#stepMap|alt=Next Up|Top]]</td> | <td width=75>[[image:NextUp.png|link=#stepMap|alt=Next Up|Top]]</td> | ||
− | <td width=75>& | + | <td width=75> </td> |
− | <td width=75>& | + | <td width=75> </td> |
</tr> | </tr> | ||
</table> <!-- END Nav Buttons Table --> | </table> <!-- END Nav Buttons Table --> | ||
---- | ---- | ||
---- | ---- | ||
− | |||
='''Trainz Wiki'''= | ='''Trainz Wiki'''= | ||
− | <table | + | <table width=1000> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[image:TrainzWiki.png|link=]]</td> | + | <td> |
+ | <table width=500 cellpadding=2 bgcolor=#ffffff> | ||
+ | <tr valign="top"> | ||
+ | <td width=80>[[image:TrainzWiki.png|link=]]</td> | ||
<td> | <td> | ||
<span style="font-size: 17px;">'''More Tutorials and Guides to Using Trainz'''</span><br> | <span style="font-size: 17px;">'''More Tutorials and Guides to Using Trainz'''</span><br> | ||
Line 1,512: | Line 1,595: | ||
*'''[[Session Rule List with Parameters|Session Rules List (Alphabetical) with Parameters]]''' | *'''[[Session Rule List with Parameters|Session Rules List (Alphabetical) with Parameters]]''' | ||
*'''[[Session Rules By Categories With Properties|Session Rules List (Categories) With Parameters]]''' | *'''[[Session Rules By Categories With Properties|Session Rules List (Categories) With Parameters]]''' | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | <td> | ||
+ | <table width=500 cellpadding=4 bgcolor="aquamarine"> | ||
+ | <tr valign="top"> | ||
+ | <td width=50>[[image:LinkWiki.PNG|link=]]</td> | ||
+ | <td> | ||
+ | <span style="font-size: 17px;">'''Related Links'''</span><br> | ||
+ | * '''[[How to Use Track Direction Markers]]''' | ||
+ | * '''[[How to Use Track Markers]]''' | ||
+ | * '''[[How to Use Track Triggers]]''' | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
</td> | </td> | ||
</tr> | </tr> |
Latest revision as of 20:44, 28 November 2023
The information in this Wiki Page applies to TANE, TRS19, Trainz Plus and TRS22.
[edit] What are Track Priority Markers? |
Track Priority Markers are track markers that are invisible in Driver but visible in Surveyor | |
They match the Priority Level assigned to AI consists with the level assigned to the marker on the track to decide if the consist is allowed to use that section of track | |
Priority Levels have no set meanings but can be assigned to specific AI trains to force them through selected sections of track (the sections are defined as the track between consecutive junctions) |
|
[edit] Route or Session? |
Priority Marks can be placed in a Route Layer or in a Session Layer |
|
Information on Route and Session layers can be found at:- |
[edit] Adding a Track Priority Marker |
|
[edit] In Surveyor Classic (S10) |
[edit] Adding a Priority Mark (S10)
|
Immediately after the Priority Mark has been placed its properties window will appear. You can:-
|
[edit] Set the Priority Mark Effect Radius (S10)
At the bottom of the Track Tools flyout menu is an Advanced button. Left Click this button to open the advanced tools.
The Effect Radius sets the size of green "effect wings" attached both ends of the marker. It has no effect on its operation but allows you to keep its "visibility" clear of other track objects such as junctions and other markers. |
|
|
[edit] In Surveyor 2.0 (S20) |
Surveyor 2.0 is currently only available for Trainz Plus and TRS22 Platinum.
[edit] Adding a Priority Mark (S20)
In the Asset Palette either:-
|
OR |
|
|
|
To narrow down the filter list, type "mark" (UPPER/lower case does not matter) in the Search Text Box
This will list all the Track Objects containing the text "mark" in the filter list.
|
Place the Priority Mark on the track.
|
|
|
[edit] Set its Priority Level (S20)
The Priority Level is the ONLY important property of a Priority Mark. Its possible values are 1, 2 and 3. |
|
[edit] Change Its Name (S20)
The name of the marker is only useful for finding it in the route. It is not used for any operational purpose.
|
[edit] Set its Effect Radius (S20)
The Effect Radius sets the size of green "effect wings" attached both ends of the marker. It has no effect on its operation but allows you to keep its "visibility" clear of other track objects such as junctions and other markers. |
|
[edit] Move a Priority Mark Along the Track (S20)
Priority Marks can be moved along the track or to other tracks.
|
[edit] Move the Priority Mark Vertically (S20)
Priority Marks can be physically placed above (or below) the track. This feature allows them to be placed, for example, above the track so that they will not be hidden in Surveyor if a consist is parked on a marker. |
|
[edit] Move the Priority Mark Horizontally (S20)
Priority Marks can be physically placed left or right alongside the track. This feature allows them to be placed, for example, beside the track so that they will not be hidden in Surveyor if a consist is parked on a marker. |
|
|
[edit] Assign a Priority Marker to a New Layer (S20)
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. | |||||||||||||||||||||||
|
[edit] Assigning Priority Levels to Trains |
A higher priority level does not mean that one consist is more important than another. A priority 1 consist will not be given first access to a junction, for example, or be the first one to depart. The priority levels have no set meaning beyond what you decide they will mean. |
|
For example you could assign priority 1 to express trains and 3 to slow general "all stops" freight trains, or you could assign priority 3 to express trains and 1 to slow general "all stops" freight trains, it is up to you. These values will not alter the speed or importance of these trains but will only decide which paths they should take. |
[edit] Surveyor Classic (S10) |
To assign a priority level to a consist.
|
[edit] Surveyor 2.0 (S20) |
Surveyor 2.0 is currently only available for Trainz Plus and TRS22 Platinum.
To assign a priority level to a consist.
|
[edit] Priority Marker Operation |
Priority Marks only work on AI controlled trains. They have no effect on manually controlled trains | |
Priority Marks force a AI trains that with the same priority level into taking the path containing the marker | |
AI trains will ignore a path containing a Priority Mark that does not match its own priority level unless that path is also the shortest available | |
If the specified path is blocked, then the AI will ignore the Priority Mark and find another path | |
The direction that the Priority Mark is pointing has NO effect on its operation |
Consider the situations represented in the diagrams below. Three trains - Red, Green, Yellow - have been given priority levels of 1, 2 and 3 as shown. Each is given the driver command Drive to Trackmark or Navigate to Trackmark. The destination trackmark is shown on the right. In Figure 1 below, no Track Priority Markers have been set. All three trains will take the shortest path, assuming there are no blockages.
In Figure 2 below, a Track Priority Marker has been placed on the top loop line and has been given a priority level of 1. The red train (priority level 1) will now take the priority 1 path because it will "see" that as being the shortest of the three possible paths. The green and yellow trains (priority levels 2 and 3) will still "see" the middle path as the shortest.
In Figure 3 below, a Track Priority Marker has been placed on the lower loop line and has been given a priority level of 3. For the same reasons as explained above, the yellow train (priority level 3) will now take the priority 3 path because it now sees that as the shortest.
In Figure 4 below, Track Priority Markers have been placed on the upper and lower loop lines and set as shown. The red and yellow trains will take their respective loop paths while the green train is unaffected.
An exception, shown in Figure 5 below, will occur when a Track Priority Marker path has been blocked, for example by another train under AI or manual control. In the figure the lower loop path has been blocked. The red train will take its assigned path, the green train takes its shortest path and yellow train will be forced to take what it "sees" as the next shortest path.
|
|
Another exception, shown in Figure 6 below, will occur when a driver command overrides a Track Priority Marker. In the figure the yellow train (priority level 3) has been given the driver command Drive To Station followed by Drive to Trackmark. As the station is not on the priority 3 path, that path will be ignored to reach the station and then the trackmark. After stopping at the station the train will not reverse back onto the main line to then use the priority 3 track.
The Special Case of Priority 2 Track Priority Markers can also be used to direct trains away from specific paths. Figure 8 below shows how this can be done. A Track Priority Marker set to priority level 1 has been positioned on the shortest physical path. This will block all trains of priority level 2 and 3 from using that path - they will see it as the longest available path. A second Track Priority Marker set to priority level 3 has been positioned on the 2nd shortest physical path. This will block all trains of priority level 1 and 2 from using that path. The end result is that the green train (priority level 2) has only one path available - the longest physical path.
The situation shown in Figure 8 above only works up to a point. Figure 9 below shows what will happen when ALL paths are set to a blocking priority level. The green train (priority level 2) will ignore all the priority markers and choose its own shortest path. Track Priority Markers will only make a path *look* longer or shorter. When all paths have conflicting priorities to an AI train, then the AI will go back to selecting the actual shortest physical path.
|
[edit] Modifying Train Priority Levels |
The Priority Level of a consist in Driver can be altered manually or automatically |
Manually in Driver
This can be done "on the fly" using the mouse.
|
OR
Using the Session Editor
This can be done in Surveyor in the Session Editor Driver Setup Rule
|
Information on adding driver commands can be found on the Trainz Wiki Page at:- |
[edit] Track Priority in Map View |
In Surveyor when using Map View or zooming the camera right out, the tracks will be shown colour coded according to their assigned track priority level. If the track layout shown in Figure 4 above, with the priority markers as used in that figure, was shown in Map View then this would be the result.
|
[edit] Trainz Wiki
|
|
This page was created by Trainz user pware in September 2019 and was last updated as shown below.