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
I've built a quite large train network, based on path signals, in which the trains keep getting lost despite using waypoints in critical junctions. I'm attaching a savegame in which Train 109 is scheduled to go non-stop via "Waypoint Lindham 1 NW." and then non-stop via "Waypoint Lindham 2 NW." located 8 units further ahead. I get a message that it is lost when it passes "Waypoint Lindham 1 NW.". In this particular case it doesn't really matter since it seems to choose the right track anyway.
But go ahead an watch Train 105 a bit further down the track. A few days after Train 109 gets lost, Train 105 also gets lost and choses the wrong track. It is scheduled to go non-stop via "Waypoint Wrafingbridge 1NW." and then non-stop via "Waypoint Wrafingbridge Side NW", a side track deviating from the "main line". It gets lost at "Waypoint Wrafingbridge 1NW." and continues straight on the main line rather than turn to the side.
And these are not just two isolated incidents. This happens all the time on this map, just let it run a few more days and watch the messages pop up. Some of them are for trains that have been lost for a long time, but others will be trains that has been doing just fine and all of a sudden get lost. For instance, another common place where this problem occurs is near the northbound junction near Prenningpool, where trains keep going straight on the main line rather than turning up to Prenningpool Mines.
At first I didn't have these many waypoints, but started to place more and more of them trying to battle the "lost"-messages that became more and more frequent. It doesn't seem to help. As you can see the pathfinder isn't able to find the waypoints even when they are just a few units away.
I have edited the following parameters in openttd.cfg (I don't want my trains to ever turn around except at stations), but setting them to the default values again doesn't seem to help.
I'm furthermore attaching my NewGRF settings and the relevant Advanced Settings. If you need more information, don't hesitate to ask. I am eager to get this problem solved and continue to build my oversized network of trains, boats and the occational horse.
I can confirm it misbehaves, but I've so far failed to create a simple testcase where it fails.
They don't fail/get lost if the waypoint is placed one tile further from the signal, so the waypoint directly followed by the signal seems to at least a contributing factor.
In other words it first reserves the further path and then finds out it is on the waypoint tile. The pathfinding then messes up because it starts searching from "after" the waypoint and from there there is no direct route (without reversing in a station) back to the waypoint.
Indeed. I've moved all waypoints so that there is at least one tile between them and the signals, and it all seems to be working fine now. No lost trains whatsoever. Many thanks!
k9us opened the ticket and wrote:
Attachments
Reported version: 1.0.0
Operating system: Windows
This issue was imported from FlySpray: https://bugs.openttd.org/task/3770
The text was updated successfully, but these errors were encountered: