6M22 West Hampstead

You are here: Home > Forum > Simulations > Released > West Hampstead > 6M22 West Hampstead

Page 1 of 1

6M22 West Hampstead 17/11/2013 at 00:02 #51629
AlexH
Avatar
163 posts 		Great simulation, thank you to those who created it. Finally one that emerges away from exam time.

6M22 entered, then did something odd. I sent it off to the Signal 533 section part to run round. But it stopped fouling the mainline and detatched loco. Which obviously can't happen as it's trailing the points. Slightly annoying. A bug? What should I do? I can't make it move forward the loco has detatched.
Log in to reply
6M22 West Hampstead 17/11/2013 at 00:35 #51631
John
Avatar
884 posts 		This timetable issue has already been highlighted here but only partially addressed, I'm afraid.

In the end, I resolved the situation to my satisfaction by nuking 6M22 with my "remove train" button.
Log in to reply
6M22 West Hampstead 17/11/2013 at 00:45 #51632
AlexH
Avatar
163 posts 		Ah, I didn't see that, the search function was mucking up. The internet and electricity is always dropping out with this storm. Kenyan technology barely allows me to download the stuff, let alone deal with the website.

That's a shame, though. Especially given the cost of the simulation. I will nuke the train and wait for an update which fixes it.
Log in to reply
6M22 West Hampstead 17/11/2013 at 01:41 #51633
AndyG
Avatar
1843 posts
Online 		Fix required is:-
6M22:- Edit RR location to W Hampstead North Jn (FX exact works OK);
0M-R:- Edit to:
i) W Hamptead N Jn;
ii) W Hampstead Thameslink (Line DH);
iii) Cricklewood P1 (Dep/Rec might work, but not tested);
iv) W Hampstead North Jn J:6M22.

As this requires the RR to cross over the main lines, I think a better location would be to RR at W Hampstead Thameslink, but not tried that out (yet!).
I can only help one person a day. Today's not your day. Tomorrow doesn't look too good either.
Log in to reply
The following users said thank you: John, AlexH, ajax103
6M22 West Hampstead 17/11/2013 at 02:03 #51634
AndyG
Avatar
1843 posts
Online 		Yes, Plan B works too (and is at the RR location marked on the panel).

6M22 edit RR location to W Hampstead Thameslink Plt RRL, {FX seems to be fine, default stop may well work};

0M22-R to be:-
1) W Hampstead Thameslink d00:00 Plt RRL;
2) Signal 529 d00:00;
3) W Hampstead Thameslink 00/00 Plt DH;
4) signal 562 d00:00;
5) W Hampstead Thameslink Plt a00:00 RRL J:6M22.

Worked for me B)
I can only help one person a day. Today's not your day. Tomorrow doesn't look too good either.
Last edited: 17/11/2013 at 02:04 by AndyG
Log in to reply
The following users said thank you: ajax103, NCC1701, Dick, AlexH, Temple Meads
6M22 West Hampstead 17/11/2013 at 10:22 #51641
AlexH
Avatar
163 posts 		Ok thank you AndyG for the help.

I'm sure this might be a silly question, but the train is already in the sim and the engine has detached itself. Is there now anyway to fix the problem. I don't seem to have a save until hours before the train enters.
Log in to reply
6M22 West Hampstead 17/11/2013 at 10:26 #51642
TimTamToe
Avatar
664 posts 		" said:
Ok thank you AndyG for the help.

I'm sure this might be a silly question, but the train is already in the sim and the engine has detached itself. Is there now anyway to fix the problem. I don't seem to have a save until hours before the train enters.
just a thought...you could edit the timetable (via F2) to have the loco attach to the wagons at the location you are at now and then follow Andy's advice

Gareth
Log in to reply
6M22 West Hampstead 29/01/2014 at 17:42 #54516
Javelin395
Avatar
274 posts 		" said:
Yes, Plan B works too (and is at the RR location marked on the panel).

6M22 edit RR location to W Hampstead Thameslink Plt RRL, {FX seems to be fine, default stop may well work};

0M22-R to be:-
1) W Hampstead Thameslink d00:00 Plt RRL;
2) Signal 529 d00:00;
3) W Hampstead Thameslink 00/00 Plt DH;
4) signal 562 d00:00;
5) W Hampstead Thameslink Plt a00:00 RRL J:6M22.

Worked for me B)

I'm having problems with this fix. Probably me being dim but I have checked and re-checked that I have modified the TT exactly as above but the rear of 6M22 stands foul of WH531. Guessing it must work for other people going on the thanks posted so any suggestions as to what I am doing wrong would be gratefully received.
Log in to reply
6M22 West Hampstead 30/01/2014 at 00:22 #54565
sloppyjag
Avatar
480 posts 		I've just encountered this using the recently re-released 2009 timetable. First thing I did was go and check the details for 6M22 as I'd amended it in the previous version and it did work in that version but not in this version. It would appear that in the first version 6M22 was 400m lomng but in the new version it is 433m long and will not fit into either loop at West Hampstead (RRL or DH - 430m according to Wiki) or Down Hendon (WH562-WH441) (380m).

So apart from shortening the train I'm not sure what can be done.
Planotransitophobic!
Log in to reply
The following user said thank you: Javelin395
6M22 West Hampstead 30/01/2014 at 15:35 #54601
sloppyjag
Avatar
480 posts 		Loathed as I am to shorten trains I battled on and worked out how to do this without shortening the train from 433m. Train needs to be signalled beyond WH556 into the spur but leaving enough room at end of the loop for the loco to join at the other end. So;

