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

Can't insert new order... Vehicle can't go to that station (Maglev Train) #7897

Closed
aljowen opened this issue Jan 4, 2020 · 2 comments
Closed

Comments

@aljowen
Copy link

@aljowen aljowen commented Jan 4, 2020

Version

OpenTTD 1.9.3 (may be present in other versions, haven't tested)
Please note that NewGRF's "FIRS 3.0.10" and "Original vehicles cargo set" are in use on this save file. I am not familiar enough with OpenTTD to know if they are the cause of the issue, It's plausible that they may be.

Expected:

For the station to be added to a trains orders

Error message:

image

Steps to reproduce

Select any train (use train 869 to make things easy), open the "show trains orders" window, use the "Go To" button to add a new order for "Pesdale East" (located just north-east of the depot containing train 869), the error message will be received.

I have found that cloning another trains orders ("Go To" and select another train rather than a station) functions as a workaround. But that does of course have limitations for creating lines that could go between two affected stations.

There are multiple stations with this issue, "Pintditch Stores" is another example. However, I haven't tested every station on the map since there is quite a few. I haven't spotted any pattern.
Nantberg Transport, 1st Aug 2556.zip

@nielsmh
Copy link
Contributor

@nielsmh nielsmh commented Jan 4, 2020

Duplicate of #7881.
Known bug in 1.9.3, workaround is to make sure the tile below the station sign belongs to the station in question.

@nielsmh nielsmh closed this Jan 4, 2020
@aljowen
Copy link
Author

@aljowen aljowen commented Jan 4, 2020

Amazed that issue didn't surface in search results. Thanks for the reply :)

EDIT: Just gonna repeat myself by stating that there is another workaround, since you probably spotted the issue without reading into the body of text.

"I have found that cloning another trains orders functions as a workaround."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.