How to Use Layers

From TrainzOnline
(Difference between revisions)
Jump to: navigation, search
m (The Route Layers Group: cleaned up and simplified point on rulers)
m
 
(70 intermediate revisions by one user not shown)
Line 1: Line 1:
The information in this Wiki Page applies to '''TANE''', '''TRS19''' and '''Trainz Plus'''.
+
The information in this Wiki Page applies to '''TANE''', '''TRS19''', '''Trainz Plus''' and '''TRS22'''.
 
+
 
__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=#stepTool|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 Layers?'''=
 
='''What Are Layers?'''=
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
Line 18: Line 27:
  
 
Layers can contain any objects, visible and invisible, that can be placed into a layout using the Surveyor '''Object''', '''Track''' and '''Train''' tools. The layers and their contents can be hidden from view or locked against alteration whenever required. Their main use is in the development of a Route and a Session but they can also be used as a way of providing some additional novelty during a Driver session.
 
Layers can contain any objects, visible and invisible, that can be placed into a layout using the Surveyor '''Object''', '''Track''' and '''Train''' tools. The layers and their contents can be hidden from view or locked against alteration whenever required. Their main use is in the development of a Route and a Session but they can also be used as a way of providing some additional novelty during a Driver session.
<table width="100%">
+
 
<br>
+
<table bgcolor=#ffffb0 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
<td align="right">[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
+
<td>[[image:NotePad.PNG|link=]]</td>
 +
<td><span style="font-size: 17px; font-weight: 700;">Effect Layers Notes:'''</span><br>
 +
----
 +
The special ground effects layers, '''Clutter''' and '''TurfFX''', that are available in the <span style="font-weight: 700;">Topology Tools</span> (press the <span style="font-weight: 700; color: white; background-color: black;">&nbsp;F1&nbsp;</span> key) are not discussed here. They are more like '''Textures''' than '''Layers''' but some aspects of their use and operations are similar to the layers covered here. These special ground effects layers are saved as part of a '''Route''' but are not associated with any '''Route Layer'''.
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
 +
<table> <!-- BEGIN Nav Buttons Table -->
 +
<tr valign="top">
 +
<td width=729><span id="stepTool"></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=#stepRouteSession|alt=Next Down|Next Down]]</td>
 +
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td>
 +
</tr>
 +
</table> <!-- END Nav Buttons Table -->
  
 
='''The Layers Tool'''=
 
='''The Layers Tool'''=
Line 33: Line 56:
 
<td>Click the '''Layers Tool''' to open up its properties.<br>
 
<td>Click the '''Layers Tool''' to open up its properties.<br>
 
[[file:LayersTools.JPG|480px]]</td>
 
[[file:LayersTools.JPG|480px]]</td>
<td><br><br>
+
<td>
<table cellpadding="4" bgcolor=#ffffb0>
+
<br>
 +
 
 +
<table bgcolor=#000000 cellpadding=2>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffb0 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 +
----
 
The layers are organised into two groups:-
 
The layers are organised into two groups:-
 
*'''Route Layers''' in the top group, and  
 
*'''Route Layers''' in the top group, and  
Line 43: Line 72:
 
Each group can contain multiple layers - the scroll bars next to the layer names shown on the left indicate that there are more layers in each group than can fit into the display window area.</td>
 
Each group can contain multiple layers - the scroll bars next to the layer names shown on the left indicate that there are more layers in each group than can fit into the display window area.</td>
 
</tr>
 
</tr>
</table></td>
+
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 49: Line 82:
  
 
==Loading a Route and Loading a Session==
 
==Loading a Route and Loading a Session==
<table cellpadding="4" bgcolor=#c1e7e7 width="730"> <!-- BEGIN top level -->
+
<table cellpadding=4 bgcolor=#c1e7e7 width="730"> <!-- BEGIN top level -->
 
<tr valign="top">
 
<tr valign="top">
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
Line 62: Line 95:
 
</tr>
 
</tr>
 
</table> <!-- END top level -->
 
</table> <!-- END top level -->
 
+
<br>
The layers you see will depend on whether you have loaded a '''Route''' by itself (with no "child" Session) or a '''Session''' and its "parent" Route.
+
<table cellpadding=4 bgcolor="Aquamarine"> <!-- BEGIN Trainz Wiki Link -->
<table cellpadding="4" bgcolor=#ffffb0> <!-- BEGIN top level -->
+
 
<tr valign="top">
 
<tr valign="top">
<td>[[file:PencilTips.PNG|link=]]</td>
+
<td>[[image:LinkWiki.PNG|link=]]</td>
<td>Until you gain experience and confidence in working with '''Routes''' and '''Sessions''', and their layers, the best advice is to <span style="font-size: 17px; font-weight: 700;">always load and edit a Session, not a Route.</span></td>
+
<td>
 +
More information on creating, loading and saving '''Routes''' and '''Sessions''' can be found on the '''Trainz Wiki Page''' at '''[[Route_and_Session_Basics|Route and Session Basics]]'''
 +
</td>
 
</tr>
 
</tr>
</table> <!-- END top level -->
+
</table> <!-- END Trainz Wiki Link -->
 +
<br>
 +
The layers you see will depend on whether you have loaded a '''Route''' by itself (with no "child" Session) or a '''Session''' and its "parent" Route.
  
 
<table> <!-- BEGIN top level -->
 
<table> <!-- BEGIN top level -->
Line 75: Line 111:
 
<td>[[file:LayersToolsRoute.JPG|link=]]</td>
 
<td>[[file:LayersToolsRoute.JPG|link=]]</td>
 
<td>[[file:LayersToolsSession.JPG|link=]]</td>
 
<td>[[file:LayersToolsSession.JPG|link=]]</td>
<td><br>
+
<td>The first image on the left gives an example of the layers that can appear if a '''Route only''' is loaded into Surveyor. These are the layers that are saved with the Route. '''Note that a default "session-layer" is present'''.  
*The first image on the left gives an example of the layers that can appear if a '''Route only''' is loaded into Surveyor. These are the layers that are saved with the Route. '''Note that a default "session-layer" is present'''.  
+
<table cellpadding=4 bgcolor=#c1e7e7> <!-- BEGIN 2nd level -->
<table cellpadding="4" bgcolor=#c1e7e7> <!-- BEGIN 2nd level -->
+
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 88: Line 123:
 
</tr>
 
</tr>
 
</table> <!-- END 2nd level -->
 
</table> <!-- END 2nd level -->
*The second image on the left gives an example of the layers that can appear if a '''Session based on that Route''' is loaded into Surveyor. It shows Route Layers and Session Layers.<br><br>
+
The second image on the left gives an example of the layers that can appear if a '''Session based on that Route''' is loaded into Surveyor. It shows Route Layers and Session Layers.<br><br>
  
 
In both cases, the '''Route Layers''' are identical because the same Route has been loaded. A Session contains its own layers, the '''Session Layers''', that are loaded and saved with the Session but are not loaded or saved with the Route.<br>
 
In both cases, the '''Route Layers''' are identical because the same Route has been loaded. A Session contains its own layers, the '''Session Layers''', that are loaded and saved with the Session but are not loaded or saved with the Route.<br>
<table cellpadding="4" bgcolor=#ffffb0> <!-- BEGIN 2nd level -->
+
 
 +
<table bgcolor=#000000> <!-- BEGIN 2nd level Black Border -->
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0> <!-- BEGIN 2nd level Tip -->
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
Line 98: Line 137:
 
<tr>
 
<tr>
 
<td>[[file:LayersToolButtonsLOCKALL.JPG|link=]]</td>
 
<td>[[file:LayersToolButtonsLOCKALL.JPG|link=]]</td>
<td>Click the '''Lock Button'''</td>
+
<td>Click the '''Lock Button'''
 +
</td>
 
</tr>
 
</tr>
 
</table> <!-- END 3rd level -->
 
</table> <!-- END 3rd level -->
 
</td>
 
</td>
 
</tr>
 
</tr>
</table> <!-- END 2nd level -->
+
</table> <!-- END 2nd level Tip-->
 +
</td>
 +
</tr>
 +
</table>
 +
<br> <!-- END 2nd level Black Border -->
 
</td>
 
</td>
 
</tr>
 
</tr>
 
</table> <!-- END top level -->
 
</table> <!-- END top level -->
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#fcbcbc> <!-- BEGIN top level -->
+
<table bgcolor="red" cellpadding=2>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#fcbcbc cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:Stop.PNG|link=]]</td>
 
<td>[[file:Stop.PNG|link=]]</td>
<td><span style="font-size: 17px;"><b>WARNING:</b></span></td>
+
<td><span style="font-size: 17px; font-weight: 700;">If you load a <span style="text-decoration: underline;">ROUTE</span> but not the SESSION then only <span style="text-decoration: underline;">edit the Route Layers</span></span></td>
 
</tr>
 
</tr>
 
<tr valign="top">
 
<tr valign="top">
<td>[[file:DotPoint.JPG|link=]]</td>
+
<td>[[file:Stop.PNG|link=]]</td>
<td><span style="font-size: 17px;">'''If you load a <span style="text-decoration: underline;">ROUTE</span> without a SESSION then only <span style="text-decoration: underline;">edit the Route Layers</span>'''</span></td>
+
<td><span style="font-size: 17px;">'''If you edit a <span style="text-decoration: underline;">SESSION</span> or its layers then always <span style="text-decoration: underline;">save the Session</span>'''</span></td>
 
</tr>
 
</tr>
 
<tr valign="top">
 
<tr valign="top">
<td>[[file:DotPoint.JPG|link=]]</td>
+
<td>[[file:Stop.PNG|link=]]</td>
<td><span style="font-size: 17px;">'''If you load a <span style="text-decoration: underline;">SESSION</span> and edit any Session layers then <span style="text-decoration: underline;">save the Session</span>'''</span></td>
+
<td><span style="font-size: 17px;">'''When you save a new <span style="text-decoration: underline;">SESSION</span> always give it a name, do <span style="text-decoration: underline;">NOT</span> leave it as "Default"</span>
 +
</td>
 
</tr>
 
</tr>
<tr valign="top">
+
</table>
<td>[[file:DotPoint.JPG|link=]]</td>
+
</td>
<td><span style="font-size: 17px;">'''When you save a <span style="text-decoration: underline;">SESSION</span>, give it a distinctive descriptive name (do <span style="text-decoration: underline;">NOT</span> use Default)'''</span></td>
+
 
</tr>
 
</tr>
 
</table>
 
</table>
<!-- END top level -->
 
  
 
==Creating a New Route==
 
==Creating a New Route==
Line 134: Line 180:
 
<td>[[file:LayersNewRoute.JPG|link=]]</td>
 
<td>[[file:LayersNewRoute.JPG|link=]]</td>
 
<td>
 
<td>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table>
 +
<tr valign="top">
 +
<td>[[file:LayersNewRoute.JPG|link=]]</td>
 +
<td>
 +
<table bgcolor=#000000 width=604>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffb0 width=600>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
*When a brand new route is created it will come with two layers, a single "route-layer" and a single "session-layer".
+
----
 +
*When a brand new route is created it will come with two layers, a single '''route-layer''' and a single '''session-layer'''.
 
*Both layers will be empty (the baseboard with its grid is saved with the route but is not in any layer).
 
*Both layers will be empty (the baseboard with its grid is saved with the route but is not in any layer).
 
</td>
 
</td>
 
</tr>
 
</tr>
</table>
+
<tr valign="top">
<table cellpadding="4" bgcolor=#ffffb0>
+
<td colspan=2>
 +
<table width=600 bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
<td>'''A layer can be renamed at anytime by double clicking on its name with the left mouse button and typing a new name.'''</td>
+
<td>'''A layer can be renamed at anytime by double clicking on its name with the left mouse button and typing a new name'''
 +
</td>
 
</tr>
 
</tr>
</table></td>
+
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
  
 
==The "Active Layer"==
 
==The "Active Layer"==
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
Line 172: Line 238:
 
In the image above, the '''route-layer''' is the '''Active Layer'''. You can change the '''Active Layer''' at any time by clicking on the name of another layer.
 
In the image above, the '''route-layer''' is the '''Active Layer'''. You can change the '''Active Layer''' at any time by clicking on the name of another layer.
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#ffffb0 width="480">
+
 
 +
<table width=900>
 +
<tr valign="top">
 +
<td width=484>
 +
<table bgcolor=#000000 width=464>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffb0 width=460>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 +
----
 
The '''Active Layer''' is the "working layer" which is:-
 
The '''Active Layer''' is the "working layer" which is:-
 
*where new objects will be added to the layout
 
*where new objects will be added to the layout
*the layer that is automatically selected for merging and deleting</td>
+
*the layer that is automatically selected for merging and deleting
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
<table cellpadding="4" bgcolor=#fcbcbc width="480">
+
</td>
<tr valign="top">
+
<td colspan=2><span style="font-size: 17px;"><b>Caution:</b></span></td>
+
 
</tr>
 
</tr>
 +
</table>
 +
</td>
 +
<td width=12>&nbsp;</td>
 +
<td width=484>
 +
<table bgcolor="red" width=464>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#fcbcbc width=460>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:Stop.PNG|link=]]</td>
 
<td>[[file:Stop.PNG|link=]]</td>
<td>'''Trainz''' does not identify which is the '''Active Layer''' in Surveyor and this often leads to problems such as objects being added to the wrong layer.<br>
+
<td>'''Trainz''' does not identify which is the '''Active Layer''' in '''Surveyor''' and this often leads to problems such as objects being added to the wrong layer.<br>
See [[file:PageLink.PNG|link=]] '''[[#Adding Objects To Layers|Adding Objects To Layers]]''' below for more information.</td>
+
See [[file:PageLink.PNG|link=]] '''[[#Adding Objects To Layers|Adding Objects To Layers]]''' below for more information.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 207: Line 295:
 
<td>[[file:LayersAddLayer.JPG|link=]]</td>
 
<td>[[file:LayersAddLayer.JPG|link=]]</td>
 
<td>
 
<td>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr>
 
<tr>
 
<td colspan="2">
 
<td colspan="2">
Line 224: Line 312:
 
</tr>
 
</tr>
 
</table>
 
</table>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
<td>You can easily rename the layer or move it to the other layer group later if you change your mind.</td>
+
<td>You can easily rename the layer or move it to the other layer group if you change your mind.</td>
 
</tr>
 
</tr>
</table></td>
+
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 235: Line 330:
 
==Deleting a Layer==
 
==Deleting a Layer==
  
 +
<table bgcolor="red" width=300>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#fcbcbc width=296>
 +
<tr valign="top">
 +
<td>[[file:Stop.PNG|link=]]</td>
 +
<td><span style="font-size: 15px; font-weight: 700;">WARNING:</span><br>
 +
'''Deleting Layers''' cannot be undone
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
<br>
 
<table>
 
<table>
 
<tr>
 
<tr>
 
<td>[[file:LayersToolButtonsDELETE.JPG|link=]]</td>
 
<td>[[file:LayersToolButtonsDELETE.JPG|link=]]</td>
<td>Select the layer to be deleted and click the '''Delete Button'''. <span style="background-color: yellow;"> If you don't select a layer to delete then '''Trainz''' will select the current '''Active Layer'''. </span></td>
+
<td>Select the layer to be deleted and click the '''Delete Button'''. <span style="background-color: yellow; font-weight: 700;"> If you don't select a layer to delete then Trainz will select the current Active Layer. </span></td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#fcbcbc>
+
<table bgcolor="red" width=900>
 
<tr valign="top">
 
<tr valign="top">
<td colspan=2><span style="font-size: 17px;"><b>Warning:</b></span></td>
+
<td>
</tr>
+
<table bgcolor=#fcbcbc width=896>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:Stop.PNG|link=]]</td>
 
<td>[[file:Stop.PNG|link=]]</td>
 
<td>'''Deleting a layer will delete ALL the objects placed in that layer''' except objects that are "Bound" to that layer. See [[file:PageLink.PNG|link=]] '''[[#The Bound Layer|The Bound Layer]]''' section below.</td>
 
<td>'''Deleting a layer will delete ALL the objects placed in that layer''' except objects that are "Bound" to that layer. See [[file:PageLink.PNG|link=]] '''[[#The Bound Layer|The Bound Layer]]''' section below.</td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[file:Stop.PNG|link=]]</td>
 +
<td>In '''TRS19''' and later '''Trainz''' versions there will be a delay when deleting a layer. The delay will be indicated by a progress bar but can take several minutes on very large routes.<br>
 +
<span style="color: white; background-color: red; font-weight: 700;">&nbsp;Resist any urge to click the Cancel button&nbsp;</span><br>
 +
This delay will occur '''every time''' a layer is deleted.</td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[file:Stop.PNG|link=]]</td>
 +
<td>Due to a "bug" '''deleting a layer that contains a ruler will not delete the ruler'''. It will be hidden from view but it may reappear if another layer with the same name as the deleted layer is created or it will, eventually, reappear in the '''route-layer'''.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 258: Line 382:
 
<td>[[file:LayerDeleteEmpty.JPG|link=]]</td>
 
<td>[[file:LayerDeleteEmpty.JPG|link=]]</td>
 
<td>
 
<td>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr>
 
<tr>
 
<td colspan="2">
 
<td colspan="2">
Line 273: Line 397:
 
----</td>
 
----</td>
 
</tr>
 
</tr>
</table></td>
+
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 283: Line 408:
 
<td>[[file:LayerDeleteNotEmpty.JPG|link=]]</td>
 
<td>[[file:LayerDeleteNotEmpty.JPG|link=]]</td>
 
<td>
 
<td>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr>
 
<tr>
 
<td colspan="2">
 
<td colspan="2">
Line 291: Line 416:
 
<td>[[file:Choices.PNG|link=]]</td>
 
<td>[[file:Choices.PNG|link=]]</td>
 
<td><span style="font-size: 17px;">'''Choices:'''</span><br>
 
<td><span style="font-size: 17px;">'''Choices:'''</span><br>
*Click '''Merge''' to merge this layer and its contents into another layer. See '''Merging Layers''' below for more information. <span style="background-color: #fcbcbc; font-weight: 700;">&nbsp;NOTE: Merge cannot be undone&nbsp;</span>
+
*Click '''Merge''' to merge this layer and its contents into another layer. See '''Merging Layers''' below for more information
*Click '''Delete''' to delete the layer and its contents. <span style="background-color: #fcbcbc; font-weight: 700;">&nbsp;NOTE: Delete cannot be undone&nbsp;</span>
+
*Click '''Delete''' to delete the layer and its contents
 
*Click '''Cancel''' to cancel the delete operation</td>
 
*Click '''Cancel''' to cancel the delete operation</td>
 +
</tr>
 +
</table>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<td colspan="2">
 
<td colspan="2">
----</td>
+
----
</tr>
+
</td>
</table></td>
+
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 305: Line 431:
 
==Merging Layers==
 
==Merging Layers==
  
 +
<table bgcolor="red" width=300>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#fcbcbc width=296>
 +
<tr valign="top">
 +
<td>[[file:Stop.PNG|link=]]</td>
 +
<td><span style="font-size: 15px; font-weight: 700;">WARNING:</span><br>
 +
'''Mergeing Layers''' cannot be undone
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
<br>
 
<table>
 
<table>
 
<tr>
 
<tr>
 
<td>[[file:LayersToolButtonsMERGE.JPG|link=]]</td>
 
<td>[[file:LayersToolButtonsMERGE.JPG|link=]]</td>
<td>Select the layer to be merged into another layer and click the '''Merge Button'''. <span style="background-color: yellow;"> If you don't select a layer to merge then '''Trainz''' will select the current '''Active Layer'''. </span></td>
+
<td>Select the layer to be merged into another layer and click the '''Merge Button'''. <span style="background-color: yellow; font-weight: 700;"> If you don't select a layer to merge then Trainz will select the current Active Layer. </span></td>
 
</tr>
 
</tr>
 
</table>
 
</table>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
Line 324: Line 465:
 
</tr>
 
</tr>
 
</table>
 
</table>
 +
<br>
 +
<table bgcolor="red" width=900>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#fcbcbc>
 +
<tr valign="top">
 +
<td>[[file:Stop.PNG|link=]]</td>
 +
<td>In '''TRS19''' and later '''Trainz''' versions there will be a delay when merging a layer. The delay will be indicated by a progress bar but can take several minutes on very large routes.<br>
 +
<span style="color: white; background-color: red; font-weight: 700;">&nbsp;Resist any urge to click the Cancel button&nbsp;</span><br>
 +
This delay will occur '''every time''' a layer is merged.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
<br>
  
 
The layer merge dialogue window will appear as shown below:-
 
The layer merge dialogue window will appear as shown below:-
Line 331: Line 489:
 
<td>[[file:LayersMergeInto.JPG|link=]]</td>
 
<td>[[file:LayersMergeInto.JPG|link=]]</td>
 
<td>
 
<td>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr>
 
<tr>
 
<td colspan="2">
 
<td colspan="2">
Line 348: Line 506:
 
</tr>
 
</tr>
 
</table>
 
</table>
<br>
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 355: Line 512:
 
==Locking Layers==
 
==Locking Layers==
  
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
<td>It is good practice to '''LOCK ALL LAYERS that you are not currently editing.''' This will avoid the all too common problem of accidentally adding objects to the wrong layer.</td>
+
<td>It is good practice to '''LOCK ALL LAYERS that you are not currently editing.''' This will avoid the all too common problem of accidentally adding objects to the wrong layer.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 372: Line 536:
  
 
'''To LOCK an individual layer, click on the ''Open Padlock'' icon next to its name.''' The layer being locked does not have to be the current '''Active Layer'''.
 
'''To LOCK an individual layer, click on the ''Open Padlock'' icon next to its name.''' The layer being locked does not have to be the current '''Active Layer'''.
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 412: Line 576:
  
 
==Moving a Layer==
 
==Moving a Layer==
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td colspan=2><span style="font-size: 17px;"><b>Main Points:</b></span></td>
 
<td colspan=2><span style="font-size: 17px;"><b>Main Points:</b></span></td>
Line 427: Line 591:
 
</tr>
 
</tr>
 
</table>
 
</table>
 
+
<br>
 +
<table bgcolor="red" width=900>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#fcbcbc width=896>
 +
<tr valign="top">
 +
<td>[[file:Stop.PNG|link=]]</td>
 +
<td>
 +
In '''TRS19''' and later '''Trainz''' versions there will be a delay when moving a layer. The delay will be indicated by a progress bar but can take several minutes on very large routes<br>
 +
<span style="color: white; background-color: red; font-weight: 700;">&nbsp;Resist any urge to click the Cancel button&nbsp;</span><br>
 +
This delay will occur '''every time''' a layer is moved.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
<br>
 
In the example shown below a layer created in the Route Layers Group is being moved into the Session Layers Group.
 
In the example shown below a layer created in the Route Layers Group is being moved into the Session Layers Group.
 
<table>
 
<table>
Line 434: Line 615:
 
<td>[[file:LayersMove3.JPG|link=]]</td>
 
<td>[[file:LayersMove3.JPG|link=]]</td>
 
<td>
 
<td>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr>
 
<tr>
 
<td colspan="2">
 
<td colspan="2">
Line 455: Line 636:
 
*The only situation where layer order within a layer group makes any difference is when adding track objects (e.g. signals, track signs, etc) to a track.
 
*The only situation where layer order within a layer group makes any difference is when adding track objects (e.g. signals, track signs, etc) to a track.
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 484: Line 665:
 
<td>
 
<td>
 
*In the image shown left the '''Trees''' layer has its '''Eye Icon''' set to '''Hide'''<br><br>
 
*In the image shown left the '''Trees''' layer has its '''Eye Icon''' set to '''Hide'''<br><br>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 498: Line 679:
 
</table>
 
</table>
 
<br>
 
<br>
<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="stepRouteSession"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepTool|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>
 
</tr>
</table>
+
</table> <!-- END Nav Buttons Table -->
  
 
='''Route Layers vs Session Layers'''=
 
='''Route Layers vs Session Layers'''=
Line 508: Line 693:
 
This topic has filled endless threads in the '''Trainz Forums''' with arguments raging on both sides.
 
This topic has filled endless threads in the '''Trainz Forums''' with arguments raging on both sides.
  
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
 
<td colspan=2><span style="font-size: 17px;"><b>In Summary:</b></span></td>
Line 514: Line 699:
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
<td>In general, there are no "cast iron" rules that dictate what should be placed in the '''Route Layers Group''' and what should be placed in the '''Session Layers Group''' (for an exception see '''Trainz Plus and TRS19 Platinum Notes''' below). Each Route and Session will be different and different creators have different ways of working. The main question to be asked is how many different '''Sessions''' will be created using a particular '''Route'''?</td>
+
<td>In general, there are no "cast iron" rules that dictate what should be placed in the '''Route Layers Group''' and what should be placed in the '''Session Layers Group''' (for an exception see '''TRS19 Platinum Edition, Trainz Plus, TRS22 Notes''' below). Each Route and Session will be different and different creators have different ways of working. The main question to be asked is how many different '''Sessions''' will be created using a particular '''Route'''?</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table cellpadding=4 bgcolor=#ffffb0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 +
----
 
*'''For a Route with only a single Session''' - everything can safely go into the '''Route Layers Group'''
 
*'''For a Route with only a single Session''' - everything can safely go into the '''Route Layers Group'''
 
:Many creators only ever build a single Session for each of their Routes and do not use Session Layers at all (but they still have to save the session separately from the route).  
 
:Many creators only ever build a single Session for each of their Routes and do not use Session Layers at all (but they still have to save the session separately from the route).  
 
*'''For a Route with multiple (2 or more) Sessions''' - certain things will probably need to go into the '''Session Layers Group''' for each Session.
 
*'''For a Route with multiple (2 or more) Sessions''' - certain things will probably need to go into the '''Session Layers Group''' for each Session.
:Many creators build multiple Sessions for each Route and rely on the Session Layers to create the differences between their Sessions.  
+
:Many creators build multiple Sessions for each Route and rely on the Session Layers to create the differences between their Sessions.
 +
*Many scenery assets actually have their properties stored in the Session, even when the assets themselves are in a Route layer. Editing the properties of these assets is considered to be a '''change to the Session'''.  Unless you have a particular reason for saving the edited data (such as a change to commodities) you can '''usually''' ignore the offer to save the Session. These assets include:-
 +
**junction switches - the left/right switch direction is stored in the Session
 +
**industries - the commodities and quantities loaded/unloaded are stored in the Session (but the '''default''' direction is stored in the Route)
 +
**industry enabled wagons - the commodities and quantities carried are stored in the Session
 +
**consist locations ('''TRS19 Platinum Edition''', '''Trainz Plus''' and '''TRS22''') - this is stored in the Session (unless you need to save their new locations, you can safely ignore the offer to save the Session)
 +
**named route objects ('''TRS19 Platinum Edition''', '''Trainz Plus''' and '''TRS22''') - while the name is stored in the Route, adding or changing the name is treated as a change to the Session
 
</td>
 
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table cellpadding=4 bgcolor=#ffffb0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td>[[file:NotePad.PNG|link=]]</td>
<td><span style="font-size: 17px; font-weight: 700;">Trainz Plus and TRS19 Platinum Notes:</span><br>
+
<td><span style="font-size: 17px; font-weight: 700;">TRS19 Platinum Edition, Trainz Plus, TRS22 Notes:</span><br>
*The '''recommended''' practice in these versions of Trainz is to place all consists in a '''session layer''' and '''NOT''' in a '''route layer'''. Because these versions use a '''Unified Driver Surveyor''', placing a train in a route layer after switching from Driver to Surveyor will mean that it will not appear in your existing sessions (other than the one you are currently editing)
+
----
*Recent experiments using the '''Unified Driver Surveyor''' have indicated that when portals produce trains they will be placed into the same layer as the portal - so if a train that is in a '''Session layer''' enters a portal that is in a '''Route layer''' and is later returned to the layout, it will be returned in the same '''Route layer''' as the portal. This has ''possibly always been the case'' with portals but has not been noticed until the arrival of the '''Unified Driver Surveyor'''</td>
+
*The '''recommended''' practice in these versions of Trainz is to place all consists in a '''session layer''' and '''NOT''' in a '''route layer'''. Because these versions use a '''Unified Driver Surveyor''', placing a train in a route layer after switching from Driver to Surveyor can cause problems. For example:
 +
**If active Driver consists (i.e. those under manual or AI control) are in a route layer and you switch from Driver to Surveyor to edit the route and save the route edit, then those consists will be saved in their new positions, not their starting positions for the session.
 +
*Recent experiments using the '''Unified Driver Surveyor''' have indicated that when portals produce trains they will be placed into the same layer as the portal - so if a train that is in a '''Session layer''' enters a portal that is in a '''Route layer''' and is later returned to the layout, it will be returned in the same '''Route layer''' as the portal. This has ''possibly always been the case'' with portals but has not been noticed until the arrival of the '''Unified Driver Surveyor'''
 +
For more details see the Trainz Wiki page [[image:WikiLink.PNG|link=]]'''[[How_to_Use_the_UDS_Interface|How to Use the UDS Interface]]'''</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
 
==The Route Layers Group==
 
==The Route Layers Group==
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 551: Line 746:
 
*'''Hiding and Showing Objects''' in '''Driver Mode'''. There is a Session Rule and a Driver Command that can hide and show layers during the running of a Session. For example: a rail worker can be placed in a separate layer and positioned next to a track lever while shunting operations are underway but can be removed from the scene by hiding that layer when shunting has been completed.
 
*'''Hiding and Showing Objects''' in '''Driver Mode'''. There is a Session Rule and a Driver Command that can hide and show layers during the running of a Session. For example: a rail worker can be placed in a separate layer and positioned next to a track lever while shunting operations are underway but can be removed from the scene by hiding that layer when shunting has been completed.
 
*A '''Test Layer''' for experimenting. Not sure if a particular object is right for your layout? Place it in a temporary layer which you can hide and show to see any differences it makes. This is particularly useful if you are deciding between different types of grasses, for example, placed throughout the layout. If the objects prove to be unsuitable then they can all be deleted by deleting the layer. If they are suitable then the layer can be merged with another or left as a new layer.
 
*A '''Test Layer''' for experimenting. Not sure if a particular object is right for your layout? Place it in a temporary layer which you can hide and show to see any differences it makes. This is particularly useful if you are deciding between different types of grasses, for example, placed throughout the layout. If the objects prove to be unsuitable then they can all be deleted by deleting the layer. If they are suitable then the layer can be merged with another or left as a new layer.
*A '''Ruler Layer''' if you are using rulers. Although rulers obey layer behavior (lock and hide) just like all other objects and splines, they have no properties window to show their layer or allow you to change that layer. Consider placing all rulers in a dedicated layer to make their management easier.
+
*A '''Ruler Layer''' if you are using rulers. Although rulers obey layer behavior (lock and hide) just like all other objects and splines, they have no properties window to show their layer or allow you to change that layer. Consider placing all rulers in a dedicated layer to make their management easier. <span style="background-color: red; color: white; font-weight: 700;">&nbsp;NOTE:&nbsp;</span>&nbsp;Due to a bug in TANE/TRS19, deleting a dedicated '''Ruler Layer''' will not delete the rulers but will '''temporarily''' hide them from view. Rulers will still have to be deleted individually.
  
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>
 
<td>
 
*'''It is a good idea to place ALL the consists in the same layer''' particularly if they are going to be coupled together during the running of a Session.
 
*'''It is a good idea to place ALL the consists in the same layer''' particularly if they are going to be coupled together during the running of a Session.
*A very useful development tool is the '''Bound Layer'''. See [[file:PageLink.PNG|link=]] '''[[#The Bound Layer|The Bound Layer]]''' section below.</td>
+
*A very useful development tool is the '''Bound Layer'''. See [[file:PageLink.PNG|link=]] '''[[#The Bound Layer|The Bound Layer]]''' section below.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 564: Line 766:
 
===The "route-layer"===
 
===The "route-layer"===
  
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 573: Line 775:
 
While all layers are equal, the "route-layer" is special.
 
While all layers are equal, the "route-layer" is special.
  
<table cellpadding="4" bgcolor=#fcbcbc>
+
<table bgcolor="red" width=900>
 
<tr valign="top">
 
<tr valign="top">
<td colspan=2><span style="font-size: 17px;"><b>Warning:</b></span></td>
+
<td>
</tr>
+
<table bgcolor=#fcbcbc width=896>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:Stop.PNG|link=]]</td>
 
<td>[[file:Stop.PNG|link=]]</td>
<td>'''Track objects''', such as signals, junctions and track signs, ''cannot'' be placed in any layer that is above the layer (i.e. higher up the list of layers) containing the track that they are attached to. If the '''route-layer''' is used for all the track and track objects and this layer is left as the top layer then this will never be a problem.</td>
+
<td>'''Track objects''', such as signals, junctions and track signs, ''cannot'' be placed in any layer that is above the layer containing the track that they are attached to. If the '''route-layer''' is used for all the track and track objects and this layer is left as the top layer then this will never be a problem.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000 cellpadding=2>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
<td>It is recommended that the following objects should be placed in the "route-layer":-
+
<td>It is '''recommended''' that the following objects should be placed in the '''route-layer''':-
 
*Track and interactive industries with track
 
*Track and interactive industries with track
 
*Track infrastructure (turntables, bridges, tunnels, etc)
 
*Track infrastructure (turntables, bridges, tunnels, etc)
 
*Signals and track signs (speed limits, warnings, distance, etc)
 
*Signals and track signs (speed limits, warnings, distance, etc)
 
*Junctions and switches
 
*Junctions and switches
..and that the "route-layer" be placed at the top of the '''Route Layers Group'''.</td>
+
..and that the "route-layer" be placed at the top of the '''Route Layers Group'''.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
<br>
 
  
 
==The Session Layers Group==
 
==The Session Layers Group==
<table cellpadding="4" bgcolor=#c1e7e7>
+
 
 +
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 606: Line 819:
 
If you are creating more than one Session based around a particular Route, then you will probably make use of the Session Layers.
 
If you are creating more than one Session based around a particular Route, then you will probably make use of the Session Layers.
  
<table cellpadding="4" bgcolor=#ffffb0>
+
<table cellpadding=4 bgcolor=#ffffb0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 +
----
 
Session Layers can contain:-
 
Session Layers can contain:-
 
*Scenery objects that will only appear in one or some of the Sessions.
 
*Scenery objects that will only appear in one or some of the Sessions.
Line 616: Line 830:
 
</td>
 
</td>
 
</tr>
 
</tr>
</table>
+
<tr valign="top">
<table cellpadding="4" bgcolor=#ffffb0>
+
<td colspan=2>
 +
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>
 
<td>
*'''It is a good idea to place ALL the consists in the same Session Layer''' and using a Session Layer for '''ALL''' consists is the '''recommended''' method for '''Trainz Plus'''. Particularly if they are going to be coupled together during the running of a Session.
+
*'''It is a good idea to place ALL the consists in the same Session Layer''' and using a Session Layer for '''ALL''' consists is the '''recommended''' method for '''Trainz Plus'''. Particularly if they are going to be coupled together during the running of a Session
*'''When you first save a Session, give it a distinctive and informative name.''' Avoid the temptation to use '''Default''' as the name of your Session as you can easily end up with several Sessions under the same Route all called '''Default'''.</td>
+
*'''When you first save a Session, give it a distinctive and informative name.''' Avoid the temptation to use '''Default''' as the name of your Session as you can easily end up with several Sessions under the same Route all called '''Default'''
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<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="stepAdding"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepRouteSession|alt=Next Up|Top]]</td>
 +
<td width=75>[[file:NextDown.png|link=#stepDeleting|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 Objects To Layers'''=
 
='''Adding Objects To Layers'''=
Line 636: Line 865:
 
When an object (such as a scenery item, consist, track or track object) is added to the layout it is automatically placed in the currently '''Active Layer'''.  Unfortunately, '''Trainz''' does not indicate which layer is the '''Active Layer''' unless you open the Layers Tool to look. This can lead to objects being placed into the wrong layers and while these objects can later be moved to another layer (see the section [[file:PageLink.PNG|link=]] '''[[#Moving Objects To Other Layers|Moving Objects To Other Layers]]''' below) it would be better to correctly set the '''Active Layer''' first.
 
When an object (such as a scenery item, consist, track or track object) is added to the layout it is automatically placed in the currently '''Active Layer'''.  Unfortunately, '''Trainz''' does not indicate which layer is the '''Active Layer''' unless you open the Layers Tool to look. This can lead to objects being placed into the wrong layers and while these objects can later be moved to another layer (see the section [[file:PageLink.PNG|link=]] '''[[#Moving Objects To Other Layers|Moving Objects To Other Layers]]''' below) it would be better to correctly set the '''Active Layer''' first.
 
<br><br>
 
<br><br>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
<td>It is good practice to '''LOCK ALL LAYERS that you are not currently editing.''' This will avoid the all too common problem of accidentally adding objects to the wrong layer.</td>
+
<td>It is good practice to '''LOCK ALL LAYERS that you are not currently editing.''' This will avoid the all too common problem of accidentally adding objects to the wrong layer.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 658: Line 894:
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 665: Line 901:
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000 width=1000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffb0 width=996>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td>[[file:NotePad.PNG|link=]]</td>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
 
<td><span style="font-size: 17px;">'''Notes:'''</span><br>
There are many features of Trainz Routes and Sessions that are '''NOT stored in layers'''. These include:-
+
----
 +
There are many features of '''Trainz Routes''' and '''Sessions''' that are '''NOT stored in layers'''. In some cases while the objects themselves may be placed in layers, their settings or properties are not. These include:-
 
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
 
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
 
*landforms
 
*landforms
 
*textures
 
*textures
*trackside camera positions and settings
+
*'''TurfFX''' and '''Clutter''' ground effects
 +
*trackside camera '''settings'''
 
*weather conditions
 
*weather conditions
 
*time of day
 
*time of day
 
*session rules and driver commands
 
*session rules and driver commands
*signal and junctions settings
+
*signal and junctions '''settings'''
 
*rolling stock loads
 
*rolling stock loads
*industry settings
+
*industry '''settings'''
 
*portal settings
 
*portal settings
*passenger station settings
+
*passenger station '''settings'''
 
*navigation points
 
*navigation points
*interlocking tower settings'''^'''
+
*interlocking tower '''settings''' [[file:BugMini.PNG|link=]]
 
</div>
 
</div>
Landforms, textures and trackside cameras are saved as part of the '''Route''' while all the others are saved as part of a '''Session'''.
+
</td>
<br>
+
</tr>
'''^''' A bug has been reported in the Interlocking Towers (and the Enhanced Interlocking Towers) where the path and settings are initially saved in the Route but any later edits and changes are then saved in the Session. The workaround for this is to always load the Session when working with ITs and EITs.
+
<tr valign="top">
 +
<td>[[file:DotPoint.JPG|link=]]</td>
 +
<td>Landforms, textures, effect layers (TurfFX, Clutter) and some Environment settings are saved as part of the '''Route''' while all the others are saved as part of a '''Session'''</td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[file:DotPoint.JPG|link=]]</td>
 +
<td>When you enter or edit the name of a route layer scenery object, such as a station name board, that change will be treated as a change to the '''Session''' but the new or edited name will still be saved as a property of the scenery object in a '''Route''' layer. When you save, you will be given the option of saving the '''Session''' as well as the '''Route'''. You can ignore the offer to save the '''Session''' if you have not edited any objects in a '''Session Layer''', the '''Session Layers''' themselves (e.g. moved, merged, deleted or renamed) or other '''Session''' properties (e.g. commodity levels or loads). <span style="background-color: yellow; font-weight: 700;">&nbsp;If uncertain, always save the Session&nbsp;</span>
 +
</td>
 +
</tr>
 +
<tr valign="top">
 +
<td>[[file:Bug.png|link=|30px]]</td>
 +
<td>A bug has been reported in the '''Interlocking Towers''' (and the '''Enhanced Interlocking Towers''') where the path and settings are initially saved in the '''Route''' but any later edits and changes are then saved in the '''Session'''. The workaround for this is to always load the '''Session''' when working with '''IT''' and '''EIT''' assets. This problem has not been resolved in the latest versions of '''Trainz'''.
 +
</td>
 +
</tr>
 +
</table>
 
</td>
 
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<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="stepDeleting"></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=#stepMoving|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 -->
  
 
='''Deleting Objects From Layers'''=
 
='''Deleting Objects From Layers'''=
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000 width=900>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
<td>It is good practice to '''LOCK ALL LAYERS that you are not currently editing.''' This will avoid the all too common problem of accidentally deleting objects from the wrong layer.</td>
+
<td>
 +
*It is good practice to '''LOCK ALL LAYERS that you are not currently editing.''' This will avoid the all too common problem of accidentally deleting objects from the wrong layer.
 +
*An exception to this "good practice" is when managing rulers. Unless you have used a dedicated ruler layer for all rulers it can be difficult to discover which layer contains a particular ruler. If rulers are not added to a dedicated layer then you will need to unlock and unhide all the layers first before you can use the '''Delete Ruler''' tool.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
* An exception to this practice may be required when using the <b>Delete Ruler</b> tool. Unless a dedicated ruler layer was established, or otherwise, if the layer of a ruler(s) to be deleted is specifically known, there is no easy way to identify which of layer(s) a ruler(s) may reside on (this due to the unavailability of properties windows for rulers). Therefore when using the <b>Delete Ruler</b> tool, it is most efficient to temporarily unlock and unhide all layers under most circumstances.
 
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 713: Line 980:
 
</tr>
 
</tr>
 
</table>
 
</table>
 
+
<br>
 
Unfortunately '''Trainz''' does not give you a warning message when you attempt to delete an object from a locked layer, the object just refuses to be deleted.
 
Unfortunately '''Trainz''' does not give you a warning message when you attempt to delete an object from a locked layer, the object just refuses to be deleted.
 
+
<br>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>If you cannot delete an object then check:-
 
<td>If you cannot delete an object then check:-
*that the objects layer and bound layer (if set) are unlocked
+
*that the objects layer and bound layer (if it has been set) are unlocked
*that you are using the correct delete tool (e.g. such as attempting to delete a tree with the spline, signal or rolling stock delete tool) - it happens!</td>
+
*that you are using the correct delete tool (e.g. such as attempting to delete a tree with the spline, signal or rolling stock delete tool) - it happens!
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
<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="stepMoving"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepDeleting|alt=Next Up|Top]]</td>
 +
