-
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
lane connector is buggy for bidirectional lanes #784
Comments
Very good quesiton. Personally, I'd say no. Whole purpose of lane connector is to allow user to specifically decide which incoming lanes link to which outgoing lanes. I suspect it was implemented the current way to avoid UI issues once a lane is connected in one direction (the circle for the return direction would be obscured by the existing connection). Bidirectional lanes are a freaking nightmare lol. |
Single-lane train tracks are bi-directional. Hence the Single Train Track AI. So there is already a usecase where people have bi-directional lanes that we'll need to deal with somehow. Also, see #515 (comment) |
Kian wrote:
REV0 (asset author):
|
The main obstacle here is not the back-end but rather its the UI. the forward/backward lane curves cover one-another. One solution is for the lane curves to |
AN assets to that I used for the tests |
This code seems to provide support for bidirectional lanes as it adds lanes in both directions:
TMPE/TLM/TLM/State/Flags.cs
Line 437 in 0131e7f
First of all do we need reverse connection if the lanes are not bidirectional?
Secondly when I tried to connect bidirectional lanes back and forth I noticed intermittent problems. I did not mange to capture them on screen due to its intermittency but this is what happens:
If you play with them long enough you will see.
I tested using this asset: https://steamcommunity.com/sharedfiles/filedetails/?id=1308307531
![Screenshot (685)](https://user-images.githubusercontent.com/26344691/76344319-0997fd80-630a-11ea-99ff-dba34a136cb6.png)
The text was updated successfully, but these errors were encountered: