The information in this Wiki Page applies to T:ANE, TRS19, Trainz Plus and TRS22.
|
|
The Driver Setup Rule assigns drivers to consists and issues them with Driver Commands |
|
Driver Commands are lists of instructions or "orders" that drivers are tasked to complete under the control of the Trainz AI system |
|
|
A list of available Driver Commands can be found on the Trainz Wiki Page at:-
|
The Driver Setup Rule is automatically added to the Session Editor of every Session.
Adding New Drivers
|
|
|
|
|
|
|
After opening the Driver Setup Rule Left Click the link:-
|
If there is a list of drivers already present then scroll down to the bottom of the list to see the link
|
|
The image on the right shows the properties window if it is opened with no drivers placed in the layout.
This will open the Add New Driver window.
Select a driver from the list and Left Click the Tick button.
|
|
|
Timeout Problem in T:ANE This is an issue in T:ANE. It has been FIXED in TRS19 and later versions.
Adding a large number of drivers to the Driver Setup can cause Timeout errors particularly if certain driver script libraries are being used. Exactly how many is a "large number" will depend on other factors.
|
If Driver Setup Timeout errors are reported, then split the drivers between two copies of the Driver Setup Rule and place the second copy as a child of a Wait Rule set for a delay of just a few seconds, as shown on the right.
This gives Trainz enough time to process all the drivers in the first Driver Setup rule before starting on the second Driver Setup rule.
Information on how to use Parent and Child rules can be found at Parent and Child Rules
|
|
Remove Existing Drivers First
After selecting the Driver Setup Rule Left Click the Edit button, the Driver Setup Properties Window will be shown. The image below shows the properties window if it is opened with no drivers placed in the layout. |
|
If your session uses a rule that will expect to find a particular driver in charge of a train (e.g. driver Charlie in the Trigger Check Rule) then manually assign Charlie as the driver of a train and do not select the option Remove all existing Drivers first.
|
|
Generate New Drivers for Empty Trains
|
|
Settings:
|
If Checked randomly selected drivers will be assigned to all newly added driveable trains. Existing drivers will not be affected unless the Remove all existing Drivers first option has been selected |
|
If Unchecked then you will have to manually assign drivers to trains by a Left Click on the Add another Driver link |
|
|
|
|
Notes:
When using the Driver Setup Rule for the first time with no drivers assigned to existing trains, the Generate new Drivers for empty trains option will immediately assign drivers to each train. Each time a new train is added to the layout, it will be automatically assigned a driver. |
|
|
Wait For Schedule Completion
|
|
Settings:
|
If Checked then this Driver Setup Rule will not complete until all Schedule Rules (if any) have been completed |
|
If Unchecked then this Driver Setup Rule will complete as soon as all its drivers have been assigned locos and commands (if any) |
|
|
Focus Camera on First Driver
|
|
Settings:
|
If Checked then the Session will start with the camera focussed on the first driver in the list |
|
If Unchecked then the Session will start with the camera focussed on the scene that last had the camera focus in Surveyor |
|
|
Editing the Driver List
|
|
|
|
|
|
|
When drivers and trains have been added to the rule, it will appear as shown below.
|
|
If a loco name appears in red then it has been removed from the layout |
|
|
Steps: To edit the driver list:- |
|
Left Click on the driver icon to select a different driver from the Session list |
|
Left Click on the loco name to select a different loco from the Session list (an empty loco list means no unassigned locos are available) |
|
Left Click on the driver name to type in a new name for this driver (this will not change the driver icon) |
|
Left Click on Autodetect to select a new owner for this driver and loco. There are four "owner" options:-
Choose one of the following options:- |
|
AI driver - this train will be under AI control even if it has no Driver Command Bar orders to follow. This can be used to prevent a user from taking control of the train |
|
Autodetect - if the train has Driver Command Bar orders then it will be under AI control. If it has no Driver Command Bar orders then it will be under user control |
|
First Human Player - the train will be assigned to the user or a multiplayer, whoever selects it first |
|
Multiplayer Driver - the train will be assigned to a multiplayer |
|
If you need to remove a driver:- |
|
Left Click remove to delete this driver from the rule |
|
Adding Driver Commands
|
|
|
|
|
|
|
The grey area below the driver details (name, loco, owner) is the Driver Command Bar. This is where the driving instructions (the "train orders") used by the Trainz AI system are given to the driver. |
|
Notes:
When a driver command has been executed in Driver Mode by the Trainz AI system, it will be deleted from the Driver Command Bar and the next command in the sequence will then be executed. This will continue until the last command has been executed and deleted. Then the AI control of the train will terminate.
|
|
Deleting Driver Commands
|
|
|
|
|
|
|
To remove a command from the Driver Command Bar...
|
Steps: To remove a command from the Driver Command Bar:- |
|
Left Click and Drag the command out of the Driver Command Bar area |
|
|
The "Repeat" Command
|
|
|
|
|
|
|
|
The Repeat command is a special built in Driver Command that allows ALL the driver commands to be repeated endlessly |
|
|
Notes:
|
|
The Repeat icon will always be placed at the end of the Driver Command Bar after the Add Command button (>>) |
|
As each command is executed by the Trainz AI system, it will be deleted from the front of the command list and added to the end of the list to create an "endless loop" of commands |
|
|
|
|
Notes:
|
If a Repeat command is already present, then the Add Command menu list will show Don't Repeat as its first option |
|
Select Don't Repeat to remove the Repeat command |
|
|
|
|
Known Issues: This is an issue in T:ANE. It has been FIXED in TRS19 and later versions.
If a Repeat command is present in the Driver Command Bar and all the other commands are then deleted, the Repeat command will remain in the Driver Command Bar and cannot be removed. Because there are no other commands to be repeated this will not cause a problem. However when later adding new commands the presence of the Repeat command can be easily overlooked.
|
Workaround:
Add a command (any command) to the Driver Command Bar. The Don't Repeat option will then become available and the Repeat command can be removed. |
|
|
Copying the Driver Setup Rule
|
|
|
|
|
|
|
|
The Driver Setup Rule (and other rules) can be copied between Sessions |
Steps: To copy the Driver Setup Rule to other sessions:- |
|
in the Session Editor Right Click on the Driver Setup Rule |
|
select Copy from the popup menu |
|
exit the Session |
|
load the second Session (where the Rule is to be copied to) into Surveyor and open the Session Editor |
|
Right Click after the last rule entry and select Paste |
|
|
Notes:
There are some conditions that must be met before the copy between session will work:-
|
|
|
The Driver Command Rule controls which Driver Commands will be available to a user. This applies to both:-
|
commands added to the Driver Setup Rule in the Session Editor in Surveyor, and |
|
commands for the user to manually add to the Driver Command Bar of user and AI controlled trains running in Driver |
|
The Driver Command Rule is automatically added to the Session Editor of every Session.
The Rule properties window will open to show all the Driver Commands that have been installed in Trainz on your system. This list includes the commands that are built in and those that have been downloaded from the DLS. |
|
Notes:
|
|
If a command that you want to use does not appear in the list, then check in Content Manager that it has been installed and is free of errors |
|
In T:ANE some Driver Commands that have been checked ON will not appear in the Driver Command Bar if there is no target for their action. For example, no set trackmarks or interactive industries for the Drive To command |
|
Trainz Wiki
|
More Tutorials and Guides to Using Trainz
|
|
|
Related Links
|
|
This page was created by Trainz user pware in June 2018 and was last updated as shown below.