Blueprint for reproduction
[boskid][0.17.79] Train pathfinder incorreclty assumes path in same segment is shortest
[boskid][0.17.79] Train pathfinder incorreclty assumes path in same segment is shortest
As the train pathfinder is currently implemented it will always prefer the path that ends in the same segment as it starts in, regardless of whether it is the closest one or not:
Re: [0.17.79] Train pathfinder incorreclty assumes path in same segment is shortest
Is automatic routing designed to work with no rail signals at all?
No sensible signalling I can find for that setup produces a bad result. If the train starts out in the same rail segment as its destination stop, it'll go to that stop. Why spend cpu and dev time avoiding such a shruggable consequence? Put signals on your destination stops, everything works.
No sensible signalling I can find for that setup produces a bad result. If the train starts out in the same rail segment as its destination stop, it'll go to that stop. Why spend cpu and dev time avoiding such a shruggable consequence? Put signals on your destination stops, everything works.
Re: [boskid][0.17.79] Train pathfinder incorreclty assumes path in same segment is shortest
This case will take little more time to fix since there are 2 underlying issues:
- when pathfinding (multi segment), penalty of first segment is taken from end to end without consideration where locomotive is, so technicaly train choosed shortest path (it has penalty of only long segment)
- single segment pathfinder runs before main pathfinder and has priority because of this
- when pathfinding (multi segment), penalty of first segment is taken from end to end without consideration where locomotive is, so technicaly train choosed shortest path (it has penalty of only long segment)
- single segment pathfinder runs before main pathfinder and has priority because of this
Re: [boskid][0.17.79] Train pathfinder incorreclty assumes path in same segment is shortest
Both issues are now fixed for next release.