Page 1 of 1
| Bristol 15-10-2009 - 0V05 refuses to exit Chipping Sodbury loop 16/01/2014 at 16:28 #53936 | |
Muzer
718 posts |
Just started playing this on this timetable. I have 0V05 (loco just split from 4V05) trying to depart from Chipping Sodbury - however, the train list insists that it's a down train, and so it can't depart because 4V05 is obviously in front! Reversing it doesn't help - it just instantly reverses back again. Any hints on this? The timetable does have a special note on this, but it seems to be for the next part: Owing to a lack of locations in the TT editor, the loco (0V05) that runs round 4V05 at Chipping Sodbury will have to be manually reversed once it is clear of 802 signal. I can't even get it out of the loop! Log in to reply |
| Bristol 15-10-2009 - 0V05 refuses to exit Chipping Sodbury loop 16/01/2014 at 18:47 #53939 | |
|
Muzer
718 posts |
Ah, figured it out. The timing point "Chipping Sodbury East" refers to the east sidings, rather than East of the loop. Manually removing it from the timetable made him cooperate.
Log in to reply |
| Bristol 15-10-2009 - 0V05 refuses to exit Chipping Sodbury loop 16/01/2014 at 19:12 #53941 | |
|
Muzer
718 posts |
Nope - now 0V05 is refusing to join with 4V05. The join is in the timetable, but it's displaying "Train 4V05 in front". Well, yes, that is kind of necessary for a join to happen... but it's not doing it. 4V05 is at "Waiting for joining train 0V05". Help? EDIT: Ah, abandoned then re-adding the join fixed it. Last edited: 16/01/2014 at 19:14 by Muzer Log in to reply |
| Bristol 15-10-2009 - 0V05 refuses to exit Chipping Sodbury loop 16/01/2014 at 20:59 #53944 | |
postal
5264 posts 
|
" said:Nope - now 0V05 is refusing to join with 4V05. The join is in the timetable, but it's displaying "Train 4V05 in front". Well, yes, that is kind of necessary for a join to happen... but it's not doing it. 4V05 is at "Waiting for joining train 0V05". Help?One common cause of joins failing to happen is that the sim doesn't believe that the train is at the location where the join takes place - this sometimes happens after a TT edit or change. It is possible that when 0V05 was refusing to join, the sim thought it was still at a timing point before the join location. You can check this by going into F2 and looking at 0V05's TT. The location which the sim believes is 0V05's current position will be shown in bold type. If you highlight the correct location then click on the "Current/Next Location" button, this updates the sim. It might not be the case with this problem but it is quite a common cause. “In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Last edited: 16/01/2014 at 21:00 by postal Log in to reply |
| Bristol 15-10-2009 - 0V05 refuses to exit Chipping Sodbury loop 16/01/2014 at 21:49 #53946 | |
GeoffM
6376 posts |
Overhanging trains can also do it (too long for the location). if the engine doesn't "arrive" at the join location then it doesn't do the join. This is the subject of a future improvement if the train to be joined to is in front AND the train to be joined to is at the location (even if this train is not at the location).
SimSig Boss Log in to reply The following users said thank you: postal, BarryM |