-
Notifications
You must be signed in to change notification settings - Fork 85
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 prefer to stay in lane at all intersections #1483
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looking fine
fc5efb0
to
554f343
Compare
I will ignore (i.e. fall back to old code) bi-directional lanes in this PR. I created #1486 to cover bi-directional problems for all of routing manager (note that the code already had problem with bidirectional lanes even before this PR). |
will this PR benefit from some of the extensions you added in #1487 |
@aubergine10
No. All I need here is to ignore train/bidirectional lanes which I can detect using In any case if you think the code is good you can approve this PR. |
fixes #1475
TMPE.zip
similar Lane Index
.PS: Created
TrackUtils
class even though it has only one function. I might add more stuff to it in future if I deal with Continues junction barrier stuff (#1223) or if I bring Hide-Unconnectred-Tracks to TMPE. (maybe I should call it DirectConnectUtils)PS2: I used
$"{varaible}"
to log stuff because it was more reliable. I hope you don't mind: #1484EDIT: for bidirectional/station tracks I fall back to original code.