So what you want is for trains to repath and get as close as possible to their destination even if there is a train blocking the last bits. They do that anyway though, if you use normal signals instead of chain signals. Though the block nature of signalling, the second example would break regardles...

Thanks for pointing out that trains have different values depending on their running status, I wasn't aware of that. These values however do not have any impact on my examples as the stopped trains are after the branching paths have merged and therefore should be accounted for in both path evaluatio...

I had initially raised this as a bug, however as it was denied bug status it is now a suggestion. Currently the train pathfinder approximately follows these priorities: 1. Unoccupied by a train. 2. Shortest path in rail pieces/distance. 3. Complicated rules with signals/blocks to decide between equa...

After some further experimentation I've come to the conclusion that the train pathfinder almost entirely ignores signals. It's pathing priorities go something like this: 1. Unoccupied by a train. 2. Shortest path in rail pieces/distance. 3. Complicated rules with signals/blocks to decide between equ...

It is not a bug, For the patfinder, there is no reason to pick the other path. I'm not clear on what you mean - are you saying that this is intended behaviour? Another aspect to this is if there is a train inside the short path, the train will path around it. Wait forever at signal: http://i.imgur....

A picture will be the easiest way to understand this bug: Can't go: https://i.imgur.com/w0IMUy6.jpg Can't go: https://i.imgur.com/6Cs0CFs.jpg Free to go: https://i.imgur.com/4dGw0hS.jpg The issue is when the train has a choice between chain and block signals after a chain signal. If the chain signal...