How to Use Layers
m (→Deleting a Layer) |
m (→Route Layers vs Session Layers) |
||
(31 intermediate revisions by 2 users not shown) | |||
Line 49: | Line 49: | ||
==Loading a Route and Loading a Session== | ==Loading a Route and Loading a Session== | ||
− | <table cellpadding="4" bgcolor=#c1e7e7 width="730"> | + | <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 61: | Line 61: | ||
<td>'''If you edit a Session Layer and later load just the Route then those edits will not appear.'''</td> | <td>'''If you edit a Session Layer and later load just the Route then those edits will not appear.'''</td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END top level --> |
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. | 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=#ffffb0> <!-- BEGIN top level --> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:PencilTips.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> | ||
+ | </tr> | ||
+ | </table> <!-- END top level --> | ||
− | <table> | + | <table> <!-- BEGIN top level --> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:LayersToolsRoute.JPG|link=]]</td> | <td>[[file:LayersToolsRoute.JPG|link=]]</td> | ||
Line 71: | Line 77: | ||
<td><br> | <td><br> | ||
*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> | + | <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 81: | Line 87: | ||
</td> | </td> | ||
</tr> | </tr> | ||
− | </table> | + | </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> | + | <table cellpadding="4" bgcolor=#ffffb0> <!-- BEGIN 2nd level --> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:PencilTips.PNG|link=]]</td> | <td>[[file:PencilTips.PNG|link=]]</td> | ||
<td>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 | <td>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 | ||
− | <table> | + | <table> <!-- BEGIN 3rd level --> |
<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> | + | </table> <!-- END 3rd level --> |
</td> | </td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END 2nd level --> |
</td> | </td> | ||
</tr> | </tr> | ||
− | </table> | + | </table> <!-- END top level --> |
<br> | <br> | ||
− | <table cellpadding="4" bgcolor=#fcbcbc> | + | <table cellpadding="4" bgcolor=#fcbcbc> <!-- BEGIN top level --> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:Stop.PNG|link=]]</td> | <td>[[file:Stop.PNG|link=]]</td> | ||
Line 114: | Line 120: | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|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;">'''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> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</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 237: | Line 248: | ||
<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. | ||
+ | *Due to a bug in TANE/TRS19, '''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 is created or it will, eventually, reappear in the '''route-layer'''. | ||
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 280: | Line 294: | ||
<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 | + | *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;"> NOTE: Merge cannot be undone </span> |
− | *Click '''Delete''' to delete the layer and its contents. | + | *Click '''Delete''' to delete the layer and its contents. <span style="background-color: #fcbcbc; font-weight: 700;"> NOTE: Delete cannot be undone </span> |
*Click '''Cancel''' to cancel the delete operation</td> | *Click '''Cancel''' to cancel the delete operation</td> | ||
</tr> | </tr> | ||
Line 416: | Line 430: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | <br> | |
+ | <table cellpadding="4" bgcolor=#fcbcbc> | ||
+ | <tr valign="top"> | ||
+ | <td colspan=2><span style="font-size: 17px;"><b>Warning:</b></span></td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:Stop.PNG|link=]]</td> | ||
+ | <td> | ||
+ | In '''TRS19 SP2''' there can 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. The delay will occur every time a layer is moved. | ||
+ | </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 457: | Line 483: | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | |||
==Hiding Layers== | ==Hiding Layers== | ||
Line 523: | Line 550: | ||
<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;">Trainz Plus and TRS19 Platinum 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 | + | *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'''</td> | *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> | ||
</tr> | </tr> | ||
Line 540: | Line 568: | ||
*'''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. <span style="background-color: red; color: white; font-weight: 700;"> NOTE: </span> 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 cellpadding="4" bgcolor=#ffffb0> | ||
Line 671: | Line 700: | ||
*passenger station settings | *passenger station settings | ||
*navigation points | *navigation points | ||
− | *interlocking tower settings'''^''' | + | *interlocking tower settings '''^''' |
</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'''. | Landforms, textures and trackside cameras are saved as part of the '''Route''' while all the others are saved as part of a '''Session'''. | ||
<br> | <br> | ||
− | '''^''' 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. | + | '''^''' 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. This problem has still not been fixed in '''TRS19 SP2'''. |
</td> | </td> | ||
</tr> | </tr> | ||
Line 690: | Line 719: | ||
<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> | </tr> | ||
</table> | </table> | ||
+ | |||
<br> | <br> | ||
<table cellpadding="4" bgcolor=#c1e7e7> | <table cellpadding="4" bgcolor=#c1e7e7> | ||
Line 749: | Line 781: | ||
<td>[[file:DotPoint.JPG|link=]]</td> | <td>[[file:DotPoint.JPG|link=]]</td> | ||
<td>Multiple scenery objects can be moved to another layer by using the '''Bulk Asset Update/Replacement''' tool from the ''Surveyor Main Menu''</td> | <td>Multiple scenery objects can be moved to another layer by using the '''Bulk Asset Update/Replacement''' tool from the ''Surveyor Main Menu''</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[file:DotPoint.JPG|link=]]</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 775: | Line 811: | ||
<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 797: | Line 837: | ||
#Click the '''Bound Layer''' box or one of its '''scroll buttons''' | #Click the '''Bound Layer''' box or one of its '''scroll buttons''' | ||
#Select the layer to be used as the '''Bound Layer''' for the object (an object cannot be bound to its own layer) | #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>'''''.</td> | The effects of the binding can be reversed by setting the '''Bound Layer''' back to '''''<none>'''''.</td> | ||
</tr> | </tr> | ||
Line 815: | Line 854: | ||
</table> | </table> | ||
<br> | <br> | ||
+ | |||
<table cellpadding="4" bgcolor=#ffffb0> | <table cellpadding="4" bgcolor=#ffffb0> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 833: | Line 873: | ||
</table> | </table> | ||
<br> | <br> | ||
+ | |||
<table width="100%"> | <table width="100%"> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 858: | Line 899: | ||
#'''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> |
Revision as of 19:54, 28 December 2020
The information in this Wiki Page applies to TANE, TRS19 and Trainz Plus.
Contents |
What Are Layers?
In Summary: | ||
Layers are a Surveyor tool that allows you to better manage the objects that are placed in your Trainz World. | ||
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.
The Layers Tool
Loading a Route and Loading a Session
In Summary: | ||
Route Layers are saved with the Route. Session Layers are saved with the Session. | ||
If you edit a Session Layer and later load just the Route then those edits will not appear. |
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.
Until you gain experience and confidence in working with Routes and Sessions, and their layers, the best advice is to always load and edit a Session, not a Route. |
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.
|
WARNING: | |
If you load a ROUTE without a SESSION then only edit the Route Layers | |
If you load a SESSION and edit any Session layers then save the Session | |
When you save a SESSION, give it a distinctive descriptive name (do NOT use Default) |
Creating a New Route
|
The "Active Layer"
In Summary: | |
The Active Layer is the selected (highlighted) layer. | |
When you load the Route only into Surveyor, the first Route layer will be the Active Layer | |
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.
Notes: The Active Layer is the "working layer" which is:-
|
Caution: | |
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 Adding Objects To Layers below for more information. |
Adding a New Layer
Click the Add Button |
An Add layer dialogue window will appear.
|
Deleting a Layer
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. |
Warning: | |
|
If the layer being deleted is empty, then the following dialogue window will appear:-
|
If the layer being deleted is NOT empty, then the following dialogue window will appear:-
|
Merging Layers
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: | |
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. | |
Once layers have been merged they cannot be separated. |
The layer merge dialogue window will appear as shown below:-
|
Locking Layers
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. |
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.
The objects in a LOCKED layer cannot be moved (around the layout) or deleted but they can be moved to other layers. |
|
If you attempt to add a scenery object to a locked layer you will receive the following message:-
|
Locking ALL Route Layers
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: | |
Layers can be moved up or down
|
|
A layer containing track objects (e.g. signals, switches, etc) CANNOT be placed above the layer containing the track |
Warning: | |
In TRS19 SP2 there can 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. The 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.
|
Hiding Layers
To hide or show a layer click the Eye Icon next to its name.
|
||||||
|
Route Layers vs Session Layers
This topic has filled endless threads in the Trainz Forums with arguments raging on both sides.
In Summary: | |
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? |
Notes:
|
Trainz Plus and TRS19 Platinum Notes:
|
The Route Layers Group
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.
|
The "route-layer"
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.
Warning: | |
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. |
It is recommended that the following objects should be placed in the "route-layer":-
|
The Session Layers Group
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.
Notes: Session Layers can contain:-
|
|
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 Moving Objects To Other Layers below) it would be better to correctly set the Active Layer first.
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. |
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:-
|
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 The "route-layer" above. |
Notes: There are many features of Trainz Routes and Sessions that are NOT stored in layers. These include:-
Landforms, textures and trackside cameras are saved as part of the Route while all the others are saved as part of a Session.
|
Deleting Objects From Layers
|
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.
If you cannot delete an object then check:-
|
Moving Objects To Other Layers
|
|||||||||||
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.
An object will be LOCKED and cannot be deleted or moved if its layer OR its bound layer is locked. | |
An object will be HIDDEN if its layer OR its bound layer is hidden. | |
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).
|
When a layer is deleted any objects bound to that layer will have their Bound Layer reset to <none> |
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:-
|
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. |
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.
The two Driver Mode scenes shown on the left illustrate this feature.
|
This effect could be achieved in two different ways:-
- A Driver Command - specific to a particular driver, or
- A Session Rule - specific to a particular driver, consist, or any driver/consist
Using a Driver Command
The driver command Layer Control hides and shows named layers.
Using Session Rules
Rules Used: |
- Trackside Check Rule - to trigger the event
- Show/Hide Layer Rule - to hide layers
- Message Popup Rule - to open a browser window with a message
Session Editor Screenshot: |
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:-
- 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.
Trainz Wiki
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.