Page 1 of 1
| 5Z47 calling from incorrect signal at Par 05/05/2023 at 22:57 #151694 | |
zacpartridge
10 posts 
|
I am in the testing stage of my Cornwall 30th April 2023 timetable for the day that the Flying Scotsman ran last weekend. I have noticed what I think is a bug when trying to shunt the FS at Par. The train is scheduled to join the loco (which at this stage has just run round) and coaches together at Par P3 before shunting to 'Par East PR3/PR15' and going into the US before once again shunting out to P2 to form the northbound return service. After the loco and coaches have joined and the train is waiting for right away, I have signalled the train from PR52 to the shunt triangle on the Up Main. After two minutes of the train not moving, the driver rings up complaining to be waiting at PR51 on the Up Main whilst the TCs clearly shows the train still waiting at PR52 at Par P3. I have also tried signalling the train from PR52 to PR51, and also from PR52 to the PRDMLOS but the same issue reoccurs each time. Am I missing something obvious or is this a bug? Screengrab of the call and save game about 5 sim minutes before the issue occurs are attached. 
Post has attachments. Log in to view them. Last edited: 05/05/2023 at 22:59 by zacpartridge Reason: None given Log in to reply |
| 5Z47 calling from incorrect signal at Par 06/05/2023 at 02:30 #151695 | |
GeoffM
6288 posts |
If you explicitly define the stopping position to be 27m from the end of the platform I think it should work. Sometimes the complex shunting moves / multiple joins/divides mean things don't get left exactly where you want them. In this case the engine joining on to the front was exactly at 150m along the 150m track section, meaning it was 5m beyond the signal (set back from the TC end), so yes PR51 was its next signal*. Add to that, trains won't depart from stations if they can see a red signal in the near distance. * Ignoring the fact of cabs being at the back of steam engines! SimSig Boss Last edited: 06/05/2023 at 02:32 by GeoffM Reason: None given Log in to reply The following user said thank you: zacpartridge |
| 5Z47 calling from incorrect signal at Par 12/05/2023 at 20:26 #151811 | |
RobJ
57 posts |
zacpartridge in post 151694 said:I am in the testing stage of my Cornwall 30th April 2023 timetable for the day that the Flying Scotsman ran last weekend. I have noticed what I think is a bug when trying to shunt the FS at Par.I'm impressed with the drivers vision! As PR51* is 742 YARDS away, around a corner AND behind a bridge! 7-5-5, closing of comment Last edited: 12/05/2023 at 20:28 by RobJ Reason: None given Log in to reply |
| 5Z47 calling from incorrect signal at Par 13/05/2023 at 08:35 #151817 | |
Stephen Fulcher
2029 posts
|
Simsig only sees distance not curvature and structures.
Log in to reply |
| 5Z47 calling from incorrect signal at Par 13/05/2023 at 12:17 #151819 | |
|
RobJ
57 posts |
Stephen Fulcher in post 151817 said:Simsig only sees distance not curvature and structures.I figured so, i was making a funny haha. Nothing serious 
7-5-5, closing of comment Log in to reply |
| 5Z47 calling from incorrect signal at Par 13/05/2023 at 12:33 #151821 | |
|
bill_gensheet
1318 posts |
Stephen Fulcher in post 151817 said:Simsig only sees distance not curvature and structures.I recall it was 200m - but was that a system wide default or a variable you could set per sim / signal ? Log in to reply |
| 5Z47 calling from incorrect signal at Par 13/05/2023 at 15:58 #151830 | |
|
GeoffM
6288 posts |
300m by default; can override by signal.
SimSig Boss Log in to reply The following user said thank you: bill_gensheet |