Quote
Each train uses it's path to clear it's own route ahead. It checks the data if that route is clear and if so, it will 'reserve' that route. If not - the route is reserved by another train - it will wait and will keep checking until the other train is gone.
That is, that a train in an activity, reserves the sceduled route, all the way to the end, if possible. An end that may lay 3 hours into the future???
I also read that special code is used to resolve the gridlocks that arise from this way of doing things.
Would someone "in the know" tell me why this solution has been chosen and not one that resembles reality?
F.eks.: I read about problems with a shunting task that was difficult to get right because another train had locked the mainline.
Now, If each train clears, say 4 sections ahead at all times, the shunting train would reserve the station tracks, unless another train was within 4 sections, in which case, the shunting could not start until the approaching train has passed.
As long as the shunting train is occupying the tracks, both signals guarding the entrance to the station would be red stopping any approaching trains, that might show up.
In my opinion, this would make things a bit more realistic.
However, before asking any more silly questions, I would really like to know, why the present solution has been chosen.
ChrisD