Why isn't the 2019 version of the ATLS system working in my copy of TRS2019?

janathan

Member
I recently downloaded the 2019 version of the ATLS system and tested it out, but have come across the following problem: Despite replacing all the controllers, slaves, triggers, etc on my routes with the 2019 version, the system won't work consistently. For example, it'll activate for one or two trains, but after that, it'll never activate again unless I restart the route. I ended up having to replace all the crossings with TRC crossings instead. Here are a fer examples:
https://www.youtube.com/watch?v=x95oaaF6MdI&t=4s (with ATLS slaves, controllers, triggers and stoppers)
https://www.youtube.com/watch?v=sTw1VN3yGlY&t=6s (with ATLS slaves, controllers, stoppers and triggers.)
https://www.youtube.com/watch?v=qoz7GZb9Qzs&t=1s (with ATLS slaves, controllers, stoppers and triggers)
https://www.youtube.com/watch?v=HVTid5ZdBnY&t=3s (with ATLS slaves, controllers, stoppers and triggers)
https://www.youtube.com/watch?v=pU2V96rHiDk&t=1136s (after switching to TRC)
https://www.youtube.com/watch?v=jBYeIbaZHjE&t=1151s (after switching to TRC)

Does anyone know why this is happening and how to fix it?
 
One problem I spotted after the controller update is that some slaves have detached the invisible train. This has only happened on a few but it make them inoperative when in driver. If you see the red and green arrow above the slaves the loco has detached.
 
I still can't figure out why the crossings won't activate consistently. I made sure the controllers have names, as well as the slaves, triggers, etc, but they only activate once or twice before not activating again. Sometimes they don't even activate at all. I don't know why. The crossing are set up the way they should be. There shouldn't be any reason why they won't activate. This is really confusing. I can't see any difference in the crossing from when they activate and when they suddenly decide to stop activating.
 
When in driver locate your problem crossing and go into map view. Make sure consists are showing and you should see a consist come and go where the slave is positioned (invisible train) when the crossing is activated and deactivated. If the slave consist does not change then the invisible train is not connected to the slave track and the slave needs to be replaced. Also check that no two ATLS assets have the same names like triggers. If you use the blue code to name them you need to add (a), (b) to them. ATLS1[0,2], ATLS1[0,2](a), ATLS1[0,2](b) and so on.
 
I'm a little bit confused by what you mean. I usually don't name the objects myself. I just use whatever auto-generated name. For example, "ATLS Controller TRS19 1," "ATLS Controller TRS19 2," etc. Is there a naming system I have to use like on the TRC system?
 
If you let the game name the asset then the asset is saved to the session and will work fine. If you want to save the settings to the map you name the asset with the blue code that you see in the top left of the asset properties window. Not all assets auto-generate a name so some ATLS assets need to be named for the latest versions of trainz. The crossings are not named automatically so need a name entered. That's why I always name the asset with the blue code and have to add (?) if a duplicate code name is used.
 
Hi Janathan,

I know of no reason why ATLS should work and then stop working. Unless you have some Triggers which are not activating and the system is missing some of their commands. Another problem may be that an unrelated asset in your Route is causing script exceptions. This could be any asset, but if it does cause an execption, it will zero the ATLS memory, which will cause problems.

To check for exceptions, from launcher click 'Trainz Settings'. In the 'Dev' tab tick 'Show script exception notifications'. Then when you run Trainz, if there is anything causing an exception, the old Red Bug will appear. If you get one, click on it and see if you can trace what's causing it.

I would recommend you use the new Slave trigger or better still the new ATLS Controller/Slave. See the NEW tutorial here - http://www.boatztrainz.co.uk/ATLS5.pdf

Boat

PS - Also check ALL your ATLS assets are named. The latest assets will auto name but ATLS assets placed on a Route in the past will not autoname. You will still need to name them. (Slaves too!)
 
Last edited:
I think the slaves are the culprit. It can't be the controllers because the traffic lights still change. I don't think it's the stoppers because I've had this problem with multiple crossings. I'm pretty sure the triggers work too because in a test, they changed the traffic lights. The problem appears to be the slaves. They sometimes work, but sometimes don't. I'll check for script exceptions.
 
As I previously stated check the invisible train has not detached from the slave asset. If you see a red and green arrow above the slave it has detached.
 
Well it's been nearly a year with no response, so I thought I'd give an update.
I've been using the Slave Triggers instead of the traffic slaves under the "SCENERY" category because they're a little bit more consistent, but though they work on some of my routes, the crossings are a bit iffy. Here's an example video: (https://www.youtube.com/watch?v=Vl9FTjR5KD0)

In that video, I made an ATLS crossing. The first time I tried to use it, it didn't activate. I reset the game, and it worked. I reset the game again later that day, and it failed to activate on three consecutive tries. I then tried to use the driver command to turn on the crossing and it didn't work. I reset the game several more times and it still didn't work.

Eventually after a whole day of constantly resetting the game, it randomly decided to work, and it did consistently on three consecutive occasions, but with a track record like that, I'm far from convinced that I can trust ATLS.
 
Janathan,

Can you PM me with your e-mail address? Maybe you can cdp me your Route and I can run it to see what's going on.

Boat
 
With the help of Deneban, (thanks) I've seen there are a couple of issues with the Slave(TF) and the ATLS Trigger. These might cause occasional errors so they have both been updated.

As I write the Slave(TF) is on the DLS and a new ATLS Trigger should be there any moment.

The new Slave(TF) fixes an issue where it would throw an exception in certain circumstances, (I still recommend using the Slave/Trigger)

The ATLS Trigger has had a modification to its error trapping when Trainz Triggers sometimes post phantom 'enter' messages. They should now all be caught.

Hope these help.

Boat
 
Eventually after a whole day of constantly resetting the game, it randomly decided to work, and it did consistently on three consecutive occasions, but with a track record like that, I'm far from convinced that I can trust ATLS.

Hi Janathan,

When Boat implemented the capture of the phantom "re-enter" messages occuring when departing a trigger, that fixed the symptom you are describing for me, give it a try with his latest ATLS releases. I have also had great performance from his ATLS reset driver command to raise any gates that on rare occasion get left down.

With the help of Deneban, (thanks) ...

Boat

More than thanks returned to you my friend for using my route as your acid test.
 
Back
Top