Decouple number # <kuid2:147570:80008:1> Problem

[NJCurmudgeon]

I posted about this before...I want to be able to decouple a string of cars along a consist. I have the UnCouplezFrom <kuid:66277:80005> command, but it is limited to cars between 0 and 20. I want to be able to decouple a consist at car 35. Someone suggested Decouple number # <kuid2:147570:80008:1> which goes from 1 to 40. However, when I set it to decouple at car 35, it decouples instead at 25. I thought that perhaps it was counting starting from the other end. But when I tried changing it to 40, it still decoupled at 25. Am I missing something here?

Just to clear, I am using this in the following scenario: A shunter couples to the consist and then decouples the string of 35 coal cars from the rest of the train and takes them off to load. I am assuming it is counting the cars starting from the engine.

 

[Kennilworth]

Hi

I've just been playing around with the Decouple number # command on a small test route and it has behaved faultlessly. After coupling to the consist using the CoupleAhead command you need to reverse the train direction before using the decouple command to ensure that it counts back from the engine. If you use the decouple command before reversing direction it will count from the rear of the train.

Regards

Brian

 

[NJCurmudgeon]

Thanks Brian. I will experiment some more. I was wondering if it didn't have something to do with which end it was counting from, so that confirms that may be part of the issues.