Page 1 of 2
| 5R03 at OY10... strange 20/03/2014 at 16:00 #57470 | |
kbarber
1742 posts |
Save attached with 5R03 waiting at OY10 (having rung in to Wolves already... surely that shouldn't happen?). [attachment=2305]004-0521.ssg[/attachment] OY10 never seems to clear... 5R03 sits there blocking everything coming from Oxley (at least until 05:40, I gave up at that point). Current/next is shown as Wolves North Junction. Restarting from this save, I authorised 5R03 to pass OY10 (via F2). It seems to start moving then reverses to the down direction. I reversed it manually and it did the same again. Editing timetable (to show Wolves this time) achieved nothing. Then 5R03 seems to disappear out of the sim altogether, although it remains visible in F2. Any thoughts? Post has attachments. Log in to view them. Log in to reply |
| 5R03 at OY10... strange 20/03/2014 at 16:06 #57471 | |
|
kbarber
1742 posts |
Update: at 05:28 5R03 appeared at 34 signal, without any description!
Log in to reply |
| 5R03 at OY10... strange 20/03/2014 at 16:13 #57473 | |
|
Late Turn
699 posts |
Sounds a little bit similar to my problem (see 'Stafford Road Jn' thread), although mine did at least get moving once the freight off the Up Oxley Chord had cleared the junction. Did you have anything signalled onto the Up Oxley Chord at the time?
Log in to reply |
| 5R03 at OY10... strange 21/03/2014 at 10:20 #57516 | |
|
kbarber
1742 posts |
I certainly wondered if that might be anything to do with it. I'd sent 6G58 that way and I suspect it was on the Chord when 5R03 entered the sim. But by 05:21 when I did the save 6G58 was out of the sim and 5R03 had been stood at OY10 for the best part of 10 minutes - and remained there without any sign of movement. I wonder if the reason it went the wrong way was that because Oxley didn't pull off for the stock the road was left set towards Oxley Jcn after 6G58. That might make sense of why it appeared to change direction after I talked it by OY10. So there's some problem, it would appear, with Oxley... time to send a DI over and wake the bobby up methinks 
Log in to reply |
| 5R03 at OY10... strange 21/03/2014 at 17:08 #57532 | |
GeoffM
6376 posts |
This behaviour was observed during testing but very random and unpredictable so the cause has yet to be found.
SimSig Boss Log in to reply |
| 5R03 at OY10... strange 21/03/2014 at 17:10 #57533 | |
|
kbarber
1742 posts |
" said:This behaviour was observed during testing but very random and unpredictable so the cause has yet to be found. Thanks Geoff... so it is my old partner in crime **** *********** nodding off on nights then?! :dry: Log in to reply |
| 5R03 at OY10... strange 21/03/2014 at 20:11 #57536 | |
|
delticfan
476 posts |
Sounds similar to the problem with 5R03. I've just had a message '1G93 stood at OY10.' I authorise driver to pass at danger to see what happened. 1G94 now stood at sig 34 on Oxley Chord and is going to need reversal to call at Wolverhampton. Confused.com. Mal. Log in to reply |
| 5R03 at OY10... strange 21/03/2014 at 21:26 #57540 | |
|
Stephen Fulcher
2078 posts |
I have just had the same issue. Save attached.
Post has attachments. Log in to view them. Log in to reply |
| 5R03 at OY10... strange 24/03/2014 at 16:27 #57679 | |
|
whatlep
377 posts |
I've experienced the same problem with 1G93 and a similar one with train 1J12 in the opposite direction which gets "stuck" at the first signal after Wolverhampton North Junction. If 1J12 is authorised to pass the OY signal at danger, the driver telephones to report that "the points are wrongly set" and requests that reversal be permitted. Seems there is a bug at the pointwork? File attached with 1G93 about to get terribly confused! Post has attachments. Log in to view them. Log in to reply |
| 5R03 at OY10... strange 24/03/2014 at 18:27 #57684 | |
|
whatlep
377 posts |
Update with more data. The issue seems to be directly related to trains using the Bushbury-Oxley curve at the same time as an arrival is due from Oxley. The attached files show that, in contrast to my last post, if 6G07 is held at Bushbury until 1G93 appears in the approach display, everything works fine. Put another way, holding trains at Bushbury to check for any incoming Up Shrewsbury train seems to be the work-around pending a bug fix. Next to figure out if the same works for Down Shrewsbury trains hot on the tail of freights (e.g. 1J12)! Post has attachments. Log in to view them. Log in to reply |
| 5R03 at OY10... strange 24/03/2014 at 19:12 #57687 | |
|
delticfan
476 posts |
" said:I've experienced the same problem with 1G93 and a similar one with train 1J12 in the opposite direction which gets "stuck" at the first signal after Wolverhampton North Junction. If 1J12 is authorised to pass the OY signal at danger, the driver telephones to report that "the points are wrongly set" and requests that reversal be permitted. Seems there is a bug at the pointwork?Thanks Whatlep. I had the same prob with 1J12. Departs Wolves ok then gets stuck in the same place. I'll certainly try that one on my next run of the TT. Mal. Log in to reply |
| 5R03 at OY10... strange 24/03/2014 at 20:14 #57693 | |
|
Late Turn
699 posts |
" said:Update with more data. The issue seems to be directly related to trains using the Bushbury-Oxley curve at the same time as an arrival is due from Oxley. The attached files show that, in contrast to my last post, if 6G07 is held at Bushbury until 1G93 appears in the approach display, everything works fine. I can also confirm that holding the freight at Bushbury avoids the problem (though I tried it with a different freight, to the slight distress of a following Up Stour passenger that just caught a YY approaching Bushbury as a result). Only really suitable as a short term workaround, of course - anything booked to stand on the chord, or in disruption, could go horribly wrong! Log in to reply |
| 5R03 at OY10... strange 24/03/2014 at 21:59 #57704 | |
|
whatlep
377 posts |
" said:" said:I've now rechecked and there doesn't appear to be anything amiss with 1J12 itself. It's just disappeared towards Cosford accelerating happily!I've experienced the same problem with 1G93 and a similar one with train 1J12 in the opposite direction which gets "stuck" at the first signal after Wolverhampton North Junction. If 1J12 is authorised to pass the OY signal at danger, the driver telephones to report that "the points are wrongly set" and requests that reversal be permitted. Seems there is a bug at the pointwork?Thanks Whatlep. I had the same prob with 1J12. Departs Wolves ok then gets stuck in the same place. I'll certainly try that one on my next run of the TT. I can only conclude that in the hidden settings for Stafford Road Jn's points, something gets "stuck" when a freight train is around on the curve and takes "x" minutes to free itself. Any service to/from Wolverhampton which comes along during the "sticky" period itself then gets stuck and enters a world of woe and despair. Not entirely unrealistic.... B) Log in to reply |
| 5R03 at OY10... strange 24/03/2014 at 22:06 #57705 | |
|
Danny252
1461 posts |
" said:Any service to/from Wolverhampton which comes along during the "sticky" period itself then gets stuck and enters a world of woe and despair. Not entirely unrealistic.... B)Certainly quite realistic for going towards Wolverhampton, at least... Log in to reply |
| 5R03 at OY10... strange 04/04/2014 at 20:38 #58400 | |
|
kbarber
1742 posts |
I wonder if I may have caught it in the act... 6G07 seemed to wait on the Oxley Curve, as if Oxley was holding him for 1G93-A. Then it moved off and at the same moment 1G93 showed waiting at OY10. [attachment=2368]oy10-1g93a-0905.ssg[/attachment] A couple of minutes later, 6G07 is well on his way to Cosford (making 53mph) but 1G93 remains stuck at OY10. [attachment=2369]oy10-1g93a-0907.ssg[/attachment] I authorised 1G93 past OY10 then returned 57 signal to danger. By rights that should've given 1G93 an ACOA shouldn't it? But clearly the points at Stafford Road were set towards Bushbury because all I got was the approach locking timing out. [attachment=2370]oy10-1g93a-09011.ssg[/attachment] (I think I mean't to type 0911 as the time.) 1G93 then headed up to 34 signal and had to be reversed in Bushbury Loop. Maybe that will give enough to track down the problem. Intuitively it looks as if there's a problem with route OY10B; is that approach released? If so, I wonder if that's allowing Oxley to run a freight off the Curve at the last minute ahead of an approaching passenger but that somehow leaves OY10B unable to set and the junction points the wrong way to just call it by? Post has attachments. Log in to view them. Log in to reply |
| 5R03 at OY10... strange 04/04/2014 at 20:48 #58402 | |
|
GeoffM
6376 posts |
Thanks for the investigation. However, I can unreliably reproduce it with just a single stream of up trains to Wolverhampton, i.e. all going the same way with no other trains around. It's supposed to just re-evaluate route availability every few seconds and set the appropriate route if available. All very simple but I've probably got something really silly in there that I'm just not spotting. SimSig Boss Last edited: 04/04/2014 at 20:49 by GeoffM Log in to reply |
| 5R03 at OY10... strange 05/04/2014 at 07:32 #58426 | |
|
kbarber
1742 posts |
" said:Thanks for the investigation. However, I can unreliably reproduce it with just a single stream of up trains to Wolverhampton, i.e. all going the same way with no other trains around. Thanks Geoff, I'll not clog the forum further. It's probably just a typo or summat... I know how difficult they can be to spot! And of course better people than us never did get their heads around it until they had spellcheckers, that's why a certain daily newspaper still gets called The Grauniad around these parts! Log in to reply |
| 5R03 at OY10... strange 17/04/2014 at 23:51 #59048 | |
|
GeoffM
6376 posts |
I've found this now - actually a core code bug rather than a Wolverhampton data issue. It'll be fixed in V4.0.31 of the Loader (might be 4.1 as there are some big changes under the hood).
SimSig Boss Last edited: 17/04/2014 at 23:51 by GeoffM Log in to reply The following users said thank you: Temple Meads, Steamer, kbarber, MikeW |
| 5R03 at OY10... strange 18/04/2014 at 00:04 #59049 | |
Temple Meads
307 posts |
" said:I've found this now - actually a core code bug rather than a Wolverhampton data issue. It'll be fixed in V4.0.31 of the Loader (might be 4.1 as there are some big changes under the hood).Great news, and strangely I was thinking about this bug just before you posted this! Username TIM in multiplayer Log in to reply |
| 5R03 at OY10... strange 18/04/2014 at 16:00 #59069 | |
|
njimiller
141 posts |
Looking forward to it Geoff! Nick Log in to reply |
| 5R03 at OY10... strange 27/04/2014 at 17:26 #59619 | |
|
delticfan
476 posts |
Further to previous reports of problems with OY10 on the default TT I'm running the 2014 TT from Steamer and had a similar thing happen. So far, it has been trains 5R14 and 5R16. I have instructed both to pass OY10 at Danger and they have arrived between 5 to 10 minutes late. Other services due to arrive on Up Shrewsbury appear with no problem. Mal. Log in to reply |
| 5R03 at OY10... strange 27/04/2014 at 19:06 #59622 | |
|
JamesN
1607 posts |
Mal, the issue has been identified as an issue with the loader, rather than specifically the simulation/timetable concerned. An update to loader to fix this will be released in due course. Log in to reply The following user said thank you: delticfan |
| 5R03 at OY10... strange 27/04/2014 at 20:09 #59628 | |
|
delticfan
476 posts |
" said:Mal,Thanks James, I probably read the previous information a bit wrong. Mal. Log in to reply |
| 5R03 at OY10... strange 19/07/2014 at 21:08 #62893 | |
|
njimiller
141 posts |
I notice this issue is still happening even with 4.1.2 of the loader. Geoff, does this require a sim update to fix this as well? Cheers, Nick Log in to reply The following user said thank you: Temple Meads |
| 5R03 at OY10... strange 08/01/2018 at 23:31 #104919 | |
|
GeoffM
6376 posts |
njimiller in post 62893 said:I notice this issue is still happening even with 4.1.2 of the loader. Geoff, does this require a sim update to fix this as well?Is anybody still getting this? SimSig Boss Log in to reply |