Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trains in big network keep getting lost when using path signals #3770

Closed
DorpsGek opened this issue Apr 17, 2010 · 3 comments
Closed

Trains in big network keep getting lost when using path signals #3770

DorpsGek opened this issue Apr 17, 2010 · 3 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

k9us opened the ticket and wrote:

Windows Vista Business x86 SP2

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.

wait_oneway_signal = 255
wait_twoway_signal = 255
wait_for_pbs_path = 255

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.

Attachments

Reported version: 1.0.0
Operating system: Windows


This issue was imported from FlySpray: https://bugs.openttd.org/task/3770
@DorpsGek
Copy link
Member Author

Rubidium wrote:

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.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3770#comment7882

@DorpsGek
Copy link
Member Author

k9us wrote:

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!


This comment was imported from FlySpray: https://bugs.openttd.org/task/3770#comment7887

@DorpsGek
Copy link
Member Author

Rubidium closed the ticket.

Reason for closing: Fixed

In r19784


This comment was imported from FlySpray: https://bugs.openttd.org/task/3770

@DorpsGek DorpsGek added flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) bug labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant