[Program] Scheduled Dispatch Scheduler 1.6.1 - A tool to design timetables

[Erato]

It's been over a year since I've made Peaks & Troughs. I've been using excel to make graphs for a while, but after a few month that got old, so I made a python script, but it was far from perfect or even user friendly. So for that reason I've spent the last week developing the
Scheduled Dispatch Scheduler
Have fun designing timetables using actual timetable graphs in a program that allows you to tweak your timetables and instantly see the results, without needing to press run, or requiring external input.

You can download the program below or from Github.
For bugs, suggestions and issues, please go to the Github page for this project:
https://github.com/EratoNysiad/Schedule ... hScheduler

Credit and License:
UI icons are from OpenGFX.
The project is made using Love2D.
This project is licensed under GPL v2+.

Note:
Please note that by default, the travel times indicated in the OpenTTD time tables are in ticks, and then rounded to the nearest minute. So when it says "travelling for 2 minutes" this can mean that the train actually travels for 1 minute and 30 seconds. Because of this I advise you to reset the times manually after using automate, autofill or any other form of automatic timetable filling and double clicking and then pressing enter. You can choose the setting "Show leftover ticks in timetable" to see if the game uses a rounded value or not. When and if a feature becomes available to have it automatically round the actual planned time to the nearest whole minute.

To compile it for Mac or Linux, please see https://love2d.org/wiki/Game_Distribution

[Erato]

Fixed some crashes. Enjoy!

v1.2 - 09-12-2021
Fixed: Crash related to removing stations
Fixed: Station waiting not always shown properly
Fixed: Timetable not changing when last timetable in list removed

And some more
v1.3 - 09-12-2021
Fixed: Data corruption issue

[Erato]

I've started playing the OpenTTD again for a bit. I'm really enjoying this tool, but while using it I have discovered a crash. If you encounter a crash as well, please report it, especially when it prevents you from reopening your timetables.

v1.4 - 20-12-2021
Fixed: Station waiting times on the return stroke appearing at the wrong position
Fixed: Crash related to not being able to place said strokes at the wrong position

[Erato]

Happy new year! We have crash fixes.

v1.5 - 02-01-2022
Fixed: Crash when timetables are switched when station limits are set
Fixed: Crash when second timetable is deleted

[Erato]

I've been playing a bunch and based on that I got some new features for you all.

v1.6 - 09-01-2022
Feature: Arrow keys can be used to change field being edited
Changed: Increased amount of timetable colours
Fixed: Crash when timetables are switched when lower station limits are set
v1.6.1 - 09-01-2022
Fixed: Crash caused by debug text

[TGVfan]

Any chance of a small (video) tuorial?

[Erato]

I have planned to make a video, but I may be a bit busy as I'm moving soon, so I can't promise anything

[pfvdo]

Hey, cool app!

One thing to fix - when the interval is over 60 or 100 minutes, strange things start to happen (at least on macOS). The graphs for interval 100 minutes are the same as for 60 minutes, for 160 min the same as 200 min, and the graph for 120 min is just not correct. Somehow, the app takes both 60 minutes and 100 minutes as an hour.

I took the liberty of checking out the code and turns out it is a quick fix in drawGraph.lua, line 69.

Code: Select all

local repeatTime = math.floor(tonumber(timeTableData[0][n*masterFileLength+4])/100)*60+tonumber(timeTableData[0][n*masterFileLength+4])%100

should instead be

Code: Select all

local repeatTime = math.floor(tonumber(timeTableData[0][n*masterFileLength+4])/60)*60+tonumber(timeTableData[0][n*masterFileLength+4])%60

Any tips on how to measure or import distance between stations are greatly welcomed! Currently I'm just running a train at 120 kph and dividing the time by 2 but that gets tedious

[Erato]

Thanks for your interest in my project. I deliberately chose to do it that way to have 130 be one hour, thirty minutes. JGR parses time that way as well, hence why.

I got a report saying that some people are missing dll files, a version with MSVCP120.dll and MSVCR120.dll is attached.