[resolved] AI drivers not changing turnouts

[martinvk]

In the past, when gave an AI consist a schedule and it approached a turnout set against it, it would slow and stop at the controlling signal, and after a while, if there was no conflict, it would change the turnout in order to continue on its schedule.
Post SP5, they just sit there waiting. If I manually change the turnout, it will then continue.
Did I miss a memo or something?

 

[martinvk]

Hmm, could be something to do with the size of the new route. Over 2000 MB. When I tested on a one board route, all works fine.
I guess it takes a while for the memo to be passed around to all the signals and switches in that large route.

 

[JCitron]

The issue could be more than just the route size. This delay may have something to do with the new TLR because I've noticed the wait as well even on my relatively small Gloucester Terminal Route where there are lots of switches to through in yards and terminals.

I've noticed too that AI drivers tend to be more aggressive with switch control as well. This started when TLR was first introduced.

 

[martinvk]

That will need more investigation. Can TLR be turned on or off or is it always there in the background?
Both routes are in TRS22PE 128487. The small one board test map was created there. The humongous one was created from TransDEM in the previous build just before SP5 was applied. It has relatively few switches, many with long distances between them.

 

[JCitron]

That will need more investigation. Can TLR be turned on or off or is it always there in the background?
Both routes are in TRS22PE 128487. The small one board test map was created there. The humongous one was created from TransDEM in the previous build just before SP5 was applied. It has relatively few switches, many with long distances between them.

I don't think this can be turned off. The code is built-in now even if it's not used.