Page 1 of 1
| Approach berths lag? 30/03/2020 at 19:40 #125173 | |
UKTrainMan
1803 posts |
There appears to be a lag at most if not all fringe entry points between when I receive an F3 Messages notification of a train entering the area and the headcode actually appearing in the relevant APPR berth. This is especially difficult for regulation purposes at locations such as Rugeley Trent Valley station, Colwich junction, Trent Valley Junction (for trains from Bushbury junction), and finally Kidsgrove station. Sometimes it takes a minute or more for the headcode to appear. Is this a known simulation or perhaps core code issue? If merely a simulation based issue, could this please be improved upon? I don't really have the time, at 8am or 9am with around 25 trains on the go at once, to go near to that location and have to manually interpose the headcode somewhere such that I can check the timetable for any clashes between train timing points, particularly at somewhere such as Colwich Jn or Kidsgrove station. 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. Last edited: 30/03/2020 at 19:41 by UKTrainMan Reason: None given Log in to reply |
| Approach berths lag? 30/03/2020 at 19:43 #125174 | |
headshot119
4869 posts |
It reflects the reality of when the TDs would appear on the real workstation / panel, so is neither a core code, nor a simulation issue.
"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 |
| Approach berths lag? 30/03/2020 at 19:54 #125176 | |
|
UKTrainMan
1803 posts |
headshot119 in post 125174 said:It reflects the reality of when the TDs would appear on the real workstation / panel, so is neither a core code, nor a simulation issue.So should I really be receiving a message/notification of the train approaching/entering the area if I don't have a visual display of the train approaching the area in the first place through the APPR berths or anything else? Very unusual to have such a time gap of a minute or more before the APPR berth is filled. 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 |
| Approach berths lag? 30/03/2020 at 19:54 #125177 | |
|
Albert
1315 posts |
Also affects York, where there the delay between train entering and appearing is even larger (for trains from Northampton and Harrogate). I can't find the relevant topic at the moment but it has probably already been discussed in the York section of the forum.
AJP in games Log in to reply |
| Approach berths lag? 30/03/2020 at 19:54 #125178 | |
GeoffM
6376 posts |
This has been the case for 20 years or so. If the strike-in for a signalbox is in between timing points that are a good distance apart then the sim will show the train entering at the previous timing point, while the strike-in will show later. The alternative would be to alter every single timetable to predict when the train would get to the strike-in point which, frankly, isn't going to happen. You can ignore the messages window message if you really want to. SimSig Boss Log in to reply |
| Approach berths lag? 31/03/2020 at 11:15 #125200 | |
|
Sacro
1171 posts |
Albert in post 125177 said:Also affects York, where there the delay between train entering and appearing is even larger (for trains from Northampton and Harrogate).Given the distance from York to Northampton I'm not surprised there's a delay! Last edited: 31/03/2020 at 11:15 by Sacro Reason: None given Log in to reply |
| Approach berths lag? 31/03/2020 at 11:27 #125205 | |
|
Woodhead Signalman
64 posts |
Lol true :))
Log in to reply |