Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
What assets in what layers?
- Thread starter CofG509
- Start date
The short answer is no.
The only way that I know of is to do a visual inspection of the layout after hiding the particular layer to see what has vanished.
I can see that such a list can be useful for quickly identifying problems such as objects accidentally assigned to the wrong layers.
I would suggest posting this in the suggestion forum.
The only way that I know of is to do a visual inspection of the layout after hiding the particular layer to see what has vanished.
I can see that such a list can be useful for quickly identifying problems such as objects accidentally assigned to the wrong layers.
I would suggest posting this in the suggestion forum.
The short answer is no.
The only way that I know of is to do a visual inspection of the layout after hiding the particular layer to see what has vanished.
I can see that such a list can be useful for quickly identifying problems such as objects accidentally assigned to the wrong layers.
I would suggest posting this in the suggestion forum.
Thanks. I'll go post it there and hopefully they'll add that feature. Sure would be helpful in moving assets between layers.
Tony_Hilliam
Trainz Plus - enjoy Trainz from just 20 cents a da
Note that technically "assets" aren't in a layer, but each instance of an asset placed in the route is.
So to identify all objects in a layer, you could hide all layers but one, then select the items (using marquee select) and then list them in CM.
Not sure what you want to do next. You could add them to a picklist, but of course an asset could them appear in many picklists (which may work for your purposes or not).
So to identify all objects in a layer, you could hide all layers but one, then select the items (using marquee select) and then list them in CM.
Not sure what you want to do next. You could add them to a picklist, but of course an asset could them appear in many picklists (which may work for your purposes or not).
I think what he is asking, and I also think this would be a handy tool in route/session development, would be something like:-
This option would produce a list of assets (Name, KUID, Type) of all the assets assigned to that layer.
My suggestion anyway.
- Right Mouse Click on a layer in the Layers Palette (currently this opens a menu with "Delete", "Rename", "Merge Up" options - with "Edit" instead of "Merge Up" for Effect layers)
- Select a new option (probably only for non-effect layers) "List Assigned Assets" (or similar)
This option would produce a list of assets (Name, KUID, Type) of all the assets assigned to that layer.
My suggestion anyway.
I think what he is asking, and I also think this would be a handy tool in route/session development, would be something like:-
- Right Mouse Click on a layer in the Layers Palette (currently this opens a menu with "Delete", "Rename", "Merge Up" options - with "Edit" instead of "Merge Up" for Effect layers)
- Select a new option (probably only for non-effect layers) "List Assigned Assets" (or similar)
This option would produce a list of assets (Name, KUID, Type) of all the assets assigned to that layer.
My suggestion anyway.
Yes. This is what I was talking about. Having that feature would make it a lot easier to see and drop assets from one layer to another especially if you only wanted to drag just a few assets but not the whole layer into another.
Tony is correct. Having a list of "assets" used on a layer is useless unless you just want to add them to a pick list.
Let's keep this simple. You place a tree on a layer. That is an instance of the tree object. By placing it on the layer, it acquire certain properties that are unique to only that instance, like location in 3D space, rotation, which layer the instance is on. Place a second tree at a different spot and that instance will have different properties. It will also have a different internal identifier so the game engine can place it correctly when loaded. Each will reference the original object. This is how the bulk replace tool works. It simply changes the reference to a different asset of each instance leaving the location, rotation and layer values untouched.
What you're asking for is a version of the bulk replace tool that is restricted to moving instances of assets from one layer to another layer. You would choose the layer where the erroneously placed instances appear in the tool. Then build a list of the referenced assets to be moved and choose the target layer. The tool simply changes the layer property of each instance to the new layer.
The programming logic would be something like for each referenced asset which has instances on layer A change the layer property to be layer B.
Let's keep this simple. You place a tree on a layer. That is an instance of the tree object. By placing it on the layer, it acquire certain properties that are unique to only that instance, like location in 3D space, rotation, which layer the instance is on. Place a second tree at a different spot and that instance will have different properties. It will also have a different internal identifier so the game engine can place it correctly when loaded. Each will reference the original object. This is how the bulk replace tool works. It simply changes the reference to a different asset of each instance leaving the location, rotation and layer values untouched.
What you're asking for is a version of the bulk replace tool that is restricted to moving instances of assets from one layer to another layer. You would choose the layer where the erroneously placed instances appear in the tool. Then build a list of the referenced assets to be moved and choose the target layer. The tool simply changes the layer property of each instance to the new layer.
The programming logic would be something like for each referenced asset which has instances on layer A change the layer property to be layer B.
Tony is correct. Having a list of "assets" used on a layer is useless unless you just want to add them to a pick list.
Let's keep this simple. You place a tree on a layer. That is an instance of the tree object. By placing it on the layer, it acquire certain properties that are unique to only that instance, like location in 3D space, rotation, which layer the instance is on. Place a second tree at a different spot and that instance will have different properties. It will also have a different internal identifier so the game engine can place it correctly when loaded. Each will reference the original object. This is how the bulk replace tool works. It simply changes the reference to a different asset of each instance leaving the location, rotation and layer values untouched.
What you're asking for is a version of the bulk replace tool that is restricted to moving instances of assets from one layer to another layer. You would choose the layer where the erroneously placed instances appear in the tool. Then build a list of the referenced assets to be moved and choose the target layer. The tool simply changes the layer property of each instance to the new layer.
The programming logic would be something like for each referenced asset which has instances on layer A change the layer property to be layer B.
Wouldn't be useless. If I want to move several assets from one layer but not all of them it would be useful of having a list so you can just grab which assets you want to move from one layer or another without having to go through your route tagging objects to see what layer they're in. Very simple.
Try reading beyond the first sentence of my post. I know what you are asking for and suggested the only way you're going to get it. My way makes use of existing programming with only a slight change to the interface. You are implying that a whole new interface be created.
So being able to drag certain assets from a list from one layer to another would be harder than dragging a whole layer from one to the other?
Yep, it would basically require a rewrite of the layer panel of Classic Surveyor which isn't likely to happen as Surveyor 2.0 is destined to replace it. Now drag and drop might happen in Surveyor 2.0 which is only available to subscribers. It isn't that what you asked for is a bad idea, I happen to like it but N3V is very careful in allocating funds and no changes to Classic Surveyor are going to be made unless they can be done cheaply and also implemented in Trainz Plus as well. Since the bulk replace tool is being worked on in Trainz Plus at the moment due to it not working correctly with Surveyor 2.0 then a simple tweak to add the moving of instances of assets from one layer to the another is maybe something that might get a green light to do. That update could reach TRS22 in a future update before Surveyor 2.0 does.
Similar threads
- Replies
- 4
- Views
- 200
- Replies
- 15
- Views
- 601
- Replies
- 25
- Views
- 551