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

new path signal in driving direction doesn't clear reservation beyond it (immediately) #3418

Closed
DorpsGek opened this issue Dec 24, 2009 · 8 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

planetmaker opened the ticket and wrote:

when placing a new signal within the reserved path of a train, the path beyond it is cleared for block signals, but not cleared for path signals. That's somewhat inconsistant behaviour. See the attached screenshot sequence.

Reported version: 1.0.0-beta1
Operating system: All


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

planetmaker wrote:

He... sorry. Wrong screenshot sequence. Here's the correct one.

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/3418#comment7109

@DorpsGek
Copy link
Member Author

Rubidium wrote:

This already happens in 0.7, so I reckon it's by design.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3418#comment7110

@DorpsGek
Copy link
Member Author

Rubidium wrote:

Confirmed it behaves like this, but I'm far from sure it is actually a bug.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3418#comment7119

@DorpsGek
Copy link
Member Author

michi_cc wrote:

If you would have placed the path signal on the same tile as the block
signal, the behaviour would have been as expected. Path look-ahead triggers
one tile before the signal, which is exactly where the train is, and this
causes the reservation to be re-applied.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3418#comment7124

@DorpsGek
Copy link
Member Author

planetmaker wrote:

True. Seems I missed on of the obvious things as my usual track design is to have the path signals where they matter most - at stations. And the rest of the track is normal signals. I somehow missed this obvious distinction, sorry.

Despite, I was puzzled and the "problem" then is slightly different: the train in the images is loading at the station. And it reserves those tracks upon entering the station straight through it, even though it will never go there given its orders. What about reserving tracks past signals adjacent to a station (stations are special after all) where a train stops only after it finished un/loading?

Probably this then would go as feature request as it works as designed.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3418#comment7126

@DorpsGek
Copy link
Member Author

michi_cc wrote:

Does this do what you expect?

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/3418#comment7127

@DorpsGek
Copy link
Member Author

@DorpsGek
Copy link
Member Author

michi_cc closed the ticket.

Reason for closing: Fixed

In r18646.


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

@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