Page 1 of 1
| Chaining Rugby South to Watford Junction 06/12/2015 at 17:03 #78465 | |
ajax103
1120 posts |
I am currently running the 15th Oct 2009 00:00 timetables and have chained Watford Junction to Rugby South but have a problem with 2K43 in that both simulations seem to think this service ought to seed in both simulations as per the timetable which is correct to a point however as they are chained together why does Rugby South think it has to seed this train when it ought to only be seeded in the Watford Junction simulation? What I like to know is how do I stop it seeding in Rugby South and have it seed in Watford Junction but then carry onto Rugby South as it ought to That and for some reason I had I believe to be the Rugby South 2K43 call in a change of aspect but I didn't do anything to cause this unless this is part and parcel of the realism I have come to expect ;) I'm just interested to understand how I can resolve the 2K43 issue if anyone here can help me please? Do I change the seed point in the Rugby South sim to none for 2K43? Last edited: 06/12/2015 at 17:04 by ajax103 Log in to reply |
| Chaining Rugby South to Watford Junction 06/12/2015 at 18:44 #78475 | |
Jan
906 posts |
Hmm, good question. Removing the seed train in Watford Jn is no option because then the train would be missing in Rugby in chained mode, whereas converting the seed train to a normal entry in Rugby South isn't exactly desirable either because the simulated entry point is at Watford, so in stand-alone mode the train would actually have to enter before midnight. 4M57 would be similarly affected, except currently it's missing from the Rugby South timetable. I guess what would be needed here is a special option for seed trains which prevents them from seeding if a particular simulation is chained, or maybe the new timetable generating system under development has a solution here? Until that time, you could either edit one timetable to prevent the duplicate seed trains from entering [1], save a copy and then start a new chained game, or simply remove one of the duplicates using the Extreme Measures in the F2 train list. [1] If you edit the Rugby South timetable then yes, set the entry location to "(None)" but don't delete the timetable because it's obviously still needed when the corresponding train enters across the chaining link from Watford Jn. Two million people attempt to use Birmingham's magnificent rail network every year, with just over a million of them managing to get further than Smethwick. Log in to reply |
| Chaining Rugby South to Watford Junction 06/12/2015 at 21:39 #78479 | |
|
JamesN
1608 posts |
They shouldn't be seeded in both simulations. When the Watford TT was written Rugby wasn't considered to be possible, hence its inclusion. Work is in hand to update the WJ/WM 15th October timetables to be much more compatible with the Rugby sims (UIDs etc), however usual timescales apply! My advice for a temporary solution would be to make a copy of the offending timetables purely for chaining, and remove the train from Watford Jn Log in to reply |
| Chaining Rugby South to Watford Junction 06/12/2015 at 22:37 #78484 | |
|
Jan
906 posts |
" said:Hmm, good question. Removing the seed train in Watford Jn is no option because then the train would be missing in Rugby in chained mode, Argh, somehow I didn't read this through properly before posting. By keeping the seed train in Rugby South and removing it from Watford Jn, things will work out, although the trains might seeed slightly early. So it wouldn't necessarily be 100 % perfect, but still a workable compromise. Two million people attempt to use Birmingham's magnificent rail network every year, with just over a million of them managing to get further than Smethwick. Log in to reply |