Driver Setup AI Bug (Capacity Issue)

CRAZYPOLOGUY112

New member
Hello, fellow users of Trainz,

I'm using TS12 and I have made a maybe medium to large size custom route with 82 AI drivers running on the route.
Here is where the problem lies: Only 80 of those drivers appear whenever I start Driver, with the last two consists loading without their drivers, as well as a third consist not following their scheduled commands unless I tell them to "Continue Schedule."
Every driver appears with their train in Surveyor in the Driver Setup Rule, and each are paired with the correct loco. I keep getting the Driver Setup bug (DriverSetupRule : Thread Exception: ER_Timeout, line 578, file driversetuprule.gs (1) ), and the Driver Commands bug of the same nature as well. Maybe there is a capacity for how many AI trains are running at once?
 
Last edited:
80 drivers?

The errors you are getting are probably due to the program running out of resources and threads timing out. I don't remember what the maximum number of drivers is, but your quantity of drivers surely is a huge number which is way beyond what I've ever seen.

How can you keep track of that many? I have trouble keeping track of 10 or 20 drivers before they start doing their usual stupid AI behavior and wandering off down branches where they're not supposed to go, or skipping track marks, direction markers, or worse running red signals.

Now on another subject.

I see that this is your first post since your join date in Jul 2012. Your version timeline does not show your TS12 version registered. I highly recommend that you register your Trainz version on My Trainz. If you have already registered your TS12 program and it does not show up, or you are having trouble registering, then contact the help desk for assistance.

Welcome to the forums...

John
 
I don't know if that can help.

Are these permanent drivers on the route, or are they spat out of portals?

With portals you can time your drivers so the huge number isn't the issue because drivers will be entering and exiting all the time instead of all driving at once.

John
 
All of these drivers are permanent drivers. With the system I built, every route has an endpoint, so portals wouldn't necessarily fit in, and only half of the system has trains running.
 
All of these drivers are permanent drivers. With the system I built, every route has an endpoint, so portals wouldn't necessarily fit in, and only half of the system has trains running.

That maybe part of your problem.

When a consist loads up, the program needs to track everything about every train car, locomotive, commodity it carries, location, and probably other details. This doesn't matter whether there's an AI driver associated with the consist or not. When you add into the mix AI drivers with their associated commands and rules, you are now complicating matters further. With that many consists it's looking at once, the program is just running out of resources and the timeouts occur.

John
 
Back
Top