Page 1 of 1
| Issue with train reported at wrong location 13/02/2023 at 16:33 #150454 | |
ajax103
1120 posts |
Last night on a test session for a upcoming Wembley Mainline timetable, I was signalling a train that entered on the Down West London (Kensington Olympia) towards Willesden Junction High Level and noticed something that I believe was a bug. Now the train itself was observed as occupying track section TVCGF and waiting for the route at signal 811 however the train list and the driver both were stating that they were occupying track section TR and waiting for the route at signal 809. Surely if track section TVCGF is occupied by a train and waiting for the route to be set than surely it should be reported as being at signal 811? Track section TR was completely blank and not shown as occupied hence explaining why I think this is a bug. Log in to reply |
| Issue with train reported at wrong location 13/02/2023 at 16:47 #150457 | |
headshot119
4869 posts |
Having just run some debug trains in from Kensington Olympia I'm not able to reproduce what you are reporting here. Without a save game taken at the time, it's very difficult to diagnose issues like this after the event. "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 |
| Issue with train reported at wrong location 13/02/2023 at 17:37 #150459 | |
|
ajax103
1120 posts |
I don't have access to the save as I was not hosting but during your fault finding, are you stating that trains sat at signal 809 is occupying track section TR and is clearly shown visible as occupying said track section?
Log in to reply |