Force join

Force Join isn't practical, as the behaviour once the two trains join is undefined. Which of the two timetables does the new slightly longer train follow. For every compelling argument to follow train Y's TT, there's one for train Z.

Surely SimSig can marry the new headcode to its TT.

But I can see a scenario where this would be a very good idea - in order to restore normal running after a perturbation. In fact I'd go further and advocate a 'Split train' option as well.

A completely hypothetical example. Imagine a Kings X/Peterborough multiplayer chain. There has been disruption leading to late running on the up and a 4-car set is at the Cross waiting to depart for P'boro when the fitters are called to the wrong food trolley. By the time it's sorted (they have to test their handiwork, of course :whistle: ), the inward working for the following P'boro (another 4-car) is not far away; the late running is now coming under control and, with a quicker-than-usual turnround the second P'boro will be not far off right time away.

With a 'Force join' option, the two trains can be coupled. The earlier P'boro gets cancelled and an 8-car set departs for Peterborough only a few minutes late.

Control now instructs Hitchin to use the 'Split train' option to detach the rear 4 cars, which now take up their back working. You would need to shunt the detached portion across to the up side (and you might need to hold it somewhere out of the way for a few minutes too - Biggleswade might have to do a bit of regulating to make the space for you). The consequence is that, in this closed system, trains can end up back on their planned diagram with minimal further disruption.

Any thoughts?

But you can do all this by amending the relevant timetables of the trains involved

" said:

But you can do all this by amending the relevant timetables of the trains involved

I think the issue here is one of convenience (operational flexibility), and not the actual ability to do it.

Train A is signalled into platform, scheduled to join train B. You then signal train C into the platform, preventing train A from ever being able to see train B. Then to compound the situation instead of holding train B outside the station to allow C to depart, you go and shove that into the platform as well?

I think the issue here is one of convenience (operational flexibility), and not the actual ability to do it.

A 'split train' feature is probably as useful as 'force join', potentially helpful and negating the need to edit to edit timetables.

The problem with both is the resulting train(s) are undefined.

Force Join isn't practical, as the behaviour once the two trains join is undefined. Which of the two timetables does the new slightly longer train follow. For every compelling argument to follow train Y's TT, there's one for train Z.

The solution I envisage would be a window with headcode fields for the joiner and the joinee, plus an extra field for the headcode of the new train. Surely SimSig can marry the new headcode to its TT.

As an aside, does SimSig look at the two trains to be joined and decide if they can really be joined together, or does it just let you join any two trains - e.g. an HST and an EMU?

Kev

The solution I envisage would be a window with headcode fields for the joiner and the joinee, plus an extra field for the headcode of the new train. Surely SimSig can marry the new headcode to its TT.

Quote:

Force Join isn't practical, as the behaviour once the two trains join is undefined. Which of the two timetables does the new slightly longer train follow. For every compelling argument to follow train Y's TT, there's one for train Z.

I don't understand why forum members are having problems with this. After all, I occasionally need to order a train to Abandon timetable to ensure it will do exactly what I need it to do, then when it is correctly positioned I order Run to another timetable and resume its original TT. This is no different. Maybe you think I wish to create an entirely new train with a new headcode. No, all I want to do is follow through the original TT so the new train created as the end result will follow the TT allocated for it.

Once again pages and pages of heat and not so much light because one user of SimSig cannot work to TTs, understand the consequences of his/her actions or be bothered to do the real life thing of having to sort out his/her mistakes within the operational confines.

On West Hampstead, I've sent a train that runs-round at West Hampstead onto the wrong goods line, the upshot of which is that half the train is 'outside' the TT location. When the loco tries to re-join, it can't because it's still trying to get to that location. Since the loco was created from a 'DEF:' command, I can't move them and the only option is to move the loco back to the front of the train.

Once again pages and pages of heat and not so much light because one user of SimSig cannot work to TTs, understand the consequences of his/her actions or be bothered to do the real life thing of having to sort out his/her mistakes within the operational confines.

...

Unless people try things (or are frightened to try things and have to look for a technical quick-fix to dodge the consequences of their own actions) they will never develop the experience or capability to take full advantage of what SimSig has to offer.

What this situation brings to mind would also be the ability to lengthen as well as shorten trains, at least when the "new" section of the train would take up no more than plain line (I accept it'd be too tricky UI-wise on a junction). In a few circumstances I've had to shorten trains (either through my own fault or a bug in the timetable/sim) - I always think then (especially if the train stays in the sim for quite a while) that it's a shame I can't lengthen them again in order to keep the "unrealistic" parts to a minimum. This feature might also be useful for a "force join" feature in case you end up joining trains where the result is shorter than it should otherwise have been (depending on exactly how it's implemented)

It's possible by creating a train of length x metres (where x is the length you want to add) and editing the timetable of the existing train such that they join.