Train path finding logic (0.15)
Posted: Tue May 02, 2017 12:01 am
The changes in 0.15, with a penalty being added to routes that include a station, is a good idea.
However, for my train networks, it can create more problems than it solves.
For me, at least, the only real issue (before 0.15) with trains pathing through stations that were bulk unloading ores with a queue of traffic - holding up the misdirected train for some time. The occasional routing via a remote mining station was never a huge issue.
Additionally, I've had issues where trains are routed via a long single-line, two way route when there's a similar distance double-track route that would be preferable.
So, how about the following:
However, for my train networks, it can create more problems than it solves.
For me, at least, the only real issue (before 0.15) with trains pathing through stations that were bulk unloading ores with a queue of traffic - holding up the misdirected train for some time. The occasional routing via a remote mining station was never a huge issue.
Additionally, I've had issues where trains are routed via a long single-line, two way route when there's a similar distance double-track route that would be preferable.
So, how about the following:
- A small penalty (perhaps 50?) for routes via a station, to give a slight preference to similar routes that avoid the station.
- A larger penalty added for each train scheduled to stop at the station (e.g. 200 for the first train, 500 for the second onwards?)
- If cheap to look up, a further penalty for each train currently heading for that station. And even more penalty if the train is stopped at a signal?
- For tracks signalled in two directions, double (tripple?) the cost.