How to Use Layers

From TrainzOnline
(Difference between revisions)
Jump to: navigation, search
m (Deleting Objects From Layers)
m
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 -->
 
<table> <!-- BEGIN Nav Buttons Table -->
Line 12: Line 12:
  
 
='''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 59: Line 59:
 
<br>
 
<br>
  
<table bgcolor="black" cellpadding=2>
+
<table bgcolor=#000000 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 82: 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 96: Line 96:
 
</table> <!-- END top level -->
 
</table> <!-- END top level -->
 
<br>
 
<br>
<table cellpadding="4" bgcolor="Aquamarine"> <!-- BEGIN Trainz Wiki Link -->
+
<table cellpadding=4 bgcolor="Aquamarine"> <!-- BEGIN Trainz Wiki Link -->
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[image:LinkWiki.PNG|link=]]</td>
 
<td>[[image:LinkWiki.PNG|link=]]</td>
Line 112: Line 112:
 
<td>[[file:LayersToolsSession.JPG|link=]]</td>
 
<td>[[file:LayersToolsSession.JPG|link=]]</td>
 
<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'''.  
 
<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'''.  
<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 127: Line 127:
 
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 bgcolor="black" cellpadding=2> <!-- BEGIN 2nd level Black Border -->
+
<table bgcolor=#000000 cellpadding=2> <!-- BEGIN 2nd level Black Border -->
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 172: Line 172:
 
</tr>
 
</tr>
 
</table> <!-- END top level -->
 
</table> <!-- END top level -->
 
<!-- END top level -->
 
  
 
==Creating a New Route==
 
==Creating a New Route==
Line 185: Line 183:
 
<td>[[file:LayersNewRoute.JPG|link=]]</td>
 
<td>[[file:LayersNewRoute.JPG|link=]]</td>
 
<td>
 
<td>
<table bgcolor="black" width=604>
+
<table bgcolor=#000000 width=604>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 215: Line 213:
  
 
==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 238: Line 236:
 
<tr valign="top">
 
<tr valign="top">
 
<td width=484>
 
<td width=484>
<table bgcolor="black" width=464>
+
<table bgcolor=#000000 width=464>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 291: Line 289:
 
<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 308: Line 306:
 
</tr>
 
</tr>
 
</table>
 
</table>
<table bgcolor="black" cellpadding=2>
+
<table bgcolor=#000000 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 361: Line 359:
 
<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 387: Line 385:
 
<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 434: Line 432:
 
</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 454: Line 452:
 
<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 478: Line 476:
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:Stop.PNG|link=]]</td>
 
<td>[[file:Stop.PNG|link=]]</td>
<td>In '''TRS19''' (all versions) and '''Trainz Plus''' 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. <span style="color: white; background-color: red; font-weight: 700;">&nbsp;Resist any urge to click the Cancel button&nbsp;</span>. This delay will occur '''every time''' a layer is merged.
+
<td>In '''TRS19''' and later 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. <span style="color: white; background-color: red; font-weight: 700;">&nbsp;Resist any urge to click the Cancel button&nbsp;</span>. This delay will occur '''every time''' a layer is merged.
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 492: Line 490:
 
==Locking Layers==
 
==Locking Layers==
  
<table bgcolor="black" cellpadding=2>
+
<table bgcolor=#000000 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 506: Line 504:
 
</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 516: Line 514:
  
 
'''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 556: Line 554:
  
 
==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 579: Line 577:
 
<td>[[file:Stop.PNG|link=]]</td>
 
<td>[[file:Stop.PNG|link=]]</td>
 
<td>
 
<td>
In '''TRS19''' (all versions) and '''Trainz Plus''' 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. <span style="color: white; background-color: red; font-weight: 700;">&nbsp;Resist any urge to click the Cancel button&nbsp;</span>. This delay will occur '''every time''' a layer is moved.
+
In '''TRS19''' and later 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. <span style="color: white; background-color: red; font-weight: 700;">&nbsp;Resist any urge to click the Cancel button&nbsp;</span>. This delay will occur '''every time''' a layer is moved.
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 593: Line 591:
 
