SplitConsist

SplitConsist

Yet another but highly flexible uncouple command for splitting a train into two consists. Depending on user's convenience, this command includes four sub menus to perform the uncoupling operations. These sub menus are named as 'Train (conceptual)', 'locomotive (conceptual)', 'locomotive (natural)', and 'locomotive (DCCGear)'. Each menu contains a list of vehicle numbers as explained below.

The first sub menu, 'Train (conceptual)', is used to split the train from a vehicle counted backwards from the conceptual leading (front) end of the Train. The vehicle numbers start from 0. as being the first vehicle in the front. and increase in the ascending order towards the conceptual back end of the train. This sub menu is good for both AI and Autopilot trains.

The second menu, 'locomotive (conceptual), is used to split the train from a vehicle counted relative to the driver's locomotive. A positive vehicle number indicates that the vehicle is behind the locomotive, and a negative vehicle number indicates that the vehicle is in front of the locomotive. The vehicle number 0 corresponds to the locomotive by itself. The locomotive direction is identical to the conceptual direction of the train and hence the front and back ends of the locomotive are decided according to the train's conceptual direction. This sub menu is good for both AI and Autopilot trains.


The third sub menu, 'locomotive (natural), is used to separate a consist from a selected vehicle counted relative to the driver's locomotive with forward and backward directions being the locomotive's natural (actual) front and back ends, respectively. Like the second option, a positive vehicle number indicates that the vehicle is behind the locomotive and a negative number indicates that the vehicle is staying in front of the locomotive with vehicle 0 implying the locomotive itself. This sub menu may be used for both AI and Autopilot trains as well as the trains driven by throttle and velocity controlled custom commands such as TCdriveViaTrackmark, VCDriveViaTrackmark, etc., which are available on DLS.

The last sub menu, 'locomotive (DCCGear)', is used to separate the consist from a vehicle counted relative to the driver's locomotive with forward and backward directions being decided by the custom SwitchDCCGear command available on DLS. If this option is used with SwitchDCCGear command being set to 'normal' mode, it becomes identical to the third option, i.e., 'locomotive (natural)'. If SwitchDCCgear command is set to 'reverse' mode prior to employing this command, then the counting direction of the vehicles is reversed. The vehicle counting order is the same as those described in the second and third sub menus (i.e., positive and negative vehicle numbers indicate the vehicles behind and in front of the locomotive, respectively). This sub menu is especially designed for trains driven by throttle and velocity controlled custom commands (e.g., TCDriveViaTrackmark, VCDriveViaTrackmark, etc.) available on DLS.

It is highly recommended that the functions of these sub menus be experimented by creating a consist in a simple layout before applying it to your actual layout. The main advantage of using this command is that the locomotive be located anywhere in any direction in the consist and the train separation be done from any vehicle.

As mentioned at the beginning, each sub menu contains a range of vehicle numbers. It is, however, possible that a vehicle number that you want uncoupling is outside the range of numbers provided in these sub menus. In that case, you need to use the WorkTable rule (available on DLS) to create custom numbers that automatically shows up in these sub menus. In order to create these custom vehicle numbers, do the following. (1) download WorkTable rule from DLS, if you haven't done, (2) Create WorkTable rule in your session and edit it, (3) Add a new line in the table and type the following.

decouple, vehNumber

where vehNumber is the number that shows up in all sub menus of this driver schedule command. Both pos

Author: atilabarut

SplitConsist
• config.txt 6.17KB
• decoupleconsist.texture.txt 41 bytes
• decoupleconsistcommand.gs 11.14KB
• decoupleconsistschedulecommand.gs 5.36KB
• shuntnandcruisnpack.jpg 9.11KB
• tag.tga 64.04KB