You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trains can get stuck in a depot "waiting for free path" under the following conditions: A train is going to a depot that is included in its order list but is interrupted by a "send to depot" command which sends it the depot it was going to anyway. When the train is released, the original order to go the depot is still active. In most cases the train will exit, circle around and reenter the depot it just left. But in others, the train is stuck waiting for a free path, because it wants to exit and reenter the same depot and can't find a path. A stuck train can be freed by skipping the current go to depot order or by telling it to ignore the signal.
Attached is an example. Train 80 was on its way to the depot when it was issued a send to depot command. It is now "stuck" in the depot.
Attached is a similiar situation without PBS.
The train is heading for the nearest depot, but when entering a different depot it decides for a new neareast depot.
slgann opened the ticket and wrote:
Attachments
Reported version: 0.7.0
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/2873
The text was updated successfully, but these errors were encountered: