TMs and triggers in layers

[Gary_Evans]

What can one accomplish by placing Track marks or triggers in a layer? According to the layers tutorial, TMs & triggers are objects that can be placed in Layers. However, since Track marks and triggers are hidden in Driver what is the advantage of placing and hiding Track marks or triggers in Layers? Just asking.

 

[pitkin]

What can one accomplish by placing Track marks or triggers in a layer? According to the layers tutorial, TMs & triggers are objects that can be placed in Layers. However, since Track marks and triggers are hidden in Driver what is the advantage of placing and hiding Track marks or triggers in Layers? Just asking.

Adding trackmarks to the routes of others without changing the original route.

Using different triggers and trackmarks for different sessions. More triggers etc can mean performance problems, which have been documented many times.

 

[pware]

I place trackmarks and triggers in layers for two reasons:-

1. Better management of assets. Layers allow you to group similar assets (e.g. trees, grasses, trackmarks and triggers), or assets that are part of the same structure (e.g. seats, signage, light posts, etc that are positioned on platforms) so they can be temporarily hidden and/or locked to either get them "out of the way" or prevent accidental changes. When placing trackmarks and triggers in their own layer (or layers) you must make sure that the layers used are not positioned above the track layer in the layer lists.
2. To allow assets to be "session specific", so they only appear in one specific session, by placing them in a session layer instead of a route layer . This also applies to trackmarks and triggers that would only be needed in one session instead of being present in all sessions.