Upcoming Games

No games to display

Full list
Add a game

Upcoming Events

No events to display

Niche set of failures results in confusing outcome?

You are here: Home > Forum > Simulations > Released > King's Cross > Niche set of failures results in confusing outcome?

Page 1 of 1

Niche set of failures results in confusing outcome? 29/07/2022 at 15:29 #147380
j.a.g1
Avatar
16 posts
I was playing through the very early hours of kings cross on the 2015 timetable, and encountered a track circuit failure and a points failure very close to each other, on the down canonbury line and on the down goods which joins it.

I had train 4E83 entering on the down canonbury line being held at the red signal due to the track circuit failure. I set the route through (since the track circuit failure occurred when a route was not set), and authorised 4E83 to pass the signal at danger. it did so, reached the next signal which was green, and came to a halt claiming that the signal was red! Cancelling the route caused a message in the message box to say 4E83 would receive an adverse signal change! It was very odd, I didn't test it much since I did not have a lot of time on my hands then, but I thought I should report it nonetheless.

I will link two save games, a snapshot I had where I have not authorised 4E83 to pass signal at danger, and one where I have.

I am not sure the points failure is related to the issue or not, but its so close to the affected area I thought I should mention it anyway.

Post has attachments. Log in to view them.
Log in to reply
Niche set of failures results in confusing outcome? 29/07/2022 at 17:45 #147381
TUT
Avatar
507 posts
Not that this isn't a bug, nor that this isn't really off-topic, but IRL it's against the rules to call a route over a track circuit showing occupied anyway (just by the by, so to speak):

Quote:

2.2 Setting the route correctly on a panel or workstation

b) Calling the route

After you have set the route [manually, using individual point controls], you must call the route, if you can.

However, you must not call the route if you need to keep the entrance signal at danger or the route closed for any reason unless the signalling technician has:
• disconnected the signal
• disconnected the means of issuing MAs or told you the signalling equipment is unable to issue an MA.

You must also not call the route if there is a track circuit failure in the route concerned.

(Module S5: Passing a signal at danger or an end of authority (EoA) without a movement authority (MA))

Last edited: 29/07/2022 at 17:46 by TUT
Reason: None given

Log in to reply
The following user said thank you: j.a.g1
Niche set of failures results in confusing outcome? 29/07/2022 at 18:04 #147382
Hap
Avatar
985 posts
Ran both saves. The 0300 save, I couldn't reproduce the issue. As per Rule Book module S5 (As TUT has posted), instructed driver to pass signal and examine line. he stopped at the PLS and I called him passed again. Train came to a stand at 381, called in with no obstruction found and I cleared the signal for him. He moved on.

With the other save. I found that asking driver to shunt forward triggered him to call in and declare "no obstruction found" and then he accepted the signal. But, before that I was stuck in a loop of asking him to pass signal at danger, and him phoning in again saying stopped at signal 381.

How to report an issue: www.SimSig.co.uk/Wiki/Show?page=usertrack:reportanissue
Log in to reply
The following user said thank you: j.a.g1
Niche set of failures results in confusing outcome? 29/07/2022 at 20:28 #147384
Stephen Fulcher
Avatar
2025 posts
Two reasons not to call a route over a failed track:

1. You might inadvertently get a call-on route and the signal clear when you don’t want it to.

2. You will route lock beyond the failure.

Log in to reply
Niche set of failures results in confusing outcome? 29/07/2022 at 22:08 #147385
Hap
Avatar
985 posts
I will add though... In reference to the KGX version history. Kings Cross won't be receiving any further attention for the foreseeable.
How to report an issue: www.SimSig.co.uk/Wiki/Show?page=usertrack:reportanissue
Last edited: 29/07/2022 at 22:09 by Hap
Reason: None given

Log in to reply