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

maintenance order in timetable #4414

Closed
DorpsGek opened this issue Jan 17, 2011 · 3 comments
Closed

maintenance order in timetable #4414

DorpsGek opened this issue Jan 17, 2011 · 3 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

alocritani opened the ticket and wrote:

different behavior exists for train and road vehicles timetables, regarding maintenance order.
RVs act this way: autofilling timetable result in 1 day travel length between standard order and maintenance one.
trains' timetable instead results in a "not all timetabled" line

Attachments

Reported version: Version?
Operating system: All


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

Rubidium wrote:

Why can't you simply attach the savegame so we don't have to spend 15 minutes to get a test case?


This comment was imported from FlySpray: https://bugs.openttd.org/task/4414#comment9476

@DorpsGek
Copy link
Member Author

alocritani wrote:

savefile attached

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/4414#comment9491

@DorpsGek
Copy link
Member Author

Rubidium closed the ticket.

Reason for closing: Fixed

In r21831


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

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant