AI Function Issue

[boleyd]

An engine needs to transit a switch but is halted. There is an active train already claiming that switch, so the engine waits. The claiming engine couples to its target consist and exits the area, releasing the switch (green arrow for waiting engine). However, the engine held, awaiting the switch, never moves. It forgets what it is waiting for. Ran the session two more times and the release of the switch worked and the waiting engine completed its tasks. Will run a few more times to make sure it was a "one-time".

 

[JCitron]

An engine needs to transit a switch but is halted. There is an active train already claiming that switch, so the engine waits. The claiming engine couples to its target consist and exits the area, releasing the switch (green arrow for waiting engine). However, the engine held, awaiting the switch, never moves. It forgets what it is waiting for. Ran the session two more times and the release of the switch worked and the waiting engine completed its tasks. Will run a few more times to make sure it was a "one-time".

I've seen this before and I solved it by putting an invisible signal past the switches to allow the blocking train to create a clear path. The issue is the halted driver looks down the track and still sees the blocking train. The other issue is the blocked train is looking at all possible paths and if there's a lot of junctions, this can cause the driver to look for a very long time or sometimes quit with the "Waiting for Clearence" message.

The way to solve this is to place signals so that the head faces towards the driver that gets blocked to break up the path into smaller parts. Being a yard area, you want to use the invisible signals.

 

[Christopher824]

An engine needs to transit a switch but is halted. There is an active train already claiming that switch, so the engine waits. The claiming engine couples to its target consist and exits the area, releasing the switch (green arrow for waiting engine). However, the engine held, awaiting the switch, never moves. It forgets what it is waiting for. Ran the session two more times and the release of the switch worked and the waiting engine completed its tasks. Will run a few more times to make sure it was a "one-time".

When something gets changed in the session, it may take 2 saves before it saves all of it / lol

I fequently save every thing twice, even the ATLS settings etc.

 

[JCitron]

When something gets changed in the session, it may take 2 saves before it saves all of it / lol

I fequently save every thing twice, even the ATLS settings etc.

That must be related to caching. I've noticed that myself.