Railworks America

Is there a way to have an AI train wait until the player train stops/passes a destination point, then start (the AI train) doing something?

I want to have the player train come into a yard, drop some cars off, then go to a destination point and wait until an AI train has completed a task, then have the player train go and complete its tasks...

The RailWorks's scenario editor is sometimes rather fussy, confusing and limited to work with in some ways, especially in trying to have more complex actions happen.

You can only really set a "start time" for the AI trains to carry out it's instructions, and do your best-guess in "approximating" what time to start so that it appropriately "jives" with that instructions and actions the Player and Player's train are doing.
In here can lie a conundrum, as the Player can be going perhaps a lot faster, or a lot slower, than you anticipate, therefore the AI train's "start time" no longer "jives" with the approximate times in which you expect the Player's train to be at a certain time.

Depending on the particular area of the track infrastructure where said activities and instructions are to occur, if there's automatic-junctions involved, then the RailWorks Dispatcher may set the appropriate junctions in question to a path to allowing the the train to proceed down the path it "thinks" is best, and also according to train-priorities, and also according to if anything else is blocking it's path or not, or if track on it's path is clear.. etc...

Anyways, in my experience, though I can program some fairly complex instructions for the Player train to perform, I usually keep instructions for AI trains more "simplistic", and try to ensure that the Player's train and the AI trains will have a "clear path" to perform their instructions. Otherwise it can be easy to run into "pathing" conflicts and scenario-breaking errors.

I tend to set the Player's train "priority" a bit higher than the AI trains as well.

You could experiment with this (train priority settings and start-timings of AI trains, junction-settings and programmed instructions to perform) and see what results you may get, but like I said, it can all easily get thrown out-of-whack if the Player drives a bit too-fast or a bit too-slow than anticipated, thus, greater potential to cause pathing conflicts with AI trains and scenario-breaking errors to occur.

So when it comes down to it, in the end I try to have the AI trains follow the "KISS" method, "Keep It Simple, Stupid" and tend to keep them at a lower-priority level than the Player's train.

I think the only way to keep the AI train from moving until the player train arrives is to make sure the player train has blocked it's path ( and subsequently unblocks the path when it stops ). That is a bit hit and miss, as you might imagine :p. Player train priority seems a bit funny too, the despatcher seems to adore the player more than anything in the world.

I would have a marker where I want the player to stop and Time Table that Stop and perhaps the one prior to it, thus forcing the player to be at the destination at the time I want them to be there. I know some players just can't keep up to a timetable because of skill,(mark scenario as hard in this case) but most players will and can stick to time tables.
If it is very critical to keep to the time table I usually warn the player in the scenario read me and briefing that they should keep to line speeds. Other times I say that a train is 'limited to a speed' and the player must keep to it. I then mention in the read me that the scenario will just not be 'fun' if they do not follow the guide speed I mentioned.
This was true for my A1 v A1 scenario where the player must limit the A1 Tornado to 75mph despite the fact that it can go faster and the line speed is 125mph. I guess some players just went 'hell for leather' on the throttle and ignored my advice, in that case they passed a lot of stationary trains or missed the traffic completely.