Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Who's Online

Fendahl, mattfleaydaly, jem771, Person82, 442s3, andi, BenWright, Kage (8 users seen recently)

Liskeard yard 'shunting' and the LSK-CJ token

You are here: Home > Forum > Simulations > Released > Cornwall > Liskeard yard 'shunting' and the LSK-CJ token

Page 1 of 1

Liskeard yard 'shunting' and the LSK-CJ token 06/04/2024 at 11:53 #155961
Robyn
Avatar
74 posts
So, half of this move works through testing, the other half seems not to.

Coaches stable overnight in the goods yard, engine comes up from Moorswater shed and couples, then shunts the coaches into the branch platform reversing at Lsk GF. It gets as far as reversing at the GF, then no matter what I do the train goes back to the goods yard, and not the branch platform.

2019 era.

While we're on this topic. Theoretically, you should be able to seed a train in P3 at LSK, and have another train join it coming up from Coombe, as the 'start' of the token section (stopboard) is only at the end of the platform (meaning that the platform itself is entirely within station limits). This was the way I tried to timetable this originally but the engine sat at LSK GF refusing to go any further. (could talk it past and may have to if this GF shunt simply isn't possible)

I have other workarounds, but this is probably the most historically accurate way for the era I'm timetabling.

7-5-5, closing of comment
Log in to reply
Liskeard yard 'shunting' and the LSK-CJ token 06/04/2024 at 15:04 #155966
Stephen Fulcher
Avatar
2078 posts
To get the sim to route a train towards Platform 3 you need line code BAY at Liskeard Yard GF. If that is not present then the sim will send the train towards the Yard.

A train will not pass the stop board unless the line is clear all the way to the stop blocks.

What year is the timetable you are writing?

Log in to reply
Liskeard yard 'shunting' and the LSK-CJ token 06/04/2024 at 15:58 #155969
Robyn
Avatar
74 posts
Stephen Fulcher in post 155966 said:
To get the sim to route a train towards Platform 3 you need line code BAY at Liskeard Yard GF. If that is not present then the sim will send the train towards the Yard.

A train will not pass the stop board unless the line is clear all the way to the stop blocks.

What year is the timetable you are writing?
I didn't even notice there were path codes for the GF! And it's the wtt effective September 26th 1949 (with amendments owing to rationalisation) the 2019 era must be used as it's the closest to simulating to amount of blockposts that would've been there. (thanks to the numerous new signals enroute!)

7-5-5, closing of comment
Log in to reply
Liskeard yard 'shunting' and the LSK-CJ token 06/04/2024 at 20:41 #155977
Stephen Fulcher
Avatar
2078 posts
Realistically, I think you will struggle to get anywhere near a 1949 timetable in the sim. There are far too many major infrastructure changes, especially around freight workings.
Log in to reply
Liskeard yard 'shunting' and the LSK-CJ token 06/04/2024 at 22:21 #155979
Robyn
Avatar
74 posts
Stephen Fulcher in post 155977 said:
Realistically, I think you will struggle to get anywhere near a 1949 timetable in the sim. There are far too many major infrastructure changes, especially around freight workings.
You are correct, that's why I said "with amendments" I have finished writing the passenger, parcels and perishables timetable, and am playtesting it as we speak, I've yet to start on the goods, but I have plans.

7-5-5, closing of comment
Log in to reply
Liskeard yard 'shunting' and the LSK-CJ token 07/04/2024 at 02:54 #155981
Hap
Avatar
1039 posts
For benefit of doubt, Cornwall sim has been provided with 3 Eras. These Eras are 2000, 2009 and 2019, detailed here.

Any user who wishes to construct their own TT will have to do so within the boundaries and limitations of what has been provided and detailed within the simualtion manual.


Post has attachments. Log in to view them.
How to report an issue: www.SimSig.co.uk/Wiki/Show?page=usertrack:reportanissue
Log in to reply