What is on each layer?

[martinvk]

I want to validate that each object is on its correct layer. In a smallish map, turning on one layer at a time can show what has been assigned to that layer.
When the map gets too large, many 10's of km, close to 100 km long, this is not really possible, or rather very tedious.
Is is possible to generate a list of objects by layer? Is there another solution?

 

[pware]

There is no rule or method that I know of that will list all objects assigned to a particular layer.

The method I use is the one you described - hiding all the layers in the Layers Palette except the one that is being checked. Or hiding the route-layer and looking for those objects that should be in the route-layer but are still visible.

 

[martinvk]

Was afraid of that. Too bad that so many good ideas are not fully implemented. I know that layers are really good for route designers to keep all the different objects organized but once a route is done, all the layers could be collapsed into one and it wouldn't make a difference if all you're doing is driving. The only exception being if different eras share the same base map so that differences eras would be on different layers.

 

[JCitron]

I suggested some time ago to have the ability to show us what's on an assigned layer. One of the ways is to show the layer as we have now except add a caret, or plus sign to expand the layer to show its contents.

This could go one step further and put check boxes next to the assets when unchecked will move the selected asset back to whatever layer it came from.

Unless I'm doing something wrong, it would be nice if we could move a group of selected assets to a layer. This would be helpful when we need to hide a bunch of trees, for example, in an area because we're placing catenary.

 

[martinvk]

Unless I'm doing something wrong, it would be nice if we could move a group of selected assets to a layer. This would be helpful when we need to hide a bunch of trees, for example, in an area because we're placing catenary.

When I select multiple objects and then click on the Info palette / Layer, if they are on different layers, the box shows a "-", otherwise it shows the current layer and the drop down list shows all the possible layers. Pick one and all the selected objects will be moved to that layer.

 

[JCitron]

When I select multiple objects and then click on the Info palette / Layer, if they are on different layers, the box shows a "-", otherwise it shows the current layer and the drop down list shows all the possible layers. Pick one and all the selected objects will be moved to that layer.

I'll have to give that a try. I knew I must've been doing something wrong. Thanks. The interface should have some way of knowing what layer each item is on even if it's only informational.

 

[pware]

but once a route is done, all the layers could be collapsed into one and it wouldn't make a difference if all you're doing is driving.

Not completely true. There is a Show/Hide Layer Rule and a Layer Control driver command that I often use to show and/or hide different layers during the running of a session to add some novelty.

Some examples:

• for a shunting session I can use the rule/command to show switchmen placed at various locations around the yard
• for a night session, signallers holding lamps at stations
• at a passenger station hiding/showing luggage, passengers, parcels etc after the arrival/departure of a service (see Layers_in_Driver_Mode).

 

[martinvk]

What I meant by the exception above. Same base map with different details. Nice about the Show/Hide Layer Rule to make this more dynamic.

 

[blueodessey]

There is no rule or method that I know of that will list all objects assigned to a particular layer.

The method I use is the one you described - hiding all the layers in the Layers Palette except the one that is being checked. Or hiding the route-layer and looking for those objects that should be in the route-layer but are still visible.

Good Morning Pware,

Thank you for sharing a very valuable lesson, several times over the years, I would get confused about Layer use and visibility?

I never thought about hiding the Route Layer when trying to isolate a Asset Location relative to which Layer it is using.

 

[Williamb73]

I always used layers as a building block for sessions.
Portal, traffic, animations, working industries and portals dispatchers etc. All in the session layer. The route layer was only used in my version for main route construction. Leave the details to each Session Layer.

May be different now, just thought I'd add that.

 

[pware]

Portal, traffic, animations, working industries and portals dispatchers etc. All in the session layer.

My concerns with that list, especially the portals, is that anything placed in a session layer will only be available in that session. I add multiple sessions to each route I create with all the elements that are common to all the sessions placed into various route layers. This is not an issue for inactive scenery items (static cargo on dock platforms, rail workers, etc) which can go into a session layer and only appear in that session. All track, track objects and active industries are always in the base route-layer, this includes portals on the very rare occasions that I use them.

All consists (except those that are purely decorative such as a non operational loco on display in a public park) I place in a session layer as is the recommended method for using the UDS.

 

[JCitron]

My concerns with that list, especially the portals, is that anything placed in a session layer will only be available in that session. I add multiple sessions to each route I create with all the elements that are common to all the sessions placed into various route layers. This is not an issue for inactive scenery items (static cargo on dock platforms, rail workers, etc) which can go into a session layer and only appear in that session. All track, track objects and active industries are always in the base route-layer, this includes portals on the very rare occasions that I use them.

All consists (except those that are purely decorative such as a non operational loco on display in a public park) I place in a session layer as is the recommended method for using the UDS.

This is how I work. All infrastructure assets go on the route layer including portals. Any operations related assets such as trains, consists, and industry configurations, including portals, are all done in the session. I've worked this way since TS12 and before there were layers actually, and I've never run into issues unless I suffered a brain fart and put things in the wrong place.

 

[blueodessey]

I always used layers as a building block for sessions.
Portal, traffic, animations, working industries and portals dispatchers etc. All in the session layer. The route layer was only used in my version for main route construction. Leave the details to each Session Layer.

May be different now, just thought I'd add that.

Agree on that!

Very valid point. Keep Congestion out of the layer if possible.

 

[martinvk]

I do the opposite, keep everything in various route layers, (track layer, road layer, building layer, etc.) Only things that belong to one session and are not shared with other sessions are ever in a session layer.

 

[blueodessey]

I do the opposite, keep everything in various route layers, (track layer, road layer, building layer, etc.) Only things that belong to one session and are not shared with other sessions are ever in a session layer.

Agree Martin,

Best Tools are the ones that adapt to your way of doing things.

 

[martinvk]

One of the best features of Trainz, it goes with the flow of everyone.