Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Who's Online

waucott, Hap, Meld, Galatea45699, Person82, Kage, Djennison, Dionysusnu, postal (9 users seen recently)

6E81 is more than 9 minutes early surely

You are here: Home > Forum > Simulations > Timetables > Tyneside IECC > 6E81 is more than 9 minutes early surely

Page 1 of 1

6E81 is more than 9 minutes early surely 17/11/2022 at 16:20 #148800
bugsy
Avatar
1766 posts
Tyneside 15-10-09 timetable.
This is only a very, very minor point and I wasn't going to mention it. However, I changed my mind and wasted precious minutes of sim playing time whilst typing this.

So. Just before 18:20 I'm holding 6E81 outside Newcastle Station so that it doesn't get in the way of 1M72 (in P4), both of which are bound for Northallerton.

As you can see. The clock says that it is 18:20 and 6E31 is scheduled to pass through P4 at 19:20. Unless my maths is incorrect, that makes it 1hr 9 mins early not 9 mins.
...
Edit/Update: After passing through Newcastle Station, the time updated correctly, so no worries.

Post has attachments. Log in to view them.
Everything that you make will be useful - providing it's made of chocolate.
Last edited: 17/11/2022 at 16:28 by bugsy
Reason: None given

Log in to reply
6E81 is more than 9 minutes early surely 17/11/2022 at 16:48 #148802
Joe S
Avatar
129 posts
It's all to do with passing timing points - the train won't update a delay until it's done so.🙂
Log in to reply
The following user said thank you: bugsy
6E81 is more than 9 minutes early surely 17/11/2022 at 16:58 #148803
Dionysusnu
Avatar
577 posts
Online
The field lists "last reported delay". That means that at the last previous location the train was timetabled to pass/depart, it did so 9 minutes before its booked time. In this case, that would be Heaton, which it was booked to pass at 18:22. By adding the (negative) delay to that, you can work it out it must have done so at 18:13.

The reason the train is now 50 minutes early is because it was booked to wait in Heaton UGL. Since this timetable was made before the new "set down type" feature released, the stop is listed with an arrival and departure time at Heaton South Jn, but still with the "passing time" option ticked. This can make it easy to miss while glancing at the timetable, so pay attention with freights approaching important loops. You can see a stop is set up in the same way at the "Durham T358" location in your screenshot.

Log in to reply
6E81 is more than 9 minutes early surely 17/11/2022 at 20:32 #148810
bugsy
Avatar
1766 posts
Dionysusnu in post 148803 said:
The field lists "last reported delay". That means that at the last previous location the train was timetabled to pass/depart, it did so 9 minutes before its booked time. In this case, that would be Heaton, which it was booked to pass at 18:22. By adding the (negative) delay to that, you can work it out it must have done so at 18:13.

The reason the train is now 50 minutes early is because it was booked to wait in Heaton UGL. Since this timetable was made before the new "set down type" feature released, the stop is listed with an arrival and departure time at Heaton South Jn, but still with the "passing time" option ticked. This can make it easy to miss while glancing at the timetable, so pay attention with freights approaching important loops. You can see a stop is set up in the same way at the "Durham T358" location in your screenshot.
Thanks for explaining this to me. I've made a note so will not raise this issue again. Perhaps I should have realised this in the first place

Everything that you make will be useful - providing it's made of chocolate.
Log in to reply