Can anybody point me where it's announced / how should it be coded?
This will go straight into my replacement project!
It goes in simuconf.tab - have a look at pak128.Britain svn for an example:
http://simutrans.svn.sourceforge.net/viewvc/simutrans/pak128.Britain/config/simuconf.tab?revision=279&view=markup
No city roads in pak britain after 2050???
2050 is the official end date of the pak (for the time being at least). There's not much of anything beyond 2020 so it gets a bit boring after then...
I thought that 2050 was the highest date that would be recognised. If a higher date can be used, I can change it easily in the Experimental version.
Thanks a lot!
Another question:
When a the date changes, how is their replacement working?
As far as I can tell it affects new cityroads, including those where an adjacent building is upgraded. It doesn't all upgrade at once.
Good, I think it is the way it should.
Also in RL roads are NEVER replaced all at once, but gradually...
I like it!
About endign dates: Most very much developed games I got are well beyond 2200, because otherwise it is very hard to construct all those stuff in recent time.
So better set the latest dates to 2999?
Why not?
However, simutrans should not crash if no city-road is defined (ie if year is before/after all definitions of city-roads).
Best is setting no retire date, of course. Why does everyone insist on filling in random "good enough for myself" values?
Does setting no retire date work with the default city road types? I know that it works with things like vehicles and buildings, but I don't think that it works in this case, because the code is different, but I could be wrong.
Roads in 128 have no retire dates, so it seems that way ;)
VS,
do you mean the retirement dates in the roads' .dat files, or the dates specified in the new simuconf.tab parameters?
If no road is specified in simuconf.tab, then the default is "city_road". At least that used to be the behaviour - is that still the case?
Ah, apologies then - I meant dat files. Still, the point stands - some way to make things last infinitely makes life for everyone easier.
ANd indeed, you can omit retirement parameters in simuconf.tab too.
Thanks for the clarification prissi and Dwachs. I will change pak128.Britain to have the final city road with no retire year in simuconf.tab.
Perfect, I'll change simuconf as well. Thanks a lot for the feature :)
Bumping this old thread for a bit of extension request :)
I would like newer cityroads NOT to replace older ones, if not manually (using cityroad tool).
An older city centre would have older streets, unless manually changed.
What do you think?
? The city roads are not updated unless a new city building is created.
Btw, there is now a general_tool[36] that can be used in menuconf.tab to define a timeline aware cityroad building tool.
I think it should be an option:
0 - City roads remain original
1 - City roads update when an adjacent building is built/updated
2 - City roads update like IRL (including a period of "road construction" when a large section of the street is blocked, hehe), that is, as often as new roads come out, but at least once a year.
Ooh, that would be an interesting dynamic... "Under construction" roads with speed limits reduced by, say, 40%... Under construction for, say, one Simutrans month(day)...
My request applies exactly to this case: don't update cityroad if there's an older cityroad, not even when updating the adjacent building. Take over different roads, instead. (Allow instead *manually* updating of old cityroads with newer ones)
Similarily, disallow faster roads to be built over cityroads, unless using CTRL (no point in letting them built and, within months, cityroad taking them over again).
This is an important feature I hope gets implemented, at least as an option. I just hope the code is written so that cost for road p****ing over cityroad will be zero for those tiles where only the path (and not the actual construction) p****es over cityroad.