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

[Bug]: Two-ways path signals affect signals behind them #9662

Closed
lcd047 opened this issue Oct 29, 2021 · 3 comments
Closed

[Bug]: Two-ways path signals affect signals behind them #9662

lcd047 opened this issue Oct 29, 2021 · 3 comments

Comments

@lcd047
Copy link
Contributor

@lcd047 lcd047 commented Oct 29, 2021

Version of OpenTTD

12.0, Linux

Expected result

The exit signal 2 in the picture below should be red. The backwards path signal 1 should have no effect on what happens behind it other than a path penalty.

Actual result

The exit signal 2 in the picture below is green.

Steps to reproduce

2021-10-29_14-46

In this picture 1 is a two-ways path signal placed backwards, and 2 is an exit signal (the point of signal 1 being to encourage trains to pick one of the other choices, since they have access to two platforms rather than one). Sadly the path signal 1 seems to affect the functioning of the exit signal 2.

@PeterN
Copy link
Member

@PeterN PeterN commented Oct 29, 2021

All signals mark the end of a signal block, regardless of their direction.

There isn't really a need to use block and pre-signals this way on a terminus station.

@lcd047
Copy link
Contributor Author

@lcd047 lcd047 commented Oct 29, 2021

All signals mark the end of a signal block, regardless of their direction.

Is this a recent change? I believe the above used to work in the past.

@lcd047
Copy link
Contributor Author

@lcd047 lcd047 commented Oct 29, 2021

Right, what I'm saying doesn't make sense. Sorry for the noise.

@lcd047 lcd047 closed this Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants