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.

Sign up for GitHub

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

Pathfinding change on compatible railtypes #5216

Closed
DorpsGek opened this issue Jun 21, 2012 · 6 comments
Closed

Pathfinding change on compatible railtypes #5216

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

Comments

@DorpsGek
Copy link
Member

V453000 opened the ticket and wrote:

Hello,

when I use 2 compatible railtypes - in this case monorail and universal rail from NUTS train set in the "decision" piece of rail where train decides whether it will go to the reverser or to the signal,
the 2way eol stops working with different railtypes.

Seems to apply for both combinations - all tracks monorail with 1 piece of univ rail, or all tracks univ rail with 1 piece of monorail.

The trains have native tracks monorail.

I am using r24217

Properties of universal rail can be found here
http://paste.openttdcoop.org/show/1494/

Quick illustration of the issue comes in the pictures, for the rest is the savegame :) There are 2 newGRFs - NUTS train set from bananas, and newbridges from our grf pack http://wiki.openttdcoop.org/GRF

Thank you for your efforts

V453000

Attachments

Reported version: trunk
Operating system: Windows

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

DorpsGek commented Feb 6, 2013

Rubidium wrote:

The NUTS version used in that save is not on bananas.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5216#comment11980

@DorpsGek
Copy link
Member Author

DorpsGek commented Feb 6, 2013

V453000 wrote:

it should work with any version, but this one should be on bananas

Attachments

This comment was imported from FlySpray: https://bugs.openttd.org/task/5216#comment11982

@DorpsGek
Copy link
Member Author

DorpsGek commented Feb 7, 2013

Rubidium wrote:

The attached patch seems to solve it, but I fear it is desync prone.

Attachments

This comment was imported from FlySpray: https://bugs.openttd.org/task/5216#comment11983

@DorpsGek
Copy link
Member Author

DorpsGek commented Feb 7, 2013

Rubidium wrote:

Strike the fear... it DOES desync, so not a solution at all.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5216#comment11984

@DorpsGek
Copy link
Member Author

DorpsGek commented Feb 7, 2013

Rubidium wrote:

Why does this seem to work in case of normal rail + electrified, electrified + normal and electrified + universal, but not for monorail + universal? I'm flabbergasted.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5216#comment11985

@DorpsGek
Copy link
Member Author

Rubidium closed the ticket.

Reason for closing: Fixed

In r25609

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

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
@DorpsGek DorpsGek mentioned this issue Apr 10, 2018
Closed
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