I just ran my Gloucester Terminal Electric route. I haven't had the opportunity to do much driving if at all for months since I've been working on other projects both in and out of Trainz. In this particular route, I have nearly 2-dozen active AI drivers plus two to four captive AI drivers on a mainline with no interaction with each other. In 122411, like all previous builds, I could drive for hours before I had one particular drive do something off the wall in the typical AI fashion which I need to troubleshoot someday. Usually, I just fix the AI and continue on for another few cycles before the goof up occurs again. In build 123794, after 15 minutes I had AI get "stuck". They were all staring at a signal even though the signals were green or yellow. I CTRL-right-clicked on each one and had the drivers continue schedule which they did without problem except for one. This one driver decided to crossover on to the other mainline causing a fouled mainline due to locked switches. I had to intervene and place him beyond that junction in order to get the operation working again. The other interesting thing I noticed was that there were no messages posted in the message-box regarding getting stuck. It was as if they finished their schedules and that was that.I am a Trains + user running build 123794. This build broke many of my routes. I have had to add many more track marks to prevent AI controlled trains from stopping, or worse, reversing direction. I was one of the first people to mention that its almost like a trailing train cannot see "through" a preceding train to see its next track mark. In most cases of a malfunctioning AI train this hypothesis "explains" why I am having to add so many more track marks. Things ran fine in build 122411, the previous commercial release. Build 123794 broke a lot of stuff for me. I should comment that I have no assets showing errors and have done numerous complete data rebuilds to see if that solves any of my problems - it doesn't. I am also using the "drive to " commands.
I'll take a look at the OPs route and session tomorrow, but I have a feeling he's on to something as well. I wonder if part of this is due to the new TLR thing the developers are working on. In the process of implementing this new feature, they broke something else.