Coventry timetabling errors

You are here: Home > Forum > Simulations > Released > Coventry > Coventry timetabling errors

Page 1 of 1

Coventry timetabling errors 20/11/2018 at 17:52 #113444
UpDistant
Avatar
8 posts
I currently have Coventry chained to Rugby Centre and Rugby North (all latest versions). Although the chaining arrangement between Coventry and Rugby north generates the comment "inconsistent", tweaking the entry points for Coventry allows train movements across the interface.

However, after a few hours, trains seem to drop out of the Coventry timetable and show as "entered" when in fact they are in the future. Coventry timetable 20090915 v4.0, paused at 09:16:48 to grab a screenshot of the timetable list.

The problem has occurred twice so is reproducible. Any thoughts?


Post has attachments. Log in to view them.
Log in to reply
Coventry timetabling errors 20/11/2018 at 17:57 #113445
headshot119
Avatar
4869 posts
Can you please confirm your timetable, simulation, and loader versions? (Saying latest doesn't really help us)
"Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer
Log in to reply
Coventry timetabling errors 20/11/2018 at 18:08 #113446
postal
Avatar
5189 posts
Online
UpDistant in post 113444 said:
I currently have Coventry chained to Rugby Centre and Rugby North (all latest versions). Although the chaining arrangement between Coventry and Rugby north generates the comment "inconsistent", tweaking the entry points for Coventry allows train movements across the interface.

However, after a few hours, trains seem to drop out of the Coventry timetable and show as "entered" when in fact they are in the future. Coventry timetable 20090915 v4.0, paused at 09:16:48 to grab a screenshot of the timetable list.

The problem has occurred twice so is reproducible. Any thoughts?

Need a bit more information (saved game perhaps). First thing to check is why 2C07 is greyed out. The entry of this train is governed by a rule that it must enter 22 minutes after 2Y59 leaves the area. If you go back up the TT, is 2Y59 greyed out? The entry of 2Y59 is governed by a rule that it must enter 6 minutes after 2Y50 leaves the area. And so on up the chain.

Did you set a start time for your session after the start time of the timetable? If so any train due to enter between the TT and sim start times will not have run and any trains which are descendants of that train will also not run. Similarly. if anything got lost after you tweaked the entry points to override the chaining inconsistencies then trains further down the chain will also be lost.

Only guess-work but two possible reasons.

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Log in to reply
Coventry timetabling errors 20/11/2018 at 19:12 #113448
UpDistant
Avatar
8 posts
Thanks for the replies.
Loader version 4.8.2, Coventry 1.5, Timetable - Coventry 20091015 (0445 start)v4.0.WTT

I will start Coventry again (on its own) to see if this recurs. The sim was paused while I tweaked the timetable and I only changed the entry and exit points for the line to Nuneaton.

I'll let you know what happens.

Log in to reply
Coventry timetabling errors 20/11/2018 at 19:12 #113449
GeoffM
Avatar
6274 posts
headshot119 in post 113445 said:
Can you please confirm your timetable, simulation, and loader versions? (Saying latest doesn't really help us)
Help->About.

Particularly the Coventry simulation version.

SimSig Boss
Log in to reply
Coventry timetabling errors 21/11/2018 at 16:56 #113466
UpDistant
Avatar
8 posts
I've had a run through of Coventry (by itself) starting at 04:45 Coventry 20091015 (0445 start)v4.0.WTT timetable up to 10:30 and I haven't "lost" any trains.

So, I'm going to restart the chain with Rugby Centre and North from 00:00 and keep a closer eye on things.

I'll update the situation as and when.

Log in to reply
Coventry timetabling errors 28/11/2018 at 16:44 #113686
UpDistant
Avatar
8 posts
OK, I have started again from 00:00 (Coventry 20091015 (0000 start)v4.0.WTT), chained to Rugby Centre and North. I have kept the Coventry timetable window visible on screen and all was as expected until 06:10. The first train to apparently drop out is 2Y50, followed by 2Y59 and 2C07. Up until this time everything appeared as per the timetable. In the attached saved game, 6G64-1 has entered early and is in Coventry Yard, leaving the three examples above as "entered" in the future.
Post has attachments. Log in to view them.
Log in to reply
Coventry timetabling errors 28/11/2018 at 17:11 #113688
postal
Avatar
5189 posts
Online
Thanks for the saved game. It moves things forward but doesn't give us an answer.

There is a rule that 2Y50 must enter 22 minutes after 2Y51 leaves the area. That is part of a chain where 2C07 is dependant on 2Y59 running, 2Y59 is dependant on 2Y50 running and 2Y50 dependant on 2Y51 running. You can follow that chain under the Rules tab in the TT.

As the whole chain of trains is showing as not due to enter, the key is whether 2Y51 entered or was just ticked off. It is shown as having entered in the TT as it is already greyed out but that could also happen if the train was not handed over from Rugby Central.

Do you have any earlier Coventry saves after 05:40 to see if 2Y51 is in the Coventry sim or any saves from Rugby Central to see if it actually ran through that sim? Until we know what happened to 2Y51 it is impossible to decide whether it is a Rugby Central sim issue, a Rugby Central TT issue, a Coventry sim issue or a Coventry TT issue. It would be helpful to find out so the problem can be logged in the right place and resolved.

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Last edited: 28/11/2018 at 17:14 by postal
Reason: None given

Log in to reply
Coventry timetabling errors 28/11/2018 at 18:01 #113689
UpDistant
Avatar
8 posts
I have restarted saved games from 05:30. 2Y51 has departed from Rugby on time, it hasn't appeared in the NEXT APPR DOWN STOUR TD berth but has "entered" in the timetable list. I've attached both the Coventry and Rugby Centre games from 05:39.

I can attach the 05:30 games (in a separate post) if that will help.

Post has attachments. Log in to view them.
Log in to reply
Coventry timetabling errors 28/11/2018 at 18:02 #113690
UpDistant
Avatar
8 posts
05:30 games attached
Post has attachments. Log in to view them.
Log in to reply
Coventry timetabling errors 28/11/2018 at 18:50 #113693
postal
Avatar
5189 posts
Online
Perhaps someone who has a licence for Rugby can take this on and try to identify the problem.

(Reported on Issue Tracker as #22278)

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Last edited: 29/11/2018 at 10:00 by postal
Reason: None given

Log in to reply
Coventry timetabling errors 14/08/2020 at 00:50 #130629
postal
Avatar
5189 posts
Online
Developer is unable to reproduce with latest versions of sims and loader. Mantis report closed.
“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Log in to reply
Coventry timetabling errors 14/08/2020 at 00:54 #130630
GeoffM
Avatar
6274 posts
I've fixed all the outstanding issues on Coventry and had all four surrounding sims chained in to Coventry, and all behave as expected. However, since I can't run 5 simulations on my own, even with ARS on two of them, it will undergo a more thorough test ASAP with a few testers.
SimSig Boss
Log in to reply
Coventry timetabling errors 14/08/2020 at 11:50 #130633
8stewartt
Avatar
33 posts
There are no issues.

I have raised this myself in another thread. On the Coventry sim, when chaining to rugby centre and north, you have to choose the 0000 or 0445 NONE V4.0 version. the V4.0 is actually an earlier version of the one that doesn't list a version.

It does say in the text that is a refreshed version of the 4.0 one with the issues rectified.

I have run all together with no issues.

Log in to reply
The following user said thank you: GeoffM