Auscgu wrote:Added a shared disc so they can copy the install.
This is the exit from the down sidings at Wareham.
This is another level of complexity. There are cases where the Kuju assumption that each signal applies to exactly one location in exactly one track is invalidated by UK practice. One disk placed between both sidings applies to the track to the left and to the track to the right. (On the signal diagram I have, it sits to the left of the leftmost track. But in the game, users may well cope better with the situation when it sits between them. Who knows?)
For the game AI to understand the situation, we need two stopping signals (that is with "is stopping" = true in the .xml file). No one wants to see two things here, so they are invisible like the AI-only stopping signal. But they are signals, placed in route editor, not scenario editor.
Then we need one thing that is visible and it needs two links. This is very unorthodox in that you treat the unnumbered link 0 like any other link. It does not care where the links are placed but you do yourself a favour if you place each of them in advance of one of the bricks.
The picture in this post shows the general idea with the visible signal (called external arms) and the invisible signals of very tasteful, poisonous looking design (called virtual signal) all selected.
Each virtual signal is a master in IT parlance and they share one slave. Whenever one of them feels like clearing an arm, it tells the slave to do that. All other masters of the same slave must shut up meanwhile or we are in a mess. However, the prototype never uses such a setup where there are can be two engines competing for the path at the cleared signal.
If you don't resort to wrappers, you create 2T or whatever versions of the invisible signal. I works much like a normal signal inside. But in practice, it will go quite unconfigured 100% of all realistic use cases.