How to Use Track Priority Markers
m |
m |
||
Line 243: | Line 243: | ||
<span style="text-decoration: underline; font-weight: 700;">Figure 4</span><br> | <span style="text-decoration: underline; font-weight: 700;">Figure 4</span><br> | ||
---- | ---- | ||
− | In '''Figure 5''' below, two Track Priority Markers have been placed on the lower loop line and set as shown. The yellow train will take the lower loop (its "shortest path"), | + | In '''Figure 5''' below, two Track Priority Markers have been placed on the lower loop line and set as shown. The yellow train will take the lower loop (its "shortest path"), the red train still takes the actual shortest path but the green train is completely ignoring its set Track Priority Marker. Why?<br> |
− | + | ||
− | + | ||
[[file:PriorityMap_P23a.png|link=|alt=Priority Map - Priority 2&3a]]<br> | [[file:PriorityMap_P23a.png|link=|alt=Priority Map - Priority 2&3a]]<br> | ||
<span style="text-decoration: underline; font-weight: 700;">Figure 5</span><br> | <span style="text-decoration: underline; font-weight: 700;">Figure 5</span><br> | ||
+ | |||
+ | A priority level of <span style="text-decoration: underline; font-weight: 700;">2</span> is automatically assigned to any track that does not have a Track Priority Marker. Because it is not an actual Priority Level Marker this will have no effect on trains with priority levels of <span style="text-decoration: underline; font-weight: 700;">1</span> and <span style="text-decoration: underline; font-weight: 700;">3</span> but it does give trains with a priority level of <span style="text-decoration: underline; font-weight: 700;">2</span> an unexpected bonus. The green train has actually been given a choice between '''two''' priority level <span style="text-decoration: underline; font-weight: 700;">2</span> paths, one with a Priority Level Marker and one without. It has, naturally, taken the shortest of the two paths.<br> | ||
<table bgcolor=#000000 width=900 cellpadding=2> | <table bgcolor=#000000 width=900 cellpadding=2> | ||
Line 257: | Line 257: | ||
<td>[[image:PencilTips.PNG|link=]]</td> | <td>[[image:PencilTips.PNG|link=]]</td> | ||
<td><span style="font-weight: 700; font-size: 15px;">How Do You Fix This?</span><br> | <td><span style="font-weight: 700; font-size: 15px;">How Do You Fix This?</span><br> | ||
− | In '''Figure 6''' below, the middle and shortest path has been given a priority level of <span style="text-decoration: underline; font-weight: 700;">1</span> which forces the green train to avoid it. It now takes the next shortest and correct path. The yellow train still takes the lower loop. The red train | + | In '''Figure 6''' below, the middle and shortest path has been given a priority level of <span style="text-decoration: underline; font-weight: 700;">1</span> which forces the green train to avoid it. It now takes the next shortest and correct path. The yellow train still takes the lower loop. The red train now has a choice between two priority level <span style="text-decoration: underline; font-weight: 700;">1</span> paths and takes the shorter one of the two.<br> |
[[file:PriorityMap_P23b.png|link=|alt=Priority Map - Priority 2&3b]]<br> | [[file:PriorityMap_P23b.png|link=|alt=Priority Map - Priority 2&3b]]<br> | ||
Line 268: | Line 268: | ||
</table> | </table> | ||
---- | ---- | ||
− | An exception, shown in '''Figure 7''' below, will occur when one or more of the Track Priority Marker paths have been blocked, for example by a consist under AI or manual control. In the figure the lower loop path has been blocked. The red train will take its assigned path | + | An exception, shown in '''Figure 7''' below, will occur when one or more of the Track Priority Marker paths have been blocked, for example by a consist 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 will takes it shortest path and yellow train will be forced to take the next shortest path.<br> |
[[file:PriorityMap_P123Blocked.png|link=|alt=Priority Map - Priority 2&3 blocked]]<br> | [[file:PriorityMap_P123Blocked.png|link=|alt=Priority Map - Priority 2&3 blocked]]<br> | ||
Line 293: | Line 293: | ||
<br> | <br> | ||
---- | ---- | ||
− | Another exception, shown in '''Figure | + | Another exception, shown in '''Figure 8''' below, will occur when a driver command overrides a Track Priority Marker. In the figure the yellow train, with priority 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.<br> |
[[file:PriorityMap_P3Station.png|link=|alt=Priority Map - Station]]<br> | [[file:PriorityMap_P3Station.png|link=|alt=Priority Map - Station]]<br> | ||
− | <span style="text-decoration: underline; font-weight: 700;">Figure | + | <span style="text-decoration: underline; font-weight: 700;">Figure 8</span><br> |
---- | ---- | ||
<br> | <br> |
Revision as of 21:04, 29 September 2022
The information in this Wiki Page applies to TANE, TRS19, Trainz Plus and TRS22.
Contents |
What are Track Priority Markers?
In Summary: | |
Track Priority Markers are purple coloured track markers that are invisible in Driver Mode but visible in Surveyor Mode. They are used to direct specific trains under AI control through the track section where they are placed | |
Track Priority Markers only work on AI controlled trains. They have no effect on manually controlled trains | |
The direction that the marker is pointing has absolutely NO EFFECT on its operation | |
Track Priority Markers must be used with Priority Levels that are assigned to each train | |
Track Priority Markers are NOT a substitute for Driver Commands or Interlocking Towers |
|
Adding a Track Priority Marker
|
|
Priority levels have no set meanings but can be assigned to specific AI trains to force them through selected sections of track (the track sections are defined as between consecutive junction sets) |
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.
|
|
Steps:
|
|
|
Priority Marker Operation
Main Points: | |
Track Priority Markers only work on AI controlled trains. They have no effect on manually controlled trains | |
Track Priority Markers fool an AI train that has the same priority level into thinking that the path containing the marker is the shortest possible path, even when it is not | |
If the priority level of the AI train does not match the priority level of the Track Priority Marker, then the AI will ignore the marker and select its own path which may be the same path that contains the priority marker | |
If the specified path is blocked, then the AI will ignore the Track Priority Marker and find another path | |
The direction that the Track Priority Marker is pointing has NO effect on its operation |
Consider the situation 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.
Figure 1
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 will now take the Priority 1 path because it will "see" that path as being the shortest of the three possible paths. The green and yellow trains, with their priority levels of 2 and 3, will not be affected as they still "see" the middle path as the shortest.
Figure 2
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, the yellow train will now take the priority 3 path because it now sees that as the shortest path while the red and green trains are unaffected.
Figure 3
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.
Figure 4
In Figure 5 below, two Track Priority Markers have been placed on the lower loop line and set as shown. The yellow train will take the lower loop (its "shortest path"), the red train still takes the actual shortest path but the green train is completely ignoring its set Track Priority Marker. Why?
Figure 5
A priority level of 2 is automatically assigned to any track that does not have a Track Priority Marker. Because it is not an actual Priority Level Marker this will have no effect on trains with priority levels of 1 and 3 but it does give trains with a priority level of 2 an unexpected bonus. The green train has actually been given a choice between two priority level 2 paths, one with a Priority Level Marker and one without. It has, naturally, taken the shortest of the two paths.
|
An exception, shown in Figure 7 below, will occur when one or more of the Track Priority Marker paths have been blocked, for example by a consist 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 will takes it shortest path and yellow train will be forced to take the next shortest path.
Figure 7
|
Another exception, shown in Figure 8 below, will occur when a driver command overrides a Track Priority Marker. In the figure the yellow train, with priority 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.
Figure 8
Modifying Train Priority Levels
You can alter the Priority Level of a train in Driver mode |
Manually in Driver Mode
This can be done "on the fly" using the mouse.
|
Using a Driver Command
This can be done in Surveyor in the session Driver Setup Rule or by adding a driver command to the command bar in Driver.
- Insert the driver command Priorityz into the driver command bar and set it to the new level
Information on adding driver commands can be found on the Trainz Wiki Page at:- |
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.
Tracks that have not been given a priority marker will be shown as dark blue indicating that they have the default priority level 2.
Related Links
Trainz Wiki
More Tutorials and Guides to Using Trainz |
This page was created by Trainz user pware in September 2019 and was last updated as shown below.