Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

5L19 blocked by 5L85 in East Yard

You are here: Home > Forum > Simulations > Released > Salisbury > 5L19 blocked by 5L85 in East Yard

Page 1 of 1

5L19 blocked by 5L85 in East Yard 05/11/2021 at 10:52 #142200
BigJacko
Avatar
5 posts
Purchased Salisbury yesterday and am enjoying its subtle complexities immensely. Much more involved than it looks, given its size. Thank you.

Noticed one small oddity that I am sure is down to my practices rather than a bug, but just in case...

1L19 arrives into P4 from the Andover direction. Initially splits into 5L19 and 5065 at the platform.

5065 duly needs a turnaround at the Laverstock loop, all fine. Meanwhile 5L19 wants putting up at SY215 reverse (i.e. into the East Yard) so that it can enter the depot via the Recep line shortly later. But there is a further factor - 5L19 splits again, in the East Yard, forming a new 5L85 on its western end.

This new 5L85 is destined for the Holding Siding via a move to the western side of the station, turning at SY240 reverse - all fine in itself - but this is timetabled quite a bit later on. In the meantime, however, 5L19 cannot now be given the road through the Through Siding into Reception Line and the Depot at its appointed time - because 5L85 is deemed 'in front' and is trapping 5L19 in the eastern end of the East Yard.

Did I miss a trick? Is the move more complex even than it appears? Should I have trundled 5L85 into the Through Siding, in order to allow 5L19 to route west via SY215 and SY225 and back up into the Recep Line? Seems a bit involved, but who knows?

Or is it just a timetable-creation error, and 5L85 should have been formed at the eastern end (i.e the front of the arriving 5L19 train as it got into East Yard), thus enabling 5L19 to move freely into the depot, and 5L85 to have been attended to later?

How have others solved this? Genuinely curious and grateful for pointers.

Many thanks!

Log in to reply
5L19 blocked by 5L85 in East Yard 07/11/2021 at 19:19 #142224
BigJacko
Avatar
5 posts
Just to clarify I'm referring to the Salisbury 15th Oct 09 (0445) timetable here btw.
Log in to reply
5L19 blocked by 5L85 in East Yard 07/11/2021 at 22:41 #142228
UKTrainMan
Avatar
1803 posts
It does indeed look like a timetable creation error with regards to 5L19 / W74811 and the order of the dividing activity at location Salisbury Sig SY215 (rev).

If you can go back to a save before 10:25am...

1: Open F4 Timetable list
2: Type in 5L19
3: Double-click on / edit the timetable for 5L19; go to the Location list tab
4: Double-click on / edit the "SALISBURY SIG SY215 (REV" location
5: Double-click on / edit the single activity shown
6: Simply select the "Divides (new front)" activity instead of the already selected "Divides (new rear)" activity
7: Save the changes you've made (you'll need to press OK about 4 times), but do not save the timetable itself.

Note that if your save is at 10:20am then 5L19 may have already formed after 1L19 arrives and divides in Platform 4, so if that is the case then you should still be able to edit 5L19 'live' via F2 Train List and just follow the steps above from Step 3.

Hope this helps!

Someone with access to the bug board will need to log this error with both versions of the 15th Oct 09 timetable to be corrected via an update.

Any views and / or opinions expressed by myself are from me personally and do not represent those of any company I either work for or am a consultant for.
Log in to reply
The following user said thank you: BigJacko
5L19 blocked by 5L85 in East Yard 08/11/2021 at 01:01 #142231
headshot119
Avatar
4869 posts
Mantis 35011 raised to investigate.
"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
The following user said thank you: BigJacko
5L19 blocked by 5L85 in East Yard 11/11/2021 at 08:55 #142256
BigJacko
Avatar
5 posts
It does indeed help. Nice to know I wasn't going mad or doing something incorrect. Many thanks indeed!
Log in to reply