Page 1 of 1
| 3633 & 3629 31/12/2015 at 13:29 #79439 | |
DaveBarraza
88 posts |
Don't know if this is a bug. 3633 won't come in for the route to 3629, regardless of the state of 3629 (route/no route). 3633 to 3637 comes in as a through-route ("long route?"  and clears 3629 in the process.After this, right clicking 3629 causes 3629 to cancel and re-request which causes both 3633 and 3629 to drop down to stop. Can't tell you what exactly is wrong there, but something seems hinky.... Dave Log in to reply |
| 3633 & 3629 31/12/2015 at 13:31 #79440 | |
headshot119
4869 posts |
Dave it's mostly the correct behavior. This extract from the manual covers it better than I could. Quote: Signal L3633 is unusual in that there is no route from it to the next logical signal, L3629. Instead, route should be set from L3633 to L3637 (or L3635) at Leeds West Junction.I'm not sure that cancelling 3629 should cause the route to bob however. I'll raise a query on the issue tracker. ( #14808) "Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer Last edited: 31/12/2015 at 13:37 by headshot119 Log in to reply The following user said thank you: DaveBarraza |
| 3633 & 3629 31/12/2015 at 23:12 #79450 | |
|
DaveBarraza
88 posts |
Okay that's interesting... (Also I should RTFM) I wonder why one needs a signal at the location of 3629 at all? Log in to reply |