Upcoming Games

No games to display

Full list
Add a game

Upcoming Events

No events to display

Who's Online

2 Issues from the Chain

You are here: Home > Forum > Simulations > Released > Peterborough > 2 Issues from the Chain

Page 1 of 1

2 Issues from the Chain 01/01/2021 at 13:26 #135796
elltrain3
Avatar
358 posts
Hello, so while playing the 1985 TT on a MP game chained with X, I found 2 things:

First, if a train attempts to traverse the Up Slow at new England in the wrong direction they hit some virtual "buffer stops" and not sure if that's a bug? as I sure hope there are no buffer stops there!

and second, at signal P493 At Werrington Junc, it gave train 2K02 a double yellow for the Spalding line which assuming the Spalding signals are correct isn't possible as its a 4asp home on the DF then a 2 aspect home followed by a repeater and home so a double yellow isn't possible from this signal! as the preceding signal can't display a yellow apspect.

thanks :)



Post has attachments. Log in to view them.
Resident Mock Maker! / "The Out Of Control Host"
Last edited: 01/01/2021 at 13:28 by elltrain3
Reason: None given

Log in to reply
2 Issues from the Chain 01/01/2021 at 13:46 #135798
Steamer
Avatar
3913 posts
elltrain3 in post 135796 said:

First, if a train attempts to traverse the Up Slow at new England in the wrong direction they hit some virtual "buffer stops" and not sure if that's a bug? as I sure hope there are no buffer stops there!
While technically an issue (and logged, #32667), the Up Slow is uni-directional in this era, so you shouldn't be making this move anyway.

Quote:
and second, at signal P493 At Werrington Junc, it gave train 2K02 a double yellow for the Spalding line which assuming the Spalding signals are correct isn't possible as its a 4asp home on the DF then a 2 aspect home followed by a repeater and home so a double yellow isn't possible from this signal! as the preceding signal can't display a yellow apspect.
I've asked the question (#32668), it could be a bug or could be a real-life aspect control.

"Don't stress/ relax/ let life roll off your backs./ Except for death and paying taxes/ everything in life.../ is only for now." (Avenue Q)
Log in to reply
2 Issues from the Chain 01/01/2021 at 14:27 #135800
elltrain3
Avatar
358 posts
Yes, we were doing some shunting to fix a Mexican stand off, so was not a move I wanted to make! but found the buffer stops while doing it.

and ah okay, just upon first glance my signalling mind knew it wasn't possible, but i'm sure someone will know the whether it does/does not happen IRL!

Resident Mock Maker! / "The Out Of Control Host"
Log in to reply
2 Issues from the Chain 01/01/2021 at 22:32 #135842
clive
Avatar
2736 posts
Steamer in post 135798 said:
elltrain3 in post 135796 said:

First, if a train attempts to traverse the Up Slow at new England in the wrong direction they hit some virtual "buffer stops" and not sure if that's a bug? as I sure hope there are no buffer stops there!
While technically an issue (and logged, #32667), the Up Slow is uni-directional in this era, so you shouldn't be making this move anyway.
Okay, here's the explanation.

In the "old" scenario, trains can be signalled on to the Up Slow in the down direction to allow a loco to couple on to a rake left on the line. Because it might only be part of the original train, it's permitted for the rake to be sitting on 7734 and not 7733. That means both those track circuits are bi-directional in all eras. Because the route can only be set with one of those tracks occupied, there's no limit of shunt signal anywhere.

Trains aren't allowed to reverse on to 7735 because there's an automatic signal (472) in the other direction. The theory is that it will be held at red by the rake the loco is going to couple up to. But if we allow the train to reverse along there it could be heading towards 484 or 486 at yellow, resulting in a train unable to stop in time to prevent a collision.

So 7733 and 7734 are coded as bidirectional track and we rely on the signalling to prevent trains being sent along them in the Down direction. But 7735 is single direction in the old era, with the down direction sub-route disabled entirely. That is what's causing the "buffer stop" message. You'll get the same "buffer stop" message if you try to reverse a train anywhere on the Down Slow north of 7734 for the same reason.

Disabling the sub-route was the easiest option to code at the time. I will look at ways to change the message but it's not high priority.

Log in to reply
The following user said thank you: Steamer
2 Issues from the Chain 01/01/2021 at 22:57 #135843
clive
Avatar
2736 posts
Steamer in post 135798 said:
elltrain3 in post 135796 said:

and second, at signal P493 At Werrington Junc, it gave train 2K02 a double yellow for the Spalding line which assuming the Spalding signals are correct isn't possible as its a 4asp home on the DF then a 2 aspect home followed by a repeater and home so a double yellow isn't possible from this signal! as the preceding signal can't display a yellow apspect.
I've asked the question (#32668), it could be a bug or could be a real-life aspect control.
It's real. All the signals on the fast lines that used to be able to show a flashing green are restricted to double yellow when a diverging route is set. So in the case of 493, it shows single yellow when SD28 (it's a St.James Deeping signal, not a Spalding one) is red and double yellow when SD28 is green. You'll see similar behaviour at 543 and 544 at Tallington. I don't know what the reason for this is; these are approach-controlled routes so the driver is going to get an ARS warning anyway. 612 at Stoke is also restricted to YY for trains to the Up Slow.

Log in to reply
The following user said thank you: Steamer
2 Issues from the Chain 01/01/2021 at 23:15 #135844
elltrain3
Avatar
358 posts
so another problem...
a TCF appeared between Hitchin and Arlesey and on Petebourgh sim it shows it as having an occupancy which clearly does not (see screenshot) though on KX Sim its a piece of un-track circuited track so can't be cleared, I've tried to occupy then unoccupy the T.C. But to no avail.

is this a bug? as the T.C. seems to be in no mans land!

Post has attachments. Log in to view them.
Resident Mock Maker! / "The Out Of Control Host"
Last edited: 01/01/2021 at 23:24 by elltrain3
Reason: P.S. This is my 100th post woohoo!

Log in to reply
2 Issues from the Chain 01/01/2021 at 23:51 #135847
Albert
Avatar
1313 posts
clive in post 135843 said:
I don't know what the reason for this is; these are approach-controlled routes so the driver is going to get an ARS warning anyway.
I hope for the driver that he doesn't have to deal with route setting and that you meant AWS here!

AJP in games
Log in to reply
2 Issues from the Chain 02/01/2021 at 01:39 #135858
AlexRail575
Avatar
136 posts
Regarding the TCF issue, also to note that it did not trigger an alarm, and the train which triggered it remained listed in the "Train list" as "Transferring to external signalbox" well after it had left the area - manual removal was suggested but not enacted, I don't know if Elliot tried this after the end of the session.
Last edited: 02/01/2021 at 01:40 by AlexRail575
Reason: None given

Log in to reply
2 Issues from the Chain 02/01/2021 at 16:00 #135895
elltrain3
Avatar
358 posts
yeah, me and Peter had a fiddle, but the TC remained occupied! rather annoyingly
Resident Mock Maker! / "The Out Of Control Host"
Log in to reply