Auto drive not able to resolve path

[RobWed]

I was almost successful in building an automated session in Schwaninger Land. The only problem, which happened a couple of times, was that the AI seemed to struggle getting switches set to continue the instruction list. Signal at red. Points within range of the AI were set for the right path but one or more points beyond that range were not. After waiting as long as I could manage I flicked the out of range switches. Once the path to the destination was open the signal went to clear and off the train went.

How do I resolve this so my session is fully automated?

 

[pware]

How do I resolve this so my session is fully automated?

That is why we still have real people throwing switches (although these days they could be hundreds of kms away from the switch) in real railroads.

Who knows why the AI struggles to throw a switch that is within visual range - anxiety issues perhaps?

One solution would be to use Track Triggers and Session Rules such as Set Junction Rule and Set Signal Extended Rule to set the switches and signals ahead of the train as it moves around the track - clearing the path so to speak.

See the Trainz Wiki at How_to_Control_Junctions_in_Sessions and How_to_Control_Signals_in_Sessions

 

[RobWed]

Thanks! I'll try all those options.

I've certainly seen a few cognitive issues with the AI. No reason why it couldn't have a few emotional issues as well!

So it's supposed to be able to 'see' further than simply those points it has locked?

 

[pware]

So it's supposed to be able to 'see' further than simply those points it has locked?

The AI will look ahead a very long distance - somewhere around 30km - mainly to check the state of the next signal. Switch conflicts, where one AI grabs control of a switch some distance ahead before a closer AI does, is the most common cause of this issue. But, as you noted, sometimes it is a mystery.

 

[RobWed]

The AI will look ahead a very long distance - somewhere around 30km - mainly to check the state of the next signal. Switch conflicts, where one AI grabs control of a switch some distance ahead before a closer AI does, is the most common cause of this issue. But, as you noted, sometimes it is a mystery.

Well I created a session with just the train I'm trying to route so there is no other AI. I'm thinking the Driver needs to be renamed with a German version of Cleetus or something like that. One other issue I had was the train going to a different industry to the one I sent it to. Same factory, different track. I solved that one by putting a trackmark in the yard before the factory and sending it there first. Makes absolutely no sense to me but it works.

Of course I'm fully cognizant that I'm a complete noob at this so Cleetus could well be me....

 

[pware]

Makes absolutely no sense to me but it works.

Just noticed that title of your thread mentioned "Auto Drive". By that do you mean the "AI" or the actual "AutoDrive" driver command?

The AutoDrive command will obey all speed signs and signals but it will NOT set any switches.

 

[RobWed]

Just noticed that title of your thread mentioned "Auto Drive". By that do you mean the "AI" or the actual "AutoDrive" driver command?

The AutoDrive command will obey all speed signs and signals but it will NOT set any switches.

Oh I meant the AI