6M22 - edit RR location to West Hampstead Thameslink (Plt RRL) stopping position, Near and Exact/Adjustment 18. (NX@18)

OM22-R - edit as per AndyG's post.

Remember to signal 6M22 past the loop into the spur.

When 0M22-R runs round and joins at the other end it will overhang at WH531 but enough of the loco has arrived at its joining location for the join to commence. Driver will phone for authority to proceed when 6m22 is ready to depart.
Planotransitophobic!
Log in to reply
The following user said thank you: Javelin395
6M22 West Hampstead 30/01/2014 at 16:50 #54611
JamesN
Avatar
1611 posts 		Or you could just try doing the Run Round in the correct place :P

The train should be signalled to 444, and do the Run Round there. This was picked up in testing and I thought the TT had been ammended to reflect this (it's where Run Rounds happen IRL)

See screenshot:
Post has attachments. Log in to view them.
Log in to reply
6M22 West Hampstead 30/01/2014 at 16:57 #54614
Javelin395
Avatar
274 posts 		" said:
Loathed as I am to shorten trains I battled on and worked out how to do this without shortening the train from 433m. Train needs to be signalled beyond WH556 into the spur but leaving enough room at end of the loop for the loco to join at the other end. So;

6M22 - edit RR location to West Hampstead Thameslink (Plt RRL) stopping position, Near and Exact/Adjustment 18. (NX@18)

OM22-R - edit as per AndyG's post.

Remember to signal 6M22 past the loop into the spur.

When 0M22-R runs round and joins at the other end it will overhang at WH531 but enough of the loco has arrived at its joining location for the join to commence. Driver will phone for authority to proceed when 6m22 is ready to depart.

Cheers sloppyjag. I had considered abandoning TT then signalling forward into the spur but thought that would trap the loco running round. Didn't know about NX@ command. For now I have adjusted the TT to reduce the length of 6M22 and set the locations as per AndyG's post but I share your dislike for shortening a train. Not exactly true to life (which is one of SimSigs raison d'etre).
Last edited: 30/01/2014 at 16:58 by Javelin395
Log in to reply
6M22 West Hampstead 30/01/2014 at 17:56 #54629
sloppyjag
Avatar
480 posts 		" said:
Or you could just try doing the Run Round in the correct place :P

The train should be signalled to 444, and do the Run Round there. This was picked up in testing and I thought the TT had been ammended to reflect this (it's where Run Rounds happen IRL)

See screenshot:

How are we supposed to know it's been fixed? There has been no mention of it being fixed (until now) in either of the two threads on the subject or in the thread announcing the updated timetables PLUS the tt for 0M22-R still has the superfluous Cricklewood entry which is confusing and made me think this hadn't been fixed PLUS the Wiki suggests that the loop there is only 380m long (although admittedly does not specifically state the section between WH444 and WH531.)

Anyway, I had fun sorting it out by myself.
Planotransitophobic!
Log in to reply
6M22 West Hampstead 30/01/2014 at 18:16 #54634
John
Avatar
884 posts 		Is the bug board where bugs are logged publicly viewable, or is it a devs only area?
Log in to reply
6M22 West Hampstead 30/01/2014 at 19:35 #54650
JamesN
Avatar
1611 posts 		Quote:
How are we supposed to know it's been fixed? There has been no mention of it being fixed (until now) in either of the two threads on the subject or in the thread announcing the updated timetables PLUS the tt for 0M22-R still has the superfluous Cricklewood entry which is confusing and made me think this hadn't been fixed PLUS the Wiki suggests that the loop there is only 380m long (although admittedly does not specifically state the section between WH444 and WH531.)

Anyway, I had fun sorting it out by myself.
Alright alright - potentially I have a newer version of the TT then, with this fix in. It was only in attempting (unsuccesfully) to reproduce the issue that I discovered this was the way to do it. I've given Noel a prod and I'm sure a fix will be produced shortly to sort this out once and for all.

" said:
Is the bug board where bugs are logged publicly viewable, or is it a devs only area?
Developers (and their Testers) only I'm afraid John.
Log in to reply
6M22 West Hampstead 01/02/2014 at 18:10 #54798
Javelin395
Avatar
274 posts 		Not sure I'm quite getting what is being said here. Let me see if this is where we are at....


6M22 should be signalled to WH444 on the Up Hendon where loco will detach BUT

as already noted rear of train then fouls Down Fast

so how should I amend the TT ?
Log in to reply
6M22 West Hampstead 01/02/2014 at 19:49 #54802
sloppyjag
Avatar
480 posts 		OK, figured this one out. If you leave the stopping position at Sig WH531 as FX 6M22 will stop at the end of TC266 (the small track circuit on the right hand end of the loop) rather than T260 (the larger circuit on the left hand side) leaving the train fouling the fast line. (Is this a bug?) To get round this set the stopping position to near and exact plus room for the loco - I found NX@26 worked fine.

0M22-R has an extra location at Cricklewood presumably because there is no valid path between WH531 and West Hampstead Thameslink RRL when validating the timetable. Delete this extra "Cricklewood" - the timetable wont validate but it does work.
Planotransitophobic!
Last edited: 01/02/2014 at 19:50 by sloppyjag
Log in to reply
The following users said thank you: thickmike, Javelin395, Tempest Malice
Back