<td width=75>[[file:NextDown.png|link=#stepBound|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 -->
  
 
='''Moving Objects To Other Layers'''=
 
='''Moving Objects To Other Layers'''=
Line 737: Line 1,015:
 
<td>[[file:LayersObjectProperties.JPG|link=]]</td>
 
<td>[[file:LayersObjectProperties.JPG|link=]]</td>
 
<td>
 
<td>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:Steps.PNG|link=]]</td>
 
<td>[[file:Steps.PNG|link=]]</td>
Line 754: Line 1,032:
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 765: Line 1,043:
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
<td>Rulers cannot be moved to a different layer because no properties window can be summoned for them. To move a ruler to another layer, it must be manually reproduced on the desired layer (using the Add Ruler Tool), then the pre-existing ruler must be deleted (using the Delete Ruler tool). </td>
+
<td>Rulers cannot be moved to a different layer because they do not have a properties window. If it is necessary to move a ruler to another layer, it must be manually created in the desired layer (using the '''Add Ruler''' tool), then the pre-existing ruler must be deleted (using the '''Delete Ruler''' tool). </td>
 
</tr>
 
</tr>
 
</table></td>
 
</table></td>
Line 774: Line 1,052:
 
</table>
 
</table>
 
<br>
 
<br>
<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="stepBound"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepMoving|alt=Next Up|Top]]</td>
 +
