But I can't tell if I am even in 'Streaming' mode, how do you know, or as a casual user, should I know? There is a good discussion on it here..
https://forums.auran.com/trainz/showthread.php?148163-Asynchronous-Route-Streaming
I think the idea is that you won't know. When you load a route, if you have streaming enabled and the route is minimum Trainz Build 4.6, instead of the whole route loading in RAM memory, it will only load the local area you are viewing.
As you move around the route, Trainz will stream in more of the route from your hard-drive. Crucially it will also unload assets in areas you have moved away from.... but you shouldn't see any of this.
(It should also load assets near moving trains anywhere on the route). The idea is it makes loading a route faster because its not having to load all of it.
Would a casual user that downloads my route created in TANE, that has the older ATLS Controller V2.7 in it, and they have in there system, the newer controller V3, and is streaming, then will they get this problem? That me, as the route builder, is not going to be able to see?
It depends when you built your route in Tane. The last couple of Controller updates made the asset AutoName. So long as you didn't delete that name it should be fine.
However, any routes using ATLS built before the last month or so will probably have blank Controller names. As a route builder, please check this and give them a name before you upload your route.
Since a build 4.5 won't stream, they should be OK not listing assets, (ref instructions in the Controller asset).
A problem might occur if you have uploaded a build 4.6 route/session (TRS19) built before ATLS V3. Then ATLS assets will need to 'list'. See
www.boatztrainz.co.uk/trs19.html
[/QUOTE]
That's interesting how buildable items can't be tracked in the code. I wonder if it's due to too many possibilities therefore too many parts. I noticed the renaming of track-objects and this is most obvious with permissive signals - those that have that small black sign under the signal to place in a name or number. These now have the signal name/number on what used to be a blank sign.
Hi John,
Its not that Buildables can't be tracked. They are in the same boat as the trackside items. The problem is that the old calls to find an asset are no longer reliable. That's because an asset you are looking for may not be loaded, (not streamed).
New calls have been introduced to track assets even if they are unloaded, and to force a load if necessary. But these new calls require an asset to be named.
Trackside items now fully autoname so they will always have a name but Buildable assets have not been given this facility so they
can remain blank. With the Controller, I have to ensure it is loaded. When a train hits a Trigger it will call for the Controller to load. Since the Controller
might be unloaded I need to find it by the new calls..... so it needs a name.
Not so important with the Slaves as they will get sent messages only if they
are loaded.
I like your Controller-slave because that nifty little asset eliminates the extra clicking on the controller and I can do most of my clicks with the track-object properties.
Thanks, I wish I had made this earlier. It's so much easier to set up for Level (Grade) Crossing control and with it having the Slave built in, its less to do too![/QUOTE]