After some runs, tests and trials I've come to the conclusion that, provided that the AI train paths and schedules are well tuned, some regular meets can happen on a single-track route with the actual (1297) ORTS release. As I already mentioned in other posts, AI train paths should not have reverse points by the moment, because these often are not yet correctly managed at run time by the automatic AI dispatcher (both signalling and reversing itself). AI stops at stations can be by the moment implemented inserting waiting points, as AI trains don't yet stop at scheduled station stops.
Now, how to create and debug/tune activities? Activity creation may by the moment be done with the MSTS Activity Editor. The problem is in debugging and tuning, because the so called "VCR" facility (simulating the run on the route map) contained in the MSTS AE cannot be used, because it does not behave like ORTS does. So something within ORTS should be used. There are already the dispatcher window and the accelerated clock features, that of course are very useful. The problem is that it is quite difficult to correctly drive a train with a highly accelerated clock. This can be solved if there is a feature that allows to have the player train driven by the software, as if it were an AI train. This could be triggered by a toggle key that toggles between player-driven train and software-driven train. Maybe this is not a very complicated feature, and it would highly speed up ORTS-compatible activity creation.
By the way, another small hint: in the track monitor window (F4) it would be nice if distance of reverse points behind the train (those that have to be reached by driving backwards) would be indicated with negative values.
Carlo
Now, how to create and debug/tune activities? Activity creation may by the moment be done with the MSTS Activity Editor. The problem is in debugging and tuning, because the so called "VCR" facility (simulating the run on the route map) contained in the MSTS AE cannot be used, because it does not behave like ORTS does. So something within ORTS should be used. There are already the dispatcher window and the accelerated clock features, that of course are very useful. The problem is that it is quite difficult to correctly drive a train with a highly accelerated clock. This can be solved if there is a feature that allows to have the player train driven by the software, as if it were an AI train. This could be triggered by a toggle key that toggles between player-driven train and software-driven train. Maybe this is not a very complicated feature, and it would highly speed up ORTS-compatible activity creation.
By the way, another small hint: in the track monitor window (F4) it would be nice if distance of reverse points behind the train (those that have to be reached by driving backwards) would be indicated with negative values.
Carlo