<td width=75>[[file:NextDown.png|link=#stepDriver|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 -->
  
 
='''The Bound Layer'''=
 
='''The Bound Layer'''=
Line 784: Line 1,066:
 
This is a little used and probably little understood layer feature. It allows you to attach an object to two different layers so it can have the properties (locked/unlocked and show/hide) of both layers. The bound layer was introduced as a development tool, its sole use is as a tool in the building of routes and sessions.
 
This is a little used and probably little understood layer feature. It allows you to attach an object to two different layers so it can have the properties (locked/unlocked and show/hide) of both layers. The bound layer was introduced as a development tool, its sole use is as a tool in the building of routes and sessions.
  
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 792: Line 1,074:
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>'''An object will be HIDDEN if its layer OR its <span style="text-decoration: underline;">bound layer</span> is hidden.'''
 
<td>'''An object will be HIDDEN if its layer OR its <span style="text-decoration: underline;">bound layer</span> is hidden.'''
 +
</tr>
 +
<tr valign="top">
 +
<td>[[file:DotPoint.JPG|link=]]</td>
 +
<td>'''Rulers cannot be bound to another layer.'''
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 803: Line 1,089:
 
<td>[[file:LayersBoundLayer.JPG|link=]]</td>
 
<td>[[file:LayersBoundLayer.JPG|link=]]</td>
 
<td><br>
 
<td><br>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr>
 
<tr>
 
<td colspan="2">
 
<td colspan="2">
Line 824: Line 1,110:
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#c1e7e7>
+
<table cellpadding=4 bgcolor=#c1e7e7>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:DotPoint.JPG|link=]]</td>
 
<td>[[file:DotPoint.JPG|link=]]</td>
Line 832: Line 1,118:
 
<br>
 
<br>
  
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
Line 838: Line 1,127:
 
*Create a new empty layer called "Locked" or "Hidden" and lock or hide that layer, according to your needs
 
*Create a new empty layer called "Locked" or "Hidden" and lock or hide that layer, according to your needs
 
*Bind the individual objects to that layer as required
 
*Bind the individual objects to that layer as required
*When editing, testing or whatever you are doing has been completed simply delete the new layer. All objects that have been bound to that layer will have their '''Bound Layer''' property reset to '''none''' so the hidden objects will reappear and the locked objects will be unlocked.</td>
+
*When editing, testing or whatever you are doing has been completed simply delete the new layer. All objects that have been bound to that layer will have their '''Bound Layer''' property reset to '''none''' so the hidden objects will reappear and the locked objects will be unlocked.
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
<br>
+
</td>
 
+
<table cellpadding="4" bgcolor=#ffffb0>
+
<tr valign="top">
+
<td>[[file:PencilTips.PNG|link=]]</td>
+
<td>If you need to remove an object from a route but cannot alter the route (e.g. it is payware or under another users kuid) then create a new hidden session layer and change the bound layer of the object to the hidden layer. This will be treated as a change to the session only and Trainz will not ask you to save the route as well as the session.</td>
+
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
  
<table cellpadding="4" bgcolor=#ffffb0>
+
<table bgcolor=#000000>
 +
<tr valign="top">
 +
<td>
 +
<table bgcolor=#ffffe0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
<td>Note that although <b>rulers</b> are layer resident, they cannot be managed by a bounding layer technique because there is no facility to display or edit their properties.</td>
+
<td>If you need to remove an object from a route but cannot alter the route (e.g. it is payware or under another users kuid) then create a new hidden session layer and change the bound layer of the object to the hidden layer. This will be treated as a change to the session only and Trainz will not ask you to save the route as well as the session.
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
<br>
 
<br>
  
<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="stepDriver"></span>&nbsp;</td>
 +
<td width=46>[[file:BackToTop.png|link=#top|alt=Top|Top]]</td>
 +
<td width=75>[[file:NextUp.png|link=#stepBound|alt=Next Up|Top]]</td>
 +
<td width=75>[[file:NextDown.png|link=#bottom|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 -->
  
 
='''Layers in Driver Mode'''=
 
='''Layers in Driver Mode'''=
Line 884: Line 1,180:
 
#'''A Session Rule''' - specific to a particular driver, consist, or any driver/consist<br>
 
#'''A Session Rule''' - specific to a particular driver, consist, or any driver/consist<br>
 
=='''Using a Driver Command'''==
 
=='''Using a Driver Command'''==
The driver command '''Layer Control''' hides and shows named layers.<br>
+
The driver command [[file:WikiLink.PNG|link=]] '''[[Driver_Commands_List#Layer_Control|Layer Control]]''' hides and shows named layers.<br>
 
[[file:LayerControlExample.png|link=]]<br>
 
[[file:LayerControlExample.png|link=]]<br>
 +
 
=='''Using Session Rules'''==
 
=='''Using Session Rules'''==
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr valign="top">
 
<tr valign="top">
 
<td width="58">[[file:RulesWiki.PNG|link=]]</td>
 
<td width="58">[[file:RulesWiki.PNG|link=]]</td>
Line 899: Line 1,196:
 
*'''[[Session_Rule_List_with_Parameters#Message_Popup_Rule|Message Popup Rule]]''' - to open a browser window with a message
 
*'''[[Session_Rule_List_with_Parameters#Message_Popup_Rule|Message Popup Rule]]''' - to open a browser window with a message
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr valign="top">
 
<tr valign="top">
 
<td width="58">[[file:screenshot.PNG|link=]]</td>
 
<td width="58">[[file:screenshot.PNG|link=]]</td>
Line 912: Line 1,209:
 
</table>
 
</table>
 
<br>
 
<br>
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr valign="top">
 
<tr valign="top">
 
<td width="58">[[file:explanation.PNG|link=]]</td>
 
<td width="58">[[file:explanation.PNG|link=]]</td>
Line 920: Line 1,217:
 
</table>
 
</table>
 
In this example:-
 
In this example:-
*The '''Trackside Check Rule''' is triggered when a specific train comes to a stop at a trackmark. This then executes the following rules:-
+
*The '''Trackside Check Rule''' is triggered when a specific train comes to a stop at a trackmark. This then executes the following rules in order:-
 
**The '''Show/Hide Layer Rule''' is used to hide the layer named "People". Four passengers (three standing and one seated) are hidden.
 
**The '''Show/Hide Layer Rule''' is used to hide the layer named "People". Four passengers (three standing and one seated) are hidden.
 
**The '''Show/Hide Layer Rule''' is used to hide the layer named "CNJCartsFull". The boxes and mail bags on the three platform trolleys are hidden.
 
**The '''Show/Hide Layer Rule''' is used to hide the layer named "CNJCartsFull". The boxes and mail bags on the three platform trolleys are hidden.
 
**The '''Message Popup Rule''' is used to place a message on the screen informing the player that the passengers and mail have been loaded.
 
**The '''Message Popup Rule''' is used to place a message on the screen informing the player that the passengers and mail have been loaded.
 
<br>
 
<br>
<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=#stepDriver|alt=Next Up|Top]]</td>
 +
<td width=75>&nbsp;</td>
 +
<td width=75>&nbsp;</td>
 
</tr>
 
</tr>
</table>
+
</table> <!-- END Nav Buttons Table -->
 
+
 
----
 
----
 
----
 
----
  
 
='''Trainz Wiki'''=
 
='''Trainz Wiki'''=
<table cellpadding="4" bgcolor=#ffffff>
+
<table cellpadding=4 bgcolor=#ffffff>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:TrainzWiki.png|link=]]</td>
 
<td>[[file:TrainzWiki.png|link=]]</td>

Latest revision as of 23:16, 13 April 2022

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

Contents

  Top   Next Down Bottom

[edit] What Are Layers?

In Summary:
DotPoint.JPG Layers are a Surveyor tool that allows you to better manage the objects that are placed in your Trainz World.
DotPoint.JPG Layers are a Driver tool that allows you to change what the players see as they drive around your Trainz World.

Layers can contain any objects, visible and invisible, that can be placed into a layout using the Surveyor Object, Track and Train tools. The layers and their contents can be hidden from view or locked against alteration whenever required. Their main use is in the development of a Route and a Session but they can also be used as a way of providing some additional novelty during a Driver session.

NotePad.PNG Effect Layers Notes:

The special ground effects layers, Clutter and TurfFX, that are available in the Topology Tools (press the  F1  key) are not discussed here. They are more like Textures than Layers but some aspects of their use and operations are similar to the layers covered here. These special ground effects layers are saved as part of a Route but are not associated with any Route Layer.

  Top Next Up Next Down Bottom

[edit] The Layers Tool

SurveyorToolMenuLayers.JPG












RightArrowRed.JPG
Click the Layers Tool to open up its properties.
LayersTools.JPG


NotePad.PNG Notes:

The layers are organised into two groups:-

  • Route Layers in the top group, and
  • Session Layers in the lower group.
Each group can contain multiple layers - the scroll bars next to the layer names shown on the left indicate that there are more layers in each group than can fit into the display window area.


[edit] Loading a Route and Loading a Session

In Summary:
DotPoint.JPG Route Layers are saved with the Route. Session Layers are saved with the Session.
DotPoint.JPG If you edit a Session Layer and later load just the Route then those edits will not appear.


LinkWiki.PNG

More information on creating, loading and saving Routes and Sessions can be found on the Trainz Wiki Page at Route and Session Basics


The layers you see will depend on whether you have loaded a Route by itself (with no "child" Session) or a Session and its "parent" Route.

LayersToolsRoute.JPG LayersToolsSession.JPG The first image on the left gives an example of the layers that can appear if a Route only is loaded into Surveyor. These are the layers that are saved with the Route. Note that a default "session-layer" is present.
DotPoint.JPG An empty default "session-layer" is always created in the Session Layers Group when only the Route is loaded into Surveyor.
DotPoint.JPG If you load just the Route and edit its "session-layer" then those edits will not appear the next time you load just the Route because an empty "session-layer" is created each time a Route is loaded without a Session.

The second image on the left gives an example of the layers that can appear if a Session based on that Route is loaded into Surveyor. It shows Route Layers and Session Layers.

In both cases, the Route Layers are identical because the same Route has been loaded. A Session contains its own layers, the Session Layers, that are loaded and saved with the Session but are not loaded or saved with the Route.

PencilTips.PNG If you load a Session and do not want to edit any of the Route layers then click the Lock Route Layers icon on the Layers Tool
LayersToolButtonsLOCKALL.JPG Click the Lock Button



Stop.PNG If you load a ROUTE but not the SESSION then only edit the Route Layers
Stop.PNG If you edit a SESSION or its layers then always save the Session
Stop.PNG When you save a new SESSION always give it a name, do NOT leave it as "Default"

[edit] Creating a New Route

LayersNewRoute.JPG
LayersNewRoute.JPG
NotePad.PNG Notes:

  • When a brand new route is created it will come with two layers, a single route-layer and a single session-layer.
  • Both layers will be empty (the baseboard with its grid is saved with the route but is not in any layer).
PencilTips.PNG A layer can be renamed at anytime by double clicking on its name with the left mouse button and typing a new name

[edit] The "Active Layer"

In Summary:
DotPoint.JPG The Active Layer is the selected (highlighted) layer.
DotPoint.JPG When you load the Route only into Surveyor, the first Route layer will be the Active Layer
DotPoint.JPG When you load a Session into Surveyor, the first Session layer will be the Active Layer

In the image above, the route-layer is the Active Layer. You can change the Active Layer at any time by clicking on the name of another layer.

NotePad.PNG Notes:

The Active Layer is the "working layer" which is:-

  • where new objects will be added to the layout
  • the layer that is automatically selected for merging and deleting
 
Stop.PNG Trainz does not identify which is the Active Layer in Surveyor and this often leads to problems such as objects being added to the wrong layer.

See PageLink.PNG Adding Objects To Layers below for more information.


[edit] Adding a New Layer

LayersToolButtonsADD.JPG Click the Add Button

An Add layer dialogue window will appear.

LayersAddLayer.JPG

Steps.PNG Steps:
  1. Enter a name for the new layer
  2. Select the layer group, Route or Session, where it will be placed
  3. Click the Tick.PNG icon

PencilTips.PNG You can easily rename the layer or move it to the other layer group if you change your mind.

[edit] Deleting a Layer

Stop.PNG WARNING:

Deleting Layers cannot be undone


LayersToolButtonsDELETE.JPG Select the layer to be deleted and click the Delete Button. If you don't select a layer to delete then Trainz will select the current Active Layer.


Stop.PNG Deleting a layer will delete ALL the objects placed in that layer except objects that are "Bound" to that layer. See PageLink.PNG The Bound Layer section below.
Stop.PNG In TRS19 and later Trainz versions there will be a delay when deleting a layer. The delay will be indicated by a progress bar but can take several minutes on very large routes.

 Resist any urge to click the Cancel button 

This delay will occur every time a layer is deleted.
Stop.PNG Due to a "bug" deleting a layer that contains a ruler will not delete the ruler. It will be hidden from view but it may reappear if another layer with the same name as the deleted layer is created or it will, eventually, reappear in the route-layer.

If the layer being deleted is empty, then the following dialogue window will appear:-

LayerDeleteEmpty.JPG

Choices.PNG Choices:
  • Click Yes to delete the layer
  • Click No to cancel the delete operation

If the layer being deleted is NOT empty, then the following dialogue window will appear:-

LayerDeleteNotEmpty.JPG

Choices.PNG Choices:
  • Click Merge to merge this layer and its contents into another layer. See Merging Layers below for more information
  • Click Delete to delete the layer and its contents
  • Click Cancel to cancel the delete operation

[edit] Merging Layers

Stop.PNG WARNING:

Mergeing Layers cannot be undone


LayersToolButtonsMERGE.JPG Select the layer to be merged into another layer and click the Merge Button. If you don't select a layer to merge then Trainz will select the current Active Layer.
In Summary:
DotPoint.JPG Merging a layer into another layer will move ALL the objects from the first layer into the second layer. The first layer, which is now empty, will then be deleted.
DotPoint.JPG Once layers have been merged they cannot be separated.


Stop.PNG In TRS19 and later Trainz versions there will be a delay when merging a layer. The delay will be indicated by a progress bar but can take several minutes on very large routes.

 Resist any urge to click the Cancel button 
This delay will occur every time a layer is merged.


The layer merge dialogue window will appear as shown below:-

LayersMergeInto.JPG

Steps.PNG Steps:
  1. Select the destination layer for the merge
  2. Click the Tick.PNG icon
The Merge into: list shows all the available layers with no distinction between Route Layers and Session Layers

[edit] Locking Layers

PencilTips.PNG It is good practice to LOCK ALL LAYERS that you are not currently editing. This will avoid the all too common problem of accidentally adding objects to the wrong layer.


DotPoint.JPG If you LOCK or UNLOCK a Route Layer while editing a Session then you will have made a change to the Route and will be asked to save both the Route and the Session when you exit Surveyor.


[edit] Locking Individual Layers

To LOCK an individual layer, click on the Open Padlock icon next to its name. The layer being locked does not have to be the current Active Layer.

DotPoint.JPG The objects in a LOCKED layer cannot be moved (around the layout) or deleted but they can be moved to other layers.
LayersRouteTreesActive.JPG LayersRouteTreesActiveLocked.JPG
  • The first image on the left shows two Route Layers, both UNLOCKED with their Padlock icons Open. One layer, "Trees", is highlighted showing that it is the currently active layer.
  • The second image on the left shows the same two layers after the "Trees" layer has been LOCKED.
  • A locked layer can be UNLOCKED by clicking its Closed Padlock icon.

If you attempt to add a scenery object to a locked layer you will receive the following message:-

LayersRouteTreesActiveLockedError.JPG
  • Click the Tick.PNG icon to UNLOCK the layer

[edit] Locking ALL Route Layers

LayersToolButtonsLOCKALL.JPG Click the Lock Button

This will LOCK ALL the layers in the Route Layers Group. The Session Layers Group will not be affected.

The Route Layers Group can be UNLOCKED by clicking the Lock Button again.

[edit] Moving a Layer

Main Points:
DotPoint.JPG Layers can be moved up or down
  • within the same layer group (e.g. Route or Session)
  • between the two groups
DotPoint.JPG A layer containing track objects (e.g. signals, switches, etc) CANNOT be placed above the layer containing the track


Stop.PNG

In TRS19 and later Trainz versions there will be a delay when moving a layer. The delay will be indicated by a progress bar but can take several minutes on very large routes
 Resist any urge to click the Cancel button 
This delay will occur every time a layer is moved.


In the example shown below a layer created in the Route Layers Group is being moved into the Session Layers Group.

LayersMove1.JPG LayersMove3.JPG

Steps.PNG Steps:
  1. Select the layer to be moved and hold down the left mouse button
  2. Drag the layer up or down to its new position

  • The move can be between layer groups as shown left or within groups to move the layer to a higher or lower position in the group.
  • The only situation where layer order within a layer group makes any difference is when adding track objects (e.g. signals, track signs, etc) to a track.


DotPoint.JPG When adding track objects to a track, the object being added must be in the same layer or in a layer below the layer containing the track. For more information, see the section PageLink.PNG The "route-layer" below.
DotPoint.JPG If you attempt to move a layer containing track objects, such as signals, to a position above the layer containing the track, you will get an error message.

[edit] Hiding Layers

To hide or show a layer click the Eye Icon next to its name.

LayersHideNone.JPG
  • In the image shown left the two trees are in different Route Layers
  • All the layers have their Eye Icons set to Show
LayersHideTree.JPG
  • In the image shown left the Trees layer has its Eye Icon set to Hide

DotPoint.JPG If you attempt to add an object to a hidden layer you will receive a warning message.
DotPoint.JPG Layers that are hidden when saved in Surveyor will also be hidden when loaded in Driver.


  Top Next Up Next Down Bottom

[edit] Route Layers vs Session Layers

This topic has filled endless threads in the Trainz Forums with arguments raging on both sides.

In Summary:
DotPoint.JPG In general, there are no "cast iron" rules that dictate what should be placed in the Route Layers Group and what should be placed in the Session Layers Group (for an exception see TRS19 Platinum Edition, Trainz Plus, TRS22 Notes below). Each Route and Session will be different and different creators have different ways of working. The main question to be asked is how many different Sessions will be created using a particular Route?


NotePad.PNG Notes:

  • For a Route with only a single Session - everything can safely go into the Route Layers Group
Many creators only ever build a single Session for each of their Routes and do not use Session Layers at all (but they still have to save the session separately from the route).
  • For a Route with multiple (2 or more) Sessions - certain things will probably need to go into the Session Layers Group for each Session.
Many creators build multiple Sessions for each Route and rely on the Session Layers to create the differences between their Sessions.
  • Many scenery assets actually have their properties stored in the Session, even when the assets themselves are in a Route layer. Editing the properties of these assets is considered to be a change to the Session. Unless you have a particular reason for saving the edited data (such as a change to commodities) you can usually ignore the offer to save the Session. These assets include:-
    • junction switches - the left/right switch direction is stored in the Session
    • industries - the commodities and quantities loaded/unloaded are stored in the Session (but the default direction is stored in the Route)
    • industry enabled wagons - the commodities and quantities carried are stored in the Session
    • consist locations (TRS19 Platinum Edition, Trainz Plus and TRS22) - this is stored in the Session (unless you need to save their new locations, you can safely ignore the offer to save the Session)
    • named route objects (TRS19 Platinum Edition, Trainz Plus and TRS22) - while the name is stored in the Route, adding or changing the name is treated as a change to the Session


NotePad.PNG TRS19 Platinum Edition, Trainz Plus, TRS22 Notes:

  • The recommended practice in these versions of Trainz is to place all consists in a session layer and NOT in a route layer. Because these versions use a Unified Driver Surveyor, placing a train in a route layer after switching from Driver to Surveyor can cause problems. For example:
    • If active Driver consists (i.e. those under manual or AI control) are in a route layer and you switch from Driver to Surveyor to edit the route and save the route edit, then those consists will be saved in their new positions, not their starting positions for the session.
  • Recent experiments using the Unified Driver Surveyor have indicated that when portals produce trains they will be placed into the same layer as the portal - so if a train that is in a Session layer enters a portal that is in a Route layer and is later returned to the layout, it will be returned in the same Route layer as the portal. This has possibly always been the case with portals but has not been noticed until the arrival of the Unified Driver Surveyor
For more details see the Trainz Wiki page WikiLink.PNGHow to Use the UDS Interface


[edit] The Route Layers Group

DotPoint.JPG The Route Layer Group should be used for everything that will always appear in Driver Mode regardless of which Session is playing.

There is nothing stopping you from placing everything in the "route-layer" of the Route Layers Group and never having to worry about dealing with layers ever again - some creators prefer to work this way. However, layers do provide you with a way of organising your scenery objects to make them more manageable, particularly in more complicated layouts. Some examples:-

  • A Special Objects layer or layers that can be used to hold certain scenery objects. For example all the trees or a particular building. This can be very useful when you need to hide those objects to locate or place other objects. Trackside cameras in particular can be very difficult to find when placed in a forest.
  • A Platform Objects layer can be used to hold all platform items such as seats, luggage, luggage trolleys, people, lamp posts, etc. Because these items are placed on top of a platform object they can be very difficult to move or delete without first moving the platform. The layer containing the platform can be locked allowing these objects to be easily moved or deleted.
  • Hiding and Showing Objects in Driver Mode. There is a Session Rule and a Driver Command that can hide and show layers during the running of a Session. For example: a rail worker can be placed in a separate layer and positioned next to a track lever while shunting operations are underway but can be removed from the scene by hiding that layer when shunting has been completed.
  • A Test Layer for experimenting. Not sure if a particular object is right for your layout? Place it in a temporary layer which you can hide and show to see any differences it makes. This is particularly useful if you are deciding between different types of grasses, for example, placed throughout the layout. If the objects prove to be unsuitable then they can all be deleted by deleting the layer. If they are suitable then the layer can be merged with another or left as a new layer.
  • A Ruler Layer if you are using rulers. Although rulers obey layer behavior (lock and hide) just like all other objects and splines, they have no properties window to show their layer or allow you to change that layer. Consider placing all rulers in a dedicated layer to make their management easier.  NOTE:  Due to a bug in TANE/TRS19, deleting a dedicated Ruler Layer will not delete the rulers but will temporarily hide them from view. Rulers will still have to be deleted individually.
PencilTips.PNG
  • It is a good idea to place ALL the consists in the same layer particularly if they are going to be coupled together during the running of a Session.
  • A very useful development tool is the Bound Layer. See PageLink.PNG The Bound Layer section below.

[edit] The "route-layer"

DotPoint.JPG To avoid any confusion over which layer is the original "route-layer", this is one layer that should not be renamed or moved from the top position.


While all layers are equal, the "route-layer" is special.

Stop.PNG Track objects, such as signals, junctions and track signs, cannot be placed in any layer that is above the layer containing the track that they are attached to. If the route-layer is used for all the track and track objects and this layer is left as the top layer then this will never be a problem.


PencilTips.PNG It is recommended that the following objects should be placed in the route-layer:-
  • Track and interactive industries with track
  • Track infrastructure (turntables, bridges, tunnels, etc)
  • Signals and track signs (speed limits, warnings, distance, etc)
  • Junctions and switches

..and that the "route-layer" be placed at the top of the Route Layers Group.

[edit] The Session Layers Group

DotPoint.JPG The Session Layers Group should be used for everything that will only be seen in the currently loaded Session.

If you are creating more than one Session based around a particular Route, then you will probably make use of the Session Layers.

NotePad.PNG Notes:

Session Layers can contain:-

  • Scenery objects that will only appear in one or some of the Sessions.
For example: If you have placed human figures and equipment for a track work crew alongside the track and want them to be seen in a daylight Session but not in a night Session, then place them in one of the Session Layers of the daylight Session only. Likewise, station staff holding lamps would be placed in one of the Session Layers of the night Session only.
  • Consists used in a Session.
PencilTips.PNG
  • It is a good idea to place ALL the consists in the same Session Layer and using a Session Layer for ALL consists is the recommended method for Trainz Plus. Particularly if they are going to be coupled together during the running of a Session
  • When you first save a Session, give it a distinctive and informative name. Avoid the temptation to use Default as the name of your Session as you can easily end up with several Sessions under the same Route all called Default


  Top Next Up Next Down Bottom

[edit] Adding Objects To Layers

When an object (such as a scenery item, consist, track or track object) is added to the layout it is automatically placed in the currently Active Layer. Unfortunately, Trainz does not indicate which layer is the Active Layer unless you open the Layers Tool to look. This can lead to objects being placed into the wrong layers and while these objects can later be moved to another layer (see the section PageLink.PNG Moving Objects To Other Layers below) it would be better to correctly set the Active Layer first.

PencilTips.PNG It is good practice to LOCK ALL LAYERS that you are not currently editing. This will avoid the all too common problem of accidentally adding objects to the wrong layer.


DotPoint.JPG You cannot add objects to a layer that is LOCKED.

If you attempt to add a scenery object to a locked layer you will receive the following message:-

LayersRouteTreesActiveLockedError.JPG
  • Click the Tick.PNG icon to UNLOCK the layer.


DotPoint.JPG When adding track objects (signals, speed signs, etc) to a track, the objects being added must be in the same layer as the track or in a layer below the track layer. For more information, see the section PageLink.PNG The "route-layer" above.


NotePad.PNG Notes:

There are many features of Trainz Routes and Sessions that are NOT stored in layers. In some cases while the objects themselves may be placed in layers, their settings or properties are not. These include:-

  • landforms
  • textures
  • TurfFX and Clutter ground effects
  • trackside camera settings
  • weather conditions
  • time of day
  • session rules and driver commands
  • signal and junctions settings
  • rolling stock loads
  • industry settings
  • portal settings
  • passenger station settings
  • navigation points
  • interlocking tower settings BugMini.PNG
DotPoint.JPG Landforms, textures, effect layers (TurfFX, Clutter) and some Environment settings are saved as part of the Route while all the others are saved as part of a Session
DotPoint.JPG When you enter or edit the name of a route layer scenery object, such as a station name board, that change will be treated as a change to the Session but the new or edited name will still be saved as a property of the scenery object in a Route layer. When you save, you will be given the option of saving the Session as well as the Route. You can ignore the offer to save the Session if you have not edited any objects in a Session Layer, the Session Layers themselves (e.g. moved, merged, deleted or renamed) or other Session properties (e.g. commodity levels or loads).  If uncertain, always save the Session 
Bug.png A bug has been reported in the Interlocking Towers (and the Enhanced Interlocking Towers) where the path and settings are initially saved in the Route but any later edits and changes are then saved in the Session. The workaround for this is to always load the Session when working with IT and EIT assets. This problem has not been resolved in the latest versions of Trainz.


  Top Next Up Next Down Bottom

[edit] Deleting Objects From Layers

PencilTips.PNG
  • It is good practice to LOCK ALL LAYERS that you are not currently editing. This will avoid the all too common problem of accidentally deleting objects from the wrong layer.
  • An exception to this "good practice" is when managing rulers. Unless you have used a dedicated ruler layer for all rulers it can be difficult to discover which layer contains a particular ruler. If rulers are not added to a dedicated layer then you will need to unlock and unhide all the layers first before you can use the Delete Ruler tool.


DotPoint.JPG You cannot delete objects from a layer that is LOCKED.


Unfortunately Trainz does not give you a warning message when you attempt to delete an object from a locked layer, the object just refuses to be deleted.

PencilTips.PNG If you cannot delete an object then check:-
  • that the objects layer and bound layer (if it has been set) are unlocked
  • that you are using the correct delete tool (e.g. such as attempting to delete a tree with the spline, signal or rolling stock delete tool) - it happens!


  Top Next Up Next Down Bottom

[edit] Moving Objects To Other Layers

LayersObjectProperties.JPG
Steps.PNG Steps:

To move individual objects from one layer to another:-

  1. Open the Properties window (? button in the Object Tools) of the object to be moved
  2. Click the Layer or one of the scroll buttons
  3. Select the new layer
  4. Click the Tick.PNG icon


DotPoint.JPG You can move an object into and out of a locked layer
DotPoint.JPG Multiple scenery objects can be moved to another layer by using the Bulk Asset Update/Replacement tool from the Surveyor Main Menu
DotPoint.JPG Rulers cannot be moved to a different layer because they do not have a properties window. If it is necessary to move a ruler to another layer, it must be manually created in the desired layer (using the Add Ruler tool), then the pre-existing ruler must be deleted (using the Delete Ruler tool).
LayersObjectPropertiesChangeLayer.JPG


  Top Next Up Next Down Bottom

[edit] The Bound Layer

This is a little used and probably little understood layer feature. It allows you to attach an object to two different layers so it can have the properties (locked/unlocked and show/hide) of both layers. The bound layer was introduced as a development tool, its sole use is as a tool in the building of routes and sessions.

DotPoint.JPG An object will be LOCKED and cannot be deleted or moved if its layer OR its bound layer is locked.
DotPoint.JPG An object will be HIDDEN if its layer OR its bound layer is hidden.
DotPoint.JPG Rulers cannot be bound to another layer.


Some applications:-

  • Temporarily locking an object by binding it to a locked layer while allowing other objects in the same unlocked layer to be moved or deleted. A simple but very effective development technique is to create a Route layer called "Locked" and then lock it. If you need to temporarily stop an object from being deleted or moved then it can be bound to the "Locked" layer.
  • Temporarily hiding an object by binding it to a hidden layer (this will require the hidden layer to be made visible so the object can be unbound).
LayersBoundLayer.JPG

Steps.PNG Steps:

In the Properties Window of an object:-

  1. Click the Bound Layer box or one of its scroll buttons
  2. Select the layer to be used as the Bound Layer for the object (an object cannot be bound to its own layer)
The effects of the binding can be reversed by setting the Bound Layer back to <none>.


DotPoint.JPG When a layer is deleted any objects bound to that layer will have their Bound Layer reset to <none>


PencilTips.PNG If you are going to be working with multiple objects that will be bound to a locked or hidden layer then a simple strategy is to:-
  • Create a new empty layer called "Locked" or "Hidden" and lock or hide that layer, according to your needs
  • Bind the individual objects to that layer as required
  • When editing, testing or whatever you are doing has been completed simply delete the new layer. All objects that have been bound to that layer will have their Bound Layer property reset to none so the hidden objects will reappear and the locked objects will be unlocked.


PencilTips.PNG If you need to remove an object from a route but cannot alter the route (e.g. it is payware or under another users kuid) then create a new hidden session layer and change the bound layer of the object to the hidden layer. This will be treated as a change to the session only and Trainz will not ask you to save the route as well as the session.


  Top Next Up Next Down Bottom

[edit] Layers in Driver Mode

During the running of a Session in Driver Mode visible layers can be hidden and invisible layers revealled according to the events that occur during the Session.

LayersDriveShow.JPGLayersDriveHide.JPG The two Driver Mode scenes shown on the left illustrate this feature.
  • In the first image on the left, all layers are visible
  • In the second image on the left, two of the layers have been hidden
The trigger for this change was the arrival of a train at the platform.

This effect could be achieved in two different ways:-

  1. A Driver Command - specific to a particular driver, or
  2. A Session Rule - specific to a particular driver, consist, or any driver/consist

[edit] Using a Driver Command

The driver command WikiLink.PNG Layer Control hides and shows named layers.
LayerControlExample.png

[edit] Using Session Rules


RulesWiki.PNG Rules Used:


Screenshot.PNG Session Editor Screenshot:

LayersDriveHideRules.JPG


Explanation.PNG Description:

In this example:-

  • The Trackside Check Rule is triggered when a specific train comes to a stop at a trackmark. This then executes the following rules in order:-
    • The Show/Hide Layer Rule is used to hide the layer named "People". Four passengers (three standing and one seated) are hidden.
    • The Show/Hide Layer Rule is used to hide the layer named "CNJCartsFull". The boxes and mail bags on the three platform trolleys are hidden.
    • The Message Popup Rule is used to place a message on the screen informing the player that the passengers and mail have been loaded.


  Top Next Up    


[edit] Trainz Wiki

TrainzWiki.png

More Tutorials and Guides to Using Trainz


This page was created by Trainz user pware in June 2018 and was last updated as shown below.


Personal tools