roeter, on 12 June 2017 - 02:04 PM, said:
It's allready possible to run beyond 24 hours - trains can be started after midnight by adding '$next' to the start-time.
I suppose it would be possible to add a '$next2' etc., to add even further days.
A 'restart' of the timetable after 24 hours is far more difficult. Not only would it require some kind of link between trains which finished there run and are stored as 'static', and what service they would form the next day. But the main problem is that when the timetable starts, all trains are processed and kept in 'memory' - allowing quick access when a train forms into another train.
At the end of the day, that stack of trains has been processed and is empty. To start again, it would be required to reform this database.
The value of having multiple days of running is limited - one will regularly have to save and restart a session, and there is little difference in restarting a saved session at, say, 02:00, or starting a new session at that time.
As said, using '$next' you can run trains after midnight, and by starting overnight trains at about 01:00 or 02:00, but terminating them later (about 03:00 or 04:00), you can simulate a real full day's work including full traffic around midnight.
Regards,
Rob Roeterdink
Thank you for an explanation. I missed $next command <shame>.
And I do agree that simple restarting after 24h is not possible under current developement (ie. will need a lot more data to manage static consists and solving other problems you mentioned).
Just one another question: Have you already implemented timetable sets? These might be usefull for ie. 'hidding' some trains (move them to another timetable) which are not intended to run by player (route-in and route-out trains, trains populationg small parts of other routes visible form driven route, etc) or just to separate (have them in another timetable) trains running in a different directions.