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

All aircrafts and all airports(build menu) become unavailable in 2085. #6179

Closed
DorpsGek opened this issue Dec 2, 2014 · 7 comments
Closed
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Dec 2, 2014

Pershyn opened the ticket and wrote:

It's year 2085. In June/July all aircrafts and airports become unavailable for some reason. I have attaches the saved game(1st of May). In month or two this happens. The exact date is somewhat random. If I use cheat tool to go backwards in time airports and aircraft still won't be available. If I open "build airport" menu before this happens I will be able to build airports(until I close the menu). If I run openttd from command line there seem to be no errors. I didn't notice anything else, just airports and aircrafts... Maybe I am just missing some config option?

Reported version: 1.4.4
Operating system: Linux


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

DorpsGek commented Dec 2, 2014

planetmaker wrote:

Did you forget to attach the savegame you meant to attach?
Some airports and most aircraft cannot be built past beyond a certain date. Do you use any NewGRFs?

However, if you use the time cheat, that will never bring you back any items which already expired and became unavailable.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6179#comment13644

@DorpsGek
Copy link
Member Author

Pershyn wrote:

Hm, I thought I have attached the file... Well, I'll try again. Yes, I use NewGRFs. I expect some airports to expire, but not all of them.

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/6179#comment13679

@DorpsGek
Copy link
Member Author

DorpsGek commented Jan 1, 2015

Pershyn wrote:

Added missing file.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6179#comment13680

@DorpsGek
Copy link
Member Author

DorpsGek commented Jan 1, 2015

Rubidium wrote:

The getting unavailable of vehicles is due to aging of the vehicles. When a vehicle type is a particular amount of time old (somewhat random) it gets marked as expired. To not need a near infinite amount of vehicles to run to the end of time, the aging and thus expiration stops after a certain date which is 2050 by default.

However, there is a road vehicle in this savegame that gets introduced in 2083 which causes the stopping of aging and thus expiration of all vehicles to be pushed back from around 2050 to much later. This is calculated using introduction date + vehicle life length / 2 so 2083 + 18/2 = 2092 is the year where the aging stops instead of 2050. This causes vehicles that would normally remain forever to keep on aging and thus expiring.

So technically this is no bug in OpenTTD, although I do agree it might be useful to have at least one vehicle remain, i.e. to give different classes different aging "limits". The main problem is, however, determining these classes. For road vehicle you'd always want at least one variant for each cargo, but then what if there are trams? You need a separate class for trams. And now it gets messy, because you want to effectively do this for trains as well... but should you might not want to keep a steam train forever, you must convert into electric at some point. But should you be forced to go to monorail or maglev? But then someone introduces the univeral rail type and suddenly all vehicles can run on the same track, so they should get the same expiration... right?

As you can see, it's a hornet's nest for which I have no clear answer at the moment.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6179#comment13681

@DorpsGek
Copy link
Member Author

DorpsGek commented Jan 1, 2015

Pershyn wrote:

Thank you very much! I had no idea what could possibly make all those stuff expire... The way I thought was each vehicle just have its own expiration date. It would be nice to have an option for aging to stop after custom year, so it won't be pushed back. So all the vehicles that are present or will be introduced after that year would stay forever.

Is there a way to stop aging in this particular save?


This comment was imported from FlySpray: https://bugs.openttd.org/task/6179#comment13685

@DorpsGek
Copy link
Member Author

Pershyn wrote:

Looks like I finally got it. If I just change options "Vehicles never expire" to true lets say in year 2050, then all the needed aircrafts will remain forever. Thank you guys for showing the direction.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6179#comment13747

@DorpsGek
Copy link
Member Author

DorpsGek commented Feb 9, 2015

planetmaker closed the ticket.

Reason for closing: Requested by user

As of request


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

@DorpsGek DorpsGek closed this as completed Feb 9, 2015
@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