Tram__ decouple resetter rule I am baffled

[DennR]

I have been trying a session for some friends and I have hit a brick wall. a Manifest train pulls into a well known US rail Yard and decouples wagon 21 using decoupleN2, The Manifest then pulls forward to await some additional wagons. so all is well but when a Shunter tries to couple to the wagon what was decoupled from the Manifest it cannot. I found this link and post 3 from Tram suggest failing to couple after a decouple requires a "resetter rule".
http://forums.auran.com/trainz/showt...light=decouple
I have got the 2.9 version of the rule and tried it in both build 49922 and build 58414 but I cannot get the rule to appear in the commands list or driver rules in Surveyor or in the rules in Driver so I am now in need of some serious Trainz Brainz, something I am clearly lacking. :'( Any and all advice would be very welcome.
Regards
Bob

 

[Pendolino]

This issue has occurred both in TS12 and in Trainz for Mac. This is how Bob and I finally managed to solve it, thanks to Bob's discovery of the Tram post quoted above.

The "Decoupler_Resetter" rule, of course, must be executed after the cars have been decoupled by means of "Decouple N2" and before the couplers involved in the decoupling are involved in a subsequent coupling.

We also found that "Decoupler_Resetter", if placed in an ordered list, prevents the execution of subsequent child rules. When the rules were arranged as shown below, the "Timed Limited Display HTML 6" rule was never executed and the path defined in the "Set Junctions" was never set. As a consequence, the player never received the instructions required to proceed with the session and no path was arranged for the subsequent switching moves.

Possible solutions include:

a) putting the "Decouple_Resetter" on its own, activated by some "check-type" rule;

b) moving the "Decouple_Resetter" at the end of the ordered list, as shown below:

Bob has succesfully tried using the "a" option, and I have used the "b" option: both of them worked fine, allowing Bob and our Mac tester to finally complete the session.

I think this can be of interest to anyone creating US sessions, since "Decouple N2" is the only decouple-type order I know capable of managing US-sized consists.

P.S. This is a development beta version of the session: the "official" version, of course, shall be in English

 

[TRam__]

After release of TS12SP1, "Decouple_Resetter" is no longer need. I've updated commands on DLS,

<kuid2:400260:423246:2>,<kuid2:400260:423247:10>,<kuid2:400260:423241:2>

and they will work correctly without any resetters.

If you are using cloned commands, please, replace their scripts (*.gs - files) with the original ones.

is the only decouple-type order I know capable of managing US-sized consists.

yes, only in US and in Russia exists shunt work with so long consists