There was an issue with premature departures recently that should be fixed. Just make sure to enable the timetable by checking the box next to the line in the timetable manager.

Also it's good to be aware about how timetable slots are allocated. The vehicle picks the nearest timetable slot when it arrives at it's stop (both in the future and past). So it may appear to leave early when it is actually late for the previous slot and trying to catch up.

Perfect, seems to be working now.

Thank You!

Is there any way to override this behavior, that the train wants to catch up to the previous slot? I want to create a timetable where trains depart every 30 minutes but two trains are slightly not enough for a stable 30 minute cycle, so I have to use three trains. But since the train always wants to catch up to the previous slot, rather than waiting in station until the next slot, I end up with two trains running shortly after one another and the whole timetable falling apart...

The behaviour is as it is to be compatible with as many different uses for timetables as possible.

From the info you have given me so far, I think setting the arrival time to be 15 minutes before the departure time should solve your issue.

If this doesn't work, reply with the timetable setup for one station, and the exact frequency for the line for both 2 vehicles and 3 vehicles and I can have a look to see what can be done.

The frequency with 3 trains is 22 minutes, with 2 trains it's 33.

I had the following setup that failed:
Arrival 05 -> Departure 30
Arrival 35 -> Departure 00

I observed a train departing at 30 as expected. Then shortly after 35 the next one arrived and I would have expected it to wait until 00 but it left after it's min. wait time.

It could very well be, that I am not using the tool correctly or that I'm trying to do something too difficult here...

Yeah, this mod changed how arrival time works. The calculation is that the train takes the nearest arrival time and then departs at the corresponding departure time. So for the setup of: Arrival 05 -> Departure 30
Arrival 35 -> Departure 00

The train will depart at 30 when it arrives after 50 or arrives before 20.
The train will depart at 00 when it arrives between 20 and 50.

With this setup, you might get issues. But they would be with trains waiting longer than expected (e.g. arrives at 21 and departs at 00)



So, as you are getting trains waiting shorter than expected, This is a bug.
A train arriving shortly after 30 should always fall into the (Arrival 35 -> Departure 00) slot

If you could send a copy of the sav.lua file, that would help in finding the cause.
Thank you for the report.

So I have sidings next to a station and I want the trains to leave hourly. For example, I have one line:

Arrival at 30 and departure at 00

Now bare in mind the full line isn't done, but I just have a little loop to test it out. So when it leaves at 00 it gets back at 15, which I would think it would be fine to then pick the 30 arrival slot 15 minutes later and then leave again at 00. But sometimes when it arrives at 15 it'll stop open it's doors and then close them straight away and leave again.

I first thought that maybe it's because there's only 1 arrival and departure time per hour, but them sometimes the trains do wait until the departure time, so whatever the problem is, it happens maybe 50% of the time.

Is there any explanation for this do you think?

The arrival time is too far away that the timetable. The train will pick the timetable slot with the *nearest* arrival time.
So if a vehicle arrives at 14:59 it will pick the 00:00 -> 30:00 timetable slot rather than the 30:00 -> 00:00 timetable slot. This is because 14:59 is nearer to 00:00 than 30:00.

If a vehicle is arriving at 15:00 or later, it should pick up the 30:00 -> 00:00 timetable slot. The exception for this would be that the timetable isn't enabled for that line, or was edited after the vehicle arrived in the station.

Try to make the arrival time in the timetable as close to the actual arrival time for the best results.

I understand that. But it was working fine before the update on the 18th. I've not changed anything, so it has to be something to do with the coding of the mod.

I have another siding with other trains that come back after 10 minutes. They were waiting normally for the next departure time. But again, since the update on the 18th, it's completely messed them up

hey i have an issue my train is arrived the station as a set in the timetable but after it doesnt happen anthing and it causes big traffic jam lots of delay then a reset the next station it starts again.....

btw what does meaning this oopteion forced departure what is the affect i mean how does it work?

could you make some example pls?


Btw i love this mode it is big help for me to plan multiple lines beetwen two cities

@Aqua91

I've added forced departure to the wiki here[github.com].

Apologies but I don't understand the issue you are facing. Could you provide some more details?
Thanks

I have the same problem. This problem is new since last update.

I have a 10 minute shedule Arrival time is 35 and departure time is 40
The train arrives around 35 and leaves imedatly after unloading loading.

The mod is broken now. I have not played the game for a long time but after your last update everything is broken. Even in a new game the timetables are not working properly anymore.

Originally posted by Gregory365:

@Aqua91

I've added forced departure to the wiki here[github.com].

Apologies but I don't understand the issue you are facing. Could you provide some more details?
Thanks

My traines schedule arrive is 25 it is arriving on time but after it stuck on the trainstation ( i tried to mark "forced departure" perhaps solve the issues but it doesnt work for me ) the game doesn't allow to use this feature i cannot activate it ( i have no idea why)

@gorter127
@Aqua91
Did your lines only have one vehicle on them. If so, then this bug has been fixed in v1.3.5.

Originally posted by Gregory365:

@gorter127
@Aqua91
Did your lines only have one vehicle on them. If so, then this bug has been fixed in v1.3.5.

thanks for update but still cant use the forced departure could you check it what is the matter?