The International Simutrans Forum

 

Author Topic: Line Scheduling for simutrans standard  (Read 2650 times)

0 Members and 1 Guest are viewing this topic.

Offline prissi

  • Developer
  • Administrator
  • *
  • Posts: 9514
  • Languages: De,EN,JP
Re: Line Scheduling for simutrans standard
« Reply #35 on: June 03, 2019, 05:06:54 AM »
It would be more or less trivial for the UI to have only a + and - button to adjust the time, just like your alarm clock often. That would give you as much precision as you can achieve.

Offline Vladki cz

  • Devotee
  • *
  • Posts: 2677
    • My addons, mostly roadsigns
  • Languages: EN, CS
Re: Line Scheduling for simutrans standard
« Reply #36 on: June 03, 2019, 06:49:07 AM »
What I see as a problem is not precision (ticks vs. minutes) but the cycle length. All schedules have to sync at some time. Be it either beginning of month, year, or tick counter overflow. And then all schedules have to be fractions of that cycle.

I cannot see a working schedule with period of 0.9 cycles (in whatever units)

I do not think that we have to make it extra foolproof in case someone has a complex timetabled network and then decides to change bits per month...

Offline Leartin at

  • Devotee
  • *
  • Posts: 1254
  • PAK-DEV P192C
  • Languages: DE, EN
Re: Line Scheduling for simutrans standard
« Reply #37 on: June 03, 2019, 10:43:11 AM »
I don't think you need an actual cycle if you define the schedule with months. As long as it is "X times per month" or "Every Xth month" or "Each month at X" - you are bound to a monthly cycle by how you enter the information, even if internally it could technically be "every 7 ticks", as long as the player can't set that it would be fine.

If there is no issue with conversion (I'm not convinced, but all the better if there is no issue) the game would store the information with month-independent ticks. As such, if the player sets "Every month", the game converts it to "Every 1440 ticks", and if bpms were changed afterwards, it would still be 1440 ticks, but now it's "Every second month", or "twice per month", depending on how it was changed.
Even if you were unable to set a schedule where three trains leave in two months, due to limitations on what you can enter, you could change bpm, have three trains per month, and change bpm back to spread them over two months, since tickwise, it's the same. The trains would still go at the same real-times, but you could not set it to that again if you were to edit the schedule.