ATLS has been updated to work in the Streaming environment of TRS19.
If you are having problems with old routes, here are a few things to check.
If you are having problems with old routes, here are a few things to check.
First,
if you have just updated to V3, make sure that ALL your ATLS assets are
V3. Version 3 works by very different methods so it will not work with previous versions. (There is however some legacy functions buit-in so 3rd party ATLS assets should work for now)
A common problem may be that the Controller used in your Route may not have been named. New assets autoname but
no-name was the default position in previous versions of ATLS. Due to new script procedures in TRS19, assets must
have a name for important functions. The ATLS Controller MUST therefore be named or the system will just not work.
It can be any name you like, (really anything) but make it a unique name. i.e - If you get the 'That Name is in Use' message, choose another name. Controllers are the important assets. Naming Slaves is optional.
Also, ATLS will need to list its active assets before you run the game in Streaming Mode. If you haven't done this, do it now.
First, ensure that TRS19 is set to 'Maximise Compatibility' mode. See Launcher/Trainz Settings/Dev/Compatibility Mode.
Open Surveyor in the session where ATLS channels are saved. ATLS will immediately compile its list. All you have to do is save the session, however, you may have to open an asset or place and delete any asset so Trainz will allow you to save.
You only need to do this once. Any future ATLS assets you place will list automatically.
Note that any blank ATLS Controllers will be ignored by any new Controllers you place. This means you could end up with 2 Controllers on the same Channel so always 'name and save' on your existing route before you do anything else!
Be sure to do this one-time setup in 'Maximise Compatibility' mode. After that you can safely 'Stream Objects'.
Even if everything seems to work immediately you should still 'List Active Assets'. If you do not, problems may occur in Stream Objects mode. As previously mentioned, legacy calls have been built in so third party ATLS assets should still work for now.
Authors of third party ATLS assets should update their script to work through the new ATLS Library as soon as possible.
no-name was the default position in previous versions of ATLS. Due to new script procedures in TRS19, assets must
have a name for important functions. The ATLS Controller MUST therefore be named or the system will just not work.
It can be any name you like, (really anything) but make it a unique name. i.e - If you get the 'That Name is in Use' message, choose another name. Controllers are the important assets. Naming Slaves is optional.
Also, ATLS will need to list its active assets before you run the game in Streaming Mode. If you haven't done this, do it now.
First, ensure that TRS19 is set to 'Maximise Compatibility' mode. See Launcher/Trainz Settings/Dev/Compatibility Mode.
Open Surveyor in the session where ATLS channels are saved. ATLS will immediately compile its list. All you have to do is save the session, however, you may have to open an asset or place and delete any asset so Trainz will allow you to save.
You only need to do this once. Any future ATLS assets you place will list automatically.
Note that any blank ATLS Controllers will be ignored by any new Controllers you place. This means you could end up with 2 Controllers on the same Channel so always 'name and save' on your existing route before you do anything else!
Be sure to do this one-time setup in 'Maximise Compatibility' mode. After that you can safely 'Stream Objects'.
Even if everything seems to work immediately you should still 'List Active Assets'. If you do not, problems may occur in Stream Objects mode. As previously mentioned, legacy calls have been built in so third party ATLS assets should still work for now.
Authors of third party ATLS assets should update their script to work through the new ATLS Library as soon as possible.