Page 1 of 1
6M64 odd behaviour 13/03/2023 at 15:05 #150801 | |
bugsy
![]() 1732 posts |
I think that the driver of 6M64 has got a little bit confused. I'm playing the Staffordshire Summer August 2022 timetable and have encountered a problem. If you look at the timetable (screenshot) you can see that 6M64 is due to travel towards Crewe Basford Hall via Stafford P5 and the Slow line. When the train reached Milford Jn., it stopped when it should have proceeded along the Slow line, the route for which I had set. After a few minutes, the driver called to ask permission to proceed. Although I wondered why he had made this call, I granted permission. The next time that I glanced at the Colwich area of the sim, I noticed that 6M64 had reversed and was now travelling ‘wrong road’ towards Rugeley North Jn., and towards an oncoming train. When I checked the Train List (at 23:25:48) 6M64 was shown as travelling in the ‘Down’ direction at 55mph. This obviously isn’t correct as it was now travelling in the Up direction. In order to continue the game I abandoned the tt. I have attached a save at 23:20:00 Interesting to say the least! ![]() ![]() Post has attachments. Log in to view them. Everything that you make will be useful - providing it's made of chocolate. Log in to reply |
6M64 odd behaviour 13/03/2023 at 15:19 #150802 | |
bugsy
![]() 1732 posts |
Not only did I abandon the timetable, I had to reverse direction to get 6M64 going towards Stafford. It's now travelling in the Down direction, but the Train List says that it's going in the Up direction. I wonder what will happen when I reinstate the timetable. ![]() Post has attachments. Log in to view them. Everything that you make will be useful - providing it's made of chocolate. Log in to reply |
6M64 odd behaviour 13/03/2023 at 15:53 #150804 | |
HST125Scorton
![]() 1167 posts ![]() |
Fixed for the next version. 6M64 was missing a pass tick for Milford Jn. Although this didn't happen when I was testing the timetable. Could you provide me with a save before 23:20 so I can verify.
Aaron (AJRO) | Timetable Writer Log in to reply The following user said thank you: bugsy |
6M64 odd behaviour 13/03/2023 at 16:26 #150806 | |
bugsy
![]() 1732 posts |
HST125Scorton in post 150804 said:Fixed for the next version. 6M64 was missing a pass tick for Milford Jn. Although this didn't happen when I was testing the timetable. Could you provide me with a save before 23:20 so I can verify.I have attached the 23:00 and 23:10 saves ![]() Post has attachments. Log in to view them. Everything that you make will be useful - providing it's made of chocolate. Log in to reply |
6M64 odd behaviour 13/03/2023 at 17:00 #150810 | |
HST125Scorton
![]() 1167 posts ![]() |
Thank you running the 2310 save and adding in the missing tick for 6M64 sees the train behave and continues as normal through Milford Jn towards Stafford.
Aaron (AJRO) | Timetable Writer Log in to reply |
6M64 odd behaviour 13/03/2023 at 17:01 #150811 | |
9pN1SEAp
![]() 1140 posts ![]() |
I can replicate the bug with trains erroneously timed to stop at Milford Jn (LS3571), from the 2310 save. F2 show that the train was direction Down before stopping and when stopped. A granted MA shows the train moving wrong-way despite F2 still showing Down. Jamie S (JAMS) Log in to reply |
6M64 odd behaviour 13/03/2023 at 17:05 #150813 | |
HST125Scorton
![]() 1167 posts ![]() |
9pN1SEAp in post 150811 said:I can replicate the bug with trains erroneously timed to stop at Milford Jn (LS3571), from the 2310 save.Indeed this is what I did to verify, I added in the missing tick for Milford Jn on 6M64 and it carried on but without the passing ticking tick it does what you mentioned. Aaron (AJRO) | Timetable Writer Log in to reply |
6M64 odd behaviour 13/03/2023 at 18:35 #150814 | |
pedroathome
![]() 906 posts |
Mantis 38288 applies for the sim issue - It looks like there are a couple tracks with Up & Down incorrectly defined in this area. Probably never spotted because people hasn't had a train booked to call there before (Ignoring HST125's comment about it being a mistake for the purposes of this comment) James Log in to reply The following user said thank you: bugsy |