Skip to content

Commit 0a73a1b

Browse files
authored
Merge pull request #61 from Csantucci/update-manual-human-dispatch
Update OR manual with info about manually re-routing AI trains
2 parents 2019fdb + da8fe5f commit 0a73a1b

File tree

1 file changed

+42
-2
lines changed

1 file changed

+42
-2
lines changed

Source/Documentation/Manual/driving.rst

Lines changed: 42 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -734,8 +734,8 @@ By left- or right-clicking on a switch, a small pop-up menu with the two
734734
selections ``Main route`` and ``Side route`` appears. By clicking on them
735735
you can throw the switch, provided the OR AI dispatcher allows it.
736736

737-
With respect to AI trains, as a general rule you can command their signals
738-
but not their switches, because AI trains are not allowed to exit their path.
737+
Using the dispatcher window for AI trains is described
738+
:ref:`here below<driving-dispatcher-for-ai-trains>`.
739739

740740
The two checkboxes ``Pick Signals`` and ``Pick Switches`` are checked as
741741
default. You can uncheck one of them when a signal and a switch are
@@ -763,6 +763,46 @@ if the trains are far away, can lead to memory overflows.
763763
If after a train selection you click on ``Follow`` the dispatcher window
764764
will remain centered on that train.
765765

766+
.. _driving-dispatcher-for-ai-trains:
767+
768+
Using dispatcher window for AI trains
769+
-------------------------------------
770+
771+
What is described here is valid only for activity mode and explore in
772+
activity mode.
773+
774+
There are cases where it would be advisable to re-route an AI train to manage standoffs,
775+
train passings, train priorities.
776+
In this case, using the dispatcher window it is possible to re-route an AI train (e.g. on a siding)
777+
and then to get it back on the original route. The feature anyhow also allows to
778+
re-route it without getting it back on the original route.
779+
780+
It is suggested to look at this video which explains some practical case
781+
https://youtu.be/-f0XVg7bSgU before continuing reading.
782+
783+
To perform this correctly and in a way more similar to reality, some rules have to
784+
be followed.
785+
The concept is that switches must be manually thrown only if they aren't reserved by a train.
786+
To be sure of this it is necessary to force to stop the last signal(s) between train(s)
787+
and switch, in case such signal is not already at stop. Once the switch is manually
788+
thrown, the signal in front of the train that has to be re-routed must be set to the
789+
"System controlled" state if it had been forced to stop before.
790+
At that point OR breaks down the old train's route and re-computes a new one, taking
791+
into account the moved switch.
792+
More switches may be forced on the route (e.g. both the switches to enter the siding
793+
and the ones to re-enter the main line).
794+
795+
Signals must never be forced to clear or approach.
796+
797+
If an AI train is re-routed on a route which isn't at the moment re-entering the
798+
original route, its path information in the dispatcher info HUD is displayed in yellow.
799+
800+
Station platform stops are re-assigned to adjacent platforms, if available. Events and
801+
waiting points in the abandoned part of route will be lost.
802+
803+
The re-routed train may be also the player train (be it autopiloted or not), provided the
804+
Autopilot option is checked.
805+
766806
Additional Train Operation Commands
767807
===================================
768808

0 commit comments

Comments
 (0)