How to Use Layers
Line 1,725: | Line 1,725: | ||
<table cellpadding=2 bgcolor=#ffffb0 width=1000> | <table cellpadding=2 bgcolor=#ffffb0 width=1000> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[file:NotePad.PNG|link=]]</td> | + | <td width=25>[[file:NotePad.PNG|link=]]</td> |
<td><span style="font-size: 17px;">'''Notes:'''</span><br> | <td><span style="font-size: 17px;">'''Notes:'''</span><br> | ||
---- | ---- | ||
− | + | <table> | |
− | :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). | + | <tr valign="top"> |
− | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> | |
− | :Many creators build multiple Sessions for each Route and rely on the Session Layers to create the differences between their Sessions. | + | <td>'''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)</td> | |
− | + | </tr> | |
− | + | <tr valign="top"> | |
− | + | <td>[[image:DotPoint.JPG|10px|link=]]</td> | |
− | + | <td>'''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</td> | |
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>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:- | ||
+ | <table> | ||
+ | <tr valign="top"> | ||
+ | <td width=10>[[image:RedDot10x10.png|link=]]</td> | ||
+ | <td>junction switches - the left/right switch direction is stored in the Session (but the '''default''' switch direction is stored in the Route)</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:RedDot10x10.png|link=]]</td> | ||
+ | <td>industries - the commodities and quantities loaded/unloaded are stored in the Session</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:RedDot10x10.png|link=]]</td> | ||
+ | <td>industry enabled wagons - the commodities and quantities carried are stored in the Session</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:RedDot10x10.png|link=]]</td> | ||
+ | <td>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)</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:RedDot10x10.png|link=]]</td> | ||
+ | <td>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> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 1,747: | Line 1,776: | ||
<td><span style="font-size: 17px; font-weight: 700;">TRS19 Platinum Edition, Trainz Plus, TRS22 Notes:</span><br> | <td><span style="font-size: 17px; font-weight: 700;">TRS19 Platinum Edition, Trainz Plus, TRS22 Notes:</span><br> | ||
---- | ---- | ||
− | + | <table> | |
− | + | <tr valign="top"> | |
− | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> | |
− | 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> | + | <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 have the '''Unified Driver Surveyor''' Interface, placing a train in a route layer after switching from Driver to Surveyor can cause problems. For example:- |
+ | <table> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:RedDot10x10.png|link=]]</td> | ||
+ | <td>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</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>Recent experiments using the '''Unified Driver Surveyor''' Interface 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''' Interface</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td colspan=2>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> | ||
+ | </table> | ||
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 1,761: | Line 1,807: | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | <br> | ||
<table width=1000> | <table width=1000> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>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:- | <td>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:- | ||
− | + | <table> | |
− | + | <tr valign="top"> | |
− | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> | |
− | + | <td>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</td> | |
− | + | </tr> | |
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>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</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>'''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</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>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</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>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</td> | ||
+ | </tr> | ||
+ | </table> | ||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | <br> | |
<table bgcolor=#000000> | <table bgcolor=#000000> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 1,780: | Line 1,844: | ||
<td>[[file:PencilTips.PNG|link=]]</td> | <td>[[file:PencilTips.PNG|link=]]</td> | ||
<td> | <td> | ||
− | + | <table> | |
− | + | <tr valign="top"> | |
+ | <td width=10>[[image:DotPoint.JPG|10px|link=]]</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</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <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> | </td> | ||
</tr> | </tr> | ||
Line 1,788: | Line 1,860: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | <br> | |
===The "route-layer"=== | ===The "route-layer"=== | ||
Line 1,821: | Line 1,893: | ||
<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''':- | ||
− | + | <table> | |
− | + | <tr valign="top"> | |
− | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> | |
− | + | <td>Track and interactive industries with track</td> | |
− | ..and that the "route-layer" be placed at the top of the '''Route Layers Group''' | + | </tr> |
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>Track infrastructure (turntables, bridges, tunnels, etc)</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>Signals and track signs (speed limits, warnings, distance, etc)</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>Junctions and switches</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td colspan=2>..and that the "route-layer" be placed at the top of the '''Route Layers Group'''</td> | ||
+ | </tr> | ||
+ | </table> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 1,841: | Line 1,929: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | <br> | |
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 | + | <table width=1000 bgcolor=#000000 cellpadding=2> |
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td> |
− | <td><span style="font-size: 17px;"> | + | <table width=996 bgcolor=#ffffb0 cellpadding=2> |
+ | <tr valign="top"> | ||
+ | <td> | ||
+ | <table> | ||
+ | <tr valign="top"> | ||
+ | <td width=25>[[image:NotePad.PNG|link=]]</td> | ||
+ | <td><span style="font-size: 17px; font-weight: 700;">Notes:'''</span><br> | ||
---- | ---- | ||
Session Layers can contain:- | Session Layers can contain:- | ||
− | + | <table> | |
− | :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 | + | <tr valign="top"> |
− | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> | |
− | </td> | + | <td>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</td> | ||
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> |
− | <table bgcolor=#000000> | + | <td>Consists used in a Session</td> |
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <table width=1000 bgcolor=#000000> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td> | ||
− | <table bgcolor=#ffffe0> | + | <table width=996 bgcolor=#ffffe0> |
<tr valign="top"> | <tr valign="top"> | ||
<td>[[file:PencilTips.PNG|link=]]</td> | <td>[[file:PencilTips.PNG|link=]]</td> | ||
<td> | <td> | ||
− | + | <table> | |
− | + | <tr valign="top"> | |
− | </td> | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> |
+ | <td>'''It is a good idea to place ALL the consists in the same Session Layer and this is strongly <u>recommended</u> for Trainz Plus and TRS22 which have the UDS interface'''. It is also important if different consists are going to be coupled together during the running of a Session</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <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 all called '''Default'''</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 1,879: | Line 1,992: | ||
===The "session-layer"=== | ===The "session-layer"=== | ||
− | An empty '''session-layer''' will be automatically created when you:- | + | <table width=1000> |
− | + | <tr valign="top"> | |
− | + | <td colspan=2>An empty '''session-layer''' will be automatically created when you:-</td> | |
− | If you add anything to the '''session-layer''' or add new layers to the '''Session Layers Group''' and do not save the session before you exit from '''Trainz''' then these changes will be lost. | + | </tr> |
+ | <tr valign="top"> | ||
+ | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>load a route without also loading a session, or</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>create a new route</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td colspan=2>If you add anything to the '''session-layer''' or add new layers to the '''Session Layers Group''' and do not save the session before you exit from '''Trainz''' then these changes will be lost.</td> | ||
+ | </tr> | ||
+ | </table> | ||
<br> | <br> | ||
<table> <!-- BEGIN Nav Buttons Table --> | <table> <!-- BEGIN Nav Buttons Table --> | ||
Line 2,001: | Line 2,126: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>Some applications:- | <td>Some applications:- | ||
− | + | <table> | |
− | + | <tr valign="top"> | |
+ | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>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</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td>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)</td> | ||
+ | </tr> | ||
+ | </table> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 2,017: | Line 2,150: | ||
<td>[[file:PencilTips.PNG|link=]]</td> | <td>[[file:PencilTips.PNG|link=]]</td> | ||
<td>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:- | <td>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 | + | <table bgcolor=#ffffff cellpadding=2> |
− | + | <tr valign="top"> | |
− | + | <td colspan=2><span style="font-weight: 700; font-size: 15px;">Steps:</span> To use a bound layer:-</td> | |
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td width=25>[[image:DotPoint1.JPG|link=]]</td> | ||
+ | <td>Create a new empty layer called "Locked" or "Hidden" and lock or hide that layer, according to your needs</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint2.JPG|link=]]</td> | ||
+ | <td>Bind the individual objects to that layer as required</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint3.JPG|link=]]</td> | ||
+ | <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> | ||
+ | </table> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 2,027: | Line 2,174: | ||
</table> | </table> | ||
<br> | <br> | ||
− | |||
<table bgcolor=#000000 width=1000> | <table bgcolor=#000000 width=1000> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 2,043: | Line 2,189: | ||
<br> | <br> | ||
− | =='''Setting the Bound Layer in Surveyor Classic (S10)'''== | + | =='''Setting an Object to the Bound Layer in Surveyor Classic (S10)'''== |
<table width=1000> | <table width=1000> | ||
Line 2,081: | Line 2,227: | ||
<br> | <br> | ||
− | =='''<span style="color: white; background-color: blue;"> Setting the Bound Layer in Surveyor 2.0 (S20) </span>'''== | + | =='''<span style="color: white; background-color: blue;"> Setting an Object to the Bound Layer in Surveyor 2.0 (S20) </span>'''== |
<table width=1000 bgcolor=#000000 cellpadding=2> | <table width=1000 bgcolor=#000000 cellpadding=2> | ||
Line 2,098: | Line 2,244: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[image:BindingLayerSet_S20.png|link=|alt=Set Binding]]</td> | <td>[[image:BindingLayerSet_S20.png|link=|alt=Set Binding]]</td> | ||
− | <td><br> | + | <td> |
− | <table cellpadding=2 bgcolor=#ffffff> | + | <br> |
− | <tr> | + | <table bgcolor=#000000 cellpadding=2> |
− | <td colspan= | + | <tr valign="top"> |
− | + | <td> | |
+ | <table bgcolor=#ffffff cellpadding=2> | ||
+ | <tr valign="top"> | ||
+ | <td colspan=2><span style="font-weight: 700; font-size: 15px;">Steps:</span> To set the bound layer in '''Surveyor 2.0''':-</td> | ||
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td | + | <td colspan=2>Select an object, or a group of objects, using either the '''Free Move Tool''' or the '''Fine Adjustment Tool'''. In the '''Info Palette''' of the object (or the last selected object):-</td> |
− | + | ||
− | Select an object using either the '''Free Move Tool''' or the '''Fine Adjustment Tool | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
− | <tr> | + | <tr valign="top"> |
− | <td | + | <td width=25>[[image:DotPoint1.JPG|link=]]</td> |
− | + | <td>Open the '''Layer''' properties of the object</td> | |
</tr> | </tr> | ||
− | </table></td> | + | <tr valign="top"> |
+ | <td>[[image:DotPoint2.JPG|link=]]</td> | ||
+ | <td><span style="font-weight: 700; font-size: 15px; background-color: lightcyan;">Left Click</span> the '''Bounding''' box or one of its '''scroll buttons'''</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint3.JPG|link=]]</td> | ||
+ | <td>Select the layer to be used as the '''Bound Layer''' for the object (an object cannot be bound to its own layer)</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td colspan=2>The effects of the binding can be reversed by setting the '''Bound Layer''' back to '''''<none>'''''</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 2,124: | Line 2,282: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td width=10>[[file:DotPoint.JPG|10px|link=]]</td> | <td width=10>[[file:DotPoint.JPG|10px|link=]]</td> | ||
− | <td> | + | <td>When a layer is deleted any objects bound to that layer will have their '''Bound Layer''' reset to '''<none>'''</td> |
</tr> | </tr> | ||
</table> | </table> | ||
Line 2,145: | Line 2,303: | ||
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. | 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. | ||
+ | <table width=1000> | ||
+ | <tr valign="top"> | ||
+ | <td width=320>[[file:LayersDriveShow.JPG|link=]]</td> | ||
+ | <td width=320>[[file:LayersDriveHide.JPG|link=]]</td> | ||
+ | <td>The two '''Driver Mode''' scenes shown on the left illustrate this feature. | ||
<table> | <table> | ||
<tr valign="top"> | <tr valign="top"> | ||
− | <td>[[ | + | <td width=10>[[image:DotPoint.JPG|10px|link=]]</td> |
− | <td> | + | <td>In the first image on the left, all layers are visible</td> |
− | + | </tr> | |
− | + | <tr valign="top"> | |
− | + | <td>[[image:DotPoint.JPG|10px|link=]]</td> | |
− | The trigger for this change was the arrival of a train at the platform.</td> | + | <td>In the second image on the left, two of the layers (containing the passengers and the trolley loads) have been hidden</td> |
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint.JPG|10px|link=]]</td> | ||
+ | <td colspan=2>The trigger for this change was the arrival of a train at the platform.</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <br> | ||
+ | <table> | ||
+ | <tr valign="top"> | ||
+ | <td colspan=2>This effect could be achieved in two different ways:-</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td width=25>[[image:Ablue.png|link=]]</td> | ||
+ | <td>'''A Driver Command''' - specific to a particular driver, or</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:Bblue.png|link=]]</td> | ||
+ | <td>'''A Session Rule''' - specific to a particular driver, consist, or any driver/consist</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | |||
<br> | <br> | ||
− | |||
=='''Using a Driver Command'''== | =='''Using a Driver Command'''== | ||
The driver command [[file:WikiLink.PNG|link=]] '''[[Driver_Commands_List#Layer_Control|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> | ||
Line 2,198: | Line 2,377: | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | In this example:- | + | |
− | + | <table> | |
− | + | <tr valign="top"> | |
− | + | <td colspan=2>In this example:-</td> | |
− | + | </tr> | |
+ | <tr valign="top"> | ||
+ | <td>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:- | ||
+ | <table> | ||
+ | <tr valign="top"> | ||
+ | <td width=25>[[image:DotPoint1.JPG|link=]]</td> | ||
+ | <td>The '''Show/Hide Layer Rule''' is used to hide the layer named "People". Four passengers (three standing and one seated) are hidden</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint2.JPG|link=]]</td> | ||
+ | <td>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</td> | ||
+ | </tr> | ||
+ | <tr valign="top"> | ||
+ | <td>[[image:DotPoint3.JPG|link=]]</td> | ||
+ | <td>The '''Message Popup Rule''' is used to place a message on the screen informing the player that the passengers and mail have been loaded</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
<br> | <br> | ||
<table> <!-- BEGIN Nav Buttons Table --> | <table> <!-- BEGIN Nav Buttons Table --> |
Revision as of 18:26, 12 September 2023
The information in this Wiki Page applies to TANE, TRS19, Trainz Plus (in Surveyor Classic mode) and TRS22.
What Are Layers?
Layers can contain any objects, visible and invisible, that can be placed into a layout in Surveyor Classic using the Object, Track and Train tools or using the Placement Tool in Surveyor 2.0. The layers and their contents can be hidden from view (in both Surveyor and in Driver) 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. |
|
Almost all of what you will see in a Trainz World will be found in layers, and mostly in the Route Layers and Session Layers.
Route Layers will contain the objects that will appear in ALL the sessions created using the current route | |
Session Layers will contain the objects that will only appear in the current session |
The Layers Tool in Surveyor Classic (S10)
Left Click the Layers Tool (or press F6 ) to open up its properties. |
|
Loading a Route and Loading a Session (S10) |
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. |
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.
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 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.
|
|
Creating a New Route (S10) |
|
The "Active Layer" (S10) |
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 a Left Click on the name of another layer. |
|
|
Adding a New Layer (S10) |
Left Click the Add Button |
An Add layer dialogue window will appear.
|
Deleting a Layer (S10) |
|
Select the layer to be deleted and Left Click on the Delete Button. If you don't select a layer to delete then Trainz will select the current Active Layer. |
|
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 (S10) |
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. |
|
Select the layer to be merged into another layer and Left Click the Merge button. If you don't select a layer to merge then Trainz will select the current Active Layer. |
|
The layer merge dialogue window will appear as shown below:-
|
Locking Layers (S10) |
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 (S10)
The objects in a LOCKED layer cannot be moved (around the layout) or deleted but they can be moved to other layers. |
To LOCK an individual layer, Left Click on the Open Padlock icon next to its name. The layer being locked does not have to be the current Active Layer.
|
If you attempt to add a scenery object to a locked layer you will receive the following message:-
Left Click on the icon to UNLOCK the layer Left Click on the icon to cancel the object placement |
Locking ALL Route Layers (S10)
Left Click on 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 a Left Click on the Lock Button again.
Moving a Layer (S10) |
Main Points: | |||||
Layers can be moved up or down
|
|||||
Track Objects (signals, switches, etc) should be in the same layer or in a layer below the Track layer |
|
In the example shown below a layer created in the Route Layers Group is being moved into the Session Layers Group.
|
Hiding Layers (S10) |
To hide or show a layer Left Click the Eye Icon next to its name.
In the image shown left the two trees are in different Route Layers and all the layers have their Eye icons open (set to Show) | ||||||||
In the image shown left the Trees layer has its Eye icon closed (set to Hide)
|
Adding Objects To Layers (S10) |
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, Surveyor Classic (S10) 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. |
|
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:-
Left Click on the icon to UNLOCK the layer Left Click on the icon to cancel the addition |
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. |
|
Deleting Objects From Layers (S10) |
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.
|
Moving Objects To Other Layers (S10) |
|
|
The Layers Palette in Surveyor 2.0 (S20)
|
Layers are found in the Layers Palette.
|
|
Lock the Route Layer Group (S20)
All the layers in the Route Layer Group can be locked against accidental alteration.
|
Open a Layer Group (S20)
To the left of each Layer Group name is a small arrow. Left Click on the arrow to open up the group.
The image on the left shows that the Session Layers Group is open and its individual layers are now displayed. To close or minimise the group Left Click on the arrow again.
|
Add a New Layer (S20)
You cannot create new layer groups but you can add new layers to a existing group. |
Renaming a Layer (S20)
Right Click on a layer name and select Rename Layer.. from the popup menu. You will be asked to enter a new name for the layer. |
Deleting a Layer (S20)
Right Click on a layer name and select Delete Layer from the popup menu. You will be given a warning that you are about to delete a layer.
|
Moving a Layer (S20)
Layers can be individually moved up and down within the same layer group or between the Route Layers Group and the Session Layers Group.
|
Left Click on a layer name and, while holding the left button down, drag the layer up or down to its new position. | |
depending on the contents of the layer, the process may take some time. You will be shown a progress bar during the move operation | |
the move can be reversed (after it has completed) by using the Ctrl Z keys |
Merging a Layer (S20)
Right Click on a layer name and select Merge Layer Up from the popup menu.
|
Hiding Layers (S20)
Each individual layer has an Eye icon that controls the visible state of that layer. Left Click on the icon to toggle its state between visible and hidden.
|
Locking Layers (S20)
Each individual layer has a Padlock icon that controls the state ( Locked or Unlocked) of that layer. Left Click on the icon to toggle its state between Locked and Unlocked.
|
|
Setting the Active Layer (S20)
the Active Layer is the layer where new objects will be automatically added when using the Placement Tool. The active layer is shown in the palette with its name on a blue background. In the image on the left the Rail Workers layer is the current Active Layer. The name of the current Active Layer is also shown in the Layer Palette Title Bar. To set a new Active Layer, Double Left Click on a layer name. |
Move an Object to a New Layer (S20)
The Info Palette will show the layer assigned to the currently selected object. An object is selected by using the Free Move Tool (the S key) or the Fine Adjustment Tool (the D key) found in the Tools Palette.
|
||||||||||
|
|
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 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? |
Notes:
|
TRS19 Platinum Edition, Trainz Plus, TRS22 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:-
|
|
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.
|
|
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.
|
|
The "session-layer"
An empty session-layer will be automatically created when you:- | |
load a route without also loading a session, or | |
create a new route | |
If you add anything to the session-layer or add new layers to the Session Layers Group and do not save the session before you exit from Trainz then these changes will be lost. |
The Bound Layer
In Trainz Plus and TRS22 the Bound Layer is often referred to as the Binding 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/binding 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/binding layer is locked. | |
An object will be HIDDEN if its layer OR its bound/binding layer is hidden. | |
Rulers cannot be bound to another layer. |
|
|
|
|
|
Setting an Object to the Bound Layer in Surveyor Classic (S10)
|
When a layer is deleted any objects bound to that layer will have their Bound Layer reset to <none> |
Setting an Object to the Bound Layer in Surveyor 2.0 (S20)
|
|
When a layer is deleted any objects bound to that layer will have their Bound Layer reset to <none> |
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 in order:-
|
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.