In situation shown in diagram, Ai trains runs without problem, if signals and markers are placed correct. It's no need to use additional rules or commands. You need only ''Navigate via Trackmark''.
Sadly, I,m not familiar with Path Command and Autodrive.
Hi Colourlight
I use the jsTRF-PathControl rule and Autodrive driver command by brummfondel. This is on the DLS or is available from this site which has explanations for these and other useful rules.
This Path rule doesn't seem to work if the Quickdrive rule is also in use in a session. If you make use of the Quickdrive rule then you will have to look at the built in Path Rule which does a similar thing but is written in French. As I haven't used French since I left school 50 years ago I opted for the one in English. The one from the link above requires the signal at the start of the path to have a unique name. When you enter the signal name on the path it automatically finds the junctions behind it. The built in one requires every junction on the path to be entered manually which is a bit more time consuming.
I have a cut down version of the current ECML route from Hitchin to KX and have programmed every path through the different stations to ensure that the AI goes where it should when it should in order to run trains to the current timetable. With trains going through Finsbury Park every two minutes at times there is no room for the AI to stop and think without throwing the whole thing into confusion.
In the real world when a train stops at a signal after 2 minutes or whatever time interval it happens to be, the driver contacts the signaller and says "what the **** am I doing at this signal" or words to that effect, lol. He does not run around throwing point switches in a vain attempt to get a proceed aspect. But seriously if the AI can find a way to scupper your plans it will. I have yet to fnd a 100% foolproof way of making the AT driver do what you want it to do. I use lots of direction markers and trackmarks which work most of the time but not all the time. The other thing I do which nobody has mentioned yet is to improve your layout from an operational point of view. removing or reducing points of confict between trains can make a big difference. When I modified Port Ogden and Northern I had AI trains approaching Van DenH on 2 routes and leaving on another route and meeting at a complicated junction just outside the city. I should have filmed the ensuing chaos. One AL driver stopped at a red signal and locked the points which stopped every other train and then some trains didn,t stop until they crashed into the back of another train. So I built a flyover from the Hythe line over the junction and the river right into Van DenH so I could simplify the junction which solved the problem. Mind you the old junction was more fun to watch. Also there is a bit of a debate about whether to issue "navigate" or "drive" commands. I prefer "drive"
if the AI can find a way to scupper your plans it will. I have yet to fnd a 100% foolproof way of making the AT driver do what you want it to do. I use lots of direction markers and trackmarks which work most of the time but not all the time.
I full agree with this. Ai trains are not 100% accurate. The problems always arised if you have to much trains on the route at once 'in live', or when trains start with 'second round', repeating the schedule. And this is the biggest challange for me, how to control this behaviour.
