In build 100240
Built a simple test map, a central loop and four arms in a star formation around the perimeter. Started with 4 AI consists, one for each arm that goes around the central loop, stopping at one of the four stations and then out and back on its arm. Added an inner loop with 4 AI consists going around. No problem so far. All the AI's interact and politely wait if another consist is in front of them until the way is clear. Now I added a 9th consist that visits each arm in the star formation in turn as well as the central loop stations.
Now one of the AI consists will suddenly not continue. The track is clear, the next command is clear but it refuses to move. If I switch to manual DCC and turn the speed dial, the consist will advance but as soon as I return to the AI schedule, it stops.
Another anomaly is that each consists on the outbound leg will suddenly slow to a crawl, as if it was entering a station and preparing to stop to load passengers. Then it will resume and return to the normal track speed. All consists do this.
If I abandon the schedule for the stuck consist and issue a Drive command, all is well, even the slow to a crawl issue disappears. It seems the schedule command interpreter is causing giving my AI drivers a hard time. Are 9 AI drivers too much? I don't remember having this problem before.
It's a simple map, only some track, four stations, signals to control the trains, and a few track marks and direction markers.
Built a simple test map, a central loop and four arms in a star formation around the perimeter. Started with 4 AI consists, one for each arm that goes around the central loop, stopping at one of the four stations and then out and back on its arm. Added an inner loop with 4 AI consists going around. No problem so far. All the AI's interact and politely wait if another consist is in front of them until the way is clear. Now I added a 9th consist that visits each arm in the star formation in turn as well as the central loop stations.
Now one of the AI consists will suddenly not continue. The track is clear, the next command is clear but it refuses to move. If I switch to manual DCC and turn the speed dial, the consist will advance but as soon as I return to the AI schedule, it stops.
Another anomaly is that each consists on the outbound leg will suddenly slow to a crawl, as if it was entering a station and preparing to stop to load passengers. Then it will resume and return to the normal track speed. All consists do this.
If I abandon the schedule for the stuck consist and issue a Drive command, all is well, even the slow to a crawl issue disappears. It seems the schedule command interpreter is causing giving my AI drivers a hard time. Are 9 AI drivers too much? I don't remember having this problem before.
It's a simple map, only some track, four stations, signals to control the trains, and a few track marks and direction markers.