I guess the latest patches didn't fix AI throwing switches under driver-controlled trains!

billm001

Member
I was hoping that this simple problem would have been fixed along time ago. Are there any work arounds for this issue?
 
You can use the Set Junctions Rule to temporarily lock junctions against AI and/or user control.

There is an older (build 2.0) built-in version of this rule installed in TRS22 <kuid:-25:1269> Set Junctions as well as two more recent (build 5.0) versions on the DLS
<kuid:-25:1560> Set Junctions
<kuid:-25:1575> Set Junctions

... I do not know what are the differences (if any) between those two
 
<kuid:-25:1575> Set Junctions is the latest version of the rule, which obsoletes all other versions (negative UserIds don't allow kuid2 versions). The sequence of the versions (oldest to newest) is:
Code:
<kuid:-18:1237>
<kuid:-25:180>
<kuid:-25:1046>
<kuid:-25:1065>
<kuid:-25:1154>
<kuid:-25:1269>
<kuid:-25:1560>
Some of these aren't available at the DLS.

Peter
 
Will this fix switches points that do not visually move on routes? I have a problem with the switch points not moving, but the train still goes in the right direction.
 
Will this fix switches points that do not visually move on routes?
If it is just the switch points or blades that are not moving then I would suspect that at least one track that is forming the junction is not a procedural track. Faulty procedural junctions are usually shown with a red spline circle (in Surveyor 1.0) or a red dot (in Surveyor 2.0).
 
Last edited:
Back
Top