Rule for Uncouple/Decouple

davidakridge

Session Creator
Why is there not a rule for uncoupling assets? If you are trying to make a session that can be run entirely from the cab, there's a problem. You have to leave the cabview to uncouple the cars and go back into cabview. This is the conductors job not the engineer. (not important really)

You can have a session that uses a trigger to "Set Junctions" or "Uncouple" and AI train or other functions.

There should be rule that can be placed as a child rule after "Wait for train to Stop" and then uncouples at a specified point. Then the user could stop from the cabview and get a message to pull forward with the cars uncoupled and never leave the cabview.

Just asking!!
 
There are several driver commands that uncouple. My favorite is UnCouplezFrom,<kuid:66277:80005> by smilelyman. This will uncouple automatically the nth car back that you specify in the command. The only problem is it is limited to 20 cars. Sure wish it would go to at least 40 cars and 80 would be better.
 
Built into TS2010, all you have to do is activate it in driver commands for the session. Works fine for AI trains, dunno if it would work for a player train or not. One idea, back into the siding or spur where you want to set out the car or cars, open the F6 driver window and right click in it, order yourself to Uncouplez From #14 or whatever?
 
. . . Works fine for AI trains, dunno if it would work for a player train or not. . . .

I have found that all drive commands work for a player train. The thing is you loose control while it implements the command. If you stop the train where you want to uncouple, issue the command, right click on the driver command window and select Drive Schedule or continue schedule or something like that, the command will imlement instantly and with no more commands in the window, it reverts back to player control
 
Yep. Just now tried it, difficult to see what's happening unless you're on a curve and use the head out of window view. Open the session rules, edit Driver Commands, scroll down to Uncouplez From and tick it on. Save, exit, run session. Now if you know the number of the car (and it's no further back than #20) hit the F6, right click in the F6 window to bring up the menu, select Uncouplez From and pick a number. DCC controller pops up and the train stops if it's moving, Uncouplez From command disappears from the F6 window, DCC controller disappears. Pull forward while looking back in one of the head out views and you'll see you left that car (and all the cars aft of it) behind.
 
There is a command that will uncouple from 40 cars to engines.
It's decouple number <kuid2:147570:80008:1>
This works just the oppedes of the uncouple from # <kuid:6627:80005>
BTW, i use the stop command (not the one at top of commands) to make sure that the breaks are set before i uncouple.
Stop command is <kuid:131986:150150>
A nother command is train product & information. By right clicking on any driver you will get a list of what that driver is hauling,size of load. (tonne)
If you are driving one train and want to see what on another train is hauling R C on a any driver it won't take you away from the train you are driving.
<kuid:478659:1058>(TS12 only)
All should be on the DLS.
 
Last edited:
Yep. Just now tried it, difficult to see what's happening unless you're on a curve and use the head out of window view. Open the session rules, edit Driver Commands, scroll down to Uncouplez From and tick it on. Save, exit, run session. Now if you know the number of the car (and it's no further back than #20) hit the F6, right click in the F6 window to bring up the menu, select Uncouplez From and pick a number. DCC controller pops up and the train stops if it's moving, Uncouplez From command disappears from the F6 window, DCC controller disappears. Pull forward while looking back in one of the head out views and you'll see you left that car (and all the cars aft of it) behind.

Yep Sniper it worked for me also. Not 100% what I wanted but at least I can run the session from inside the cab. thanks for the info.
 
There is a command that will uncouple from 40 cars to engines.
It's decouple number <kuid2:147570:80008:1>
This works just the oppedes of the uncouple from # <kuid:6627:80005>
BTW, i use the stop command (not the one at top of commands) to make sure that the breaks are set before i uncouple.
Stop command is <kuid:131986:150150>
A nother command is train product & information. By right clicking on any driver you will get a list of what that driver is hauling,size of load. (tonne)
If you are driving one train and want to see what on another train is hauling R C on a any driver it won't take you away from the train you are driving.
<kuid:478659:1058>(TS12 only)
All should be on the DLS.

Danny, Thanks for the uncouple from #. It sure is hard to keep up with everything that is available on the DLS.
 
Don't know if this is helpful, but I found that if I put a "Wait for 5 seconds" command before the decouple command in Trainz2009, the train comes to a complete stop and then decouples. I was having an issue where it would decouple but momentum meant the decoupled consist kept rolling - a problem when I was designing a yard with a bunch of cars all close together!
 
Back
Top