<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 614: Line 612:
 
*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 627: Line 625:
 
</tr>
 
</tr>
 
</table>
 
</table>
 
 
==Hiding Layers==
 
==Hiding Layers==
  
Line 644: Line 641:
 
<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 672: Line 669:
 
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 678: Line 675:
 
<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>
Line 695: Line 692:
 
**industries - the commodities and quantities loaded/unloaded are stored in the Session (but the '''default''' direction is stored in the Route)
 
**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
 
**industry enabled wagons - the commodities and quantities carried are stored in the Session
**consist locations ('''TRS19 Platinum Edition''' and '''Trainz Plus''' only) - this is stored in the Session (unless you need to save their new locations, you can safely ignore the offer to save 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''' and '''Trainz Plus''' only) - while the name is stored in the Route, adding or changing the name is treated as a change to 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 can cause problems. For example:
 
*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:
Line 714: Line 711:
 
<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 727: Line 724:
 
*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.
 
*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 bgcolor="black" cellpadding=2>
+
<table bgcolor=#000000 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 745: Line 742:
 
===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 768: Line 765:
 
</table>
 
</table>
 
<br>
 
<br>
<table bgcolor="black" cellpadding=2>
+
<table bgcolor=#000000 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 788: Line 785:
  
 
==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 797: Line 795:
 
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>
Line 809: Line 807:
 
</tr>
 
</tr>
 
</table>
 
</table>
<table cellpadding="4" bgcolor=#ffffb0>
+
<table cellpadding=4 bgcolor=#ffffb0>
 
<tr valign="top">
 
<tr valign="top">
 
<td>[[file:PencilTips.PNG|link=]]</td>
 
<td>[[file:PencilTips.PNG|link=]]</td>
Line 832: Line 830:
 
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 bgcolor="black" cellpadding=2>
+
<table bgcolor=#000000 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 846: Line 844:
 
</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 861: Line 859:
 
</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 868: Line 866:
 
</table>
 
</table>
 
<br>
 
<br>
<table bgcolor="black" width=1000>
+
<table bgcolor=#000000 width=1000>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 925: Line 923:
  
 
='''Deleting Objects From Layers'''=
 
='''Deleting Objects From Layers'''=
<table bgcolor="black" width=900>
+
<table bgcolor=#000000 width=900>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 941: Line 939:
 
</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 950: Line 948:
 
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>
 
<br>
<table bgcolor="black" width=900>
+
<table bgcolor=#000000 width=900>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 982: Line 980:
 
<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 999: Line 997:
 
</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 1,033: Line 1,031:
 
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 1,056: Line 1,054:
 
<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 1,077: Line 1,075:
 
</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 1,085: Line 1,083:
 
<br>
 
<br>
  
<table bgcolor="black" cellpadding=2>
+
<table bgcolor=#000000 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 1,103: Line 1,101:
 
<br>
 
<br>
  
<table bgcolor="black" cellpadding=2>
+
<table bgcolor=#000000 cellpadding=2>
 
<tr valign="top">
 
<tr valign="top">
 
<td>
 
<td>
Line 1,152: Line 1,150:
 
=='''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 1,163: Line 1,161:
 
*'''[[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 1,176: Line 1,174:
 
</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 1,202: Line 1,200:
  
 
='''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>

Revision as of 17:11, 14 March 2022

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

Contents

  Top   Next Down Bottom

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

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.


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"

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

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.


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.

Deleting a Layer

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 (all versions) and Trainz Plus 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
Stop.PNG WARNING:

Merge and Delete cannot be undone


Merging Layers

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.

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


Stop.PNG In TRS19 and later 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.


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.


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

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.

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

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

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


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.

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.

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

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

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

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

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

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

Using a Driver Command

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

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    


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