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

Jump to bottom

train turned around twice when leaving depot cannot find path #5093

Closed
DorpsGek opened this issue Mar 9, 2012 · 4 comments
Closed

train turned around twice when leaving depot cannot find path #5093

DorpsGek opened this issue Mar 9, 2012 · 4 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Mar 9, 2012

xahodo opened the ticket and wrote:

When a train is leaving a depot and turned around while it has not fully left the depot and then turned around again, it reports that it is waiting for a free path, while there is a free path.

Steps to reproduce:
- build depot connected to some track. In my case I had a station with a pbs signal in front of it
- build a train (with some wagons?)
- let the train leave the depot
- turn it around before the entire consist has left the depot
- immediately turn it around again
- the train will not find a free path and will say it is waiting for a free path

encountered in r24016

Reported version: trunk
Operating system: All

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

NG wrote:

Do you have a screenshot of this? I don't see it happen in r24001 (no related changes since then).

This comment was imported from FlySpray: https://bugs.openttd.org/task/5093#comment10951

@DorpsGek
Copy link
Member Author

xahodo wrote:

Here's a save with said behavior in r24016 Notice that the train is waiting for a free path, while there is a free path.

Attachments

This comment was imported from FlySpray: https://bugs.openttd.org/task/5093#comment10962

@DorpsGek
Copy link
Member Author

Alberth wrote:

In a block with path signals, the outgoing train claims a path.
Upon hitting 'turn around', the path gets released.
The second 'turn around' does not allocate a new path, and the train stops due to not having an allocated path, it seems.

In this case, a path can be created, but it does not happen. A related case is when a train cannot create one, because another train uses it.

Having a train in a path signal block without a path does not sound very good to me.
Should we ignore the second 'turn around' if no path can be created ?

This comment was imported from FlySpray: https://bugs.openttd.org/task/5093#comment11023

@DorpsGek
Copy link
Member Author

michi_cc closed the ticket.

Reason for closing: Fixed

In r24071.

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

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

No branches or pull requests
1 participant
@DorpsGek