Good question, particularly since you can set up a session with instructions and AI traffic, I'm a newby to Trainz but I've heard it used to be different. Setting up subforums, over at
www.trainsim.com we have an MSTS activity forum and an MSTS route building forum - and one thing we discovered there was often they're interrelated, so when we set up the new Railworks forum we combined route building and scenario creation into a single forum.
FAQ: How do I set up AI traffic?
A: It depends on how the signals on the route are set up.
FAQ: Okay, so how do I set up signals?
A: It depends on how you intend to run AI traffic!
:hehe:
Current project is a good example, using UNCOUPLEZ FROM and COUPLE AT TRACKMARK, I have an AI train dropping half a dozen cars on a yard track marker and another AI picking them up 10 minutes later - not working, for some reason the pickup can't seem to find his way to the marker. Tinkering with instructions and navigate via don't do any good, and the AI trains that are supposed to bypass that yard sometimes run thru the yard ladder even when the main is clear. So I have to go back to the route editor, add more trackmarks and directional markers. What I found is that the dropoff train backing into the yard, the last car becomes the "front" of the train during the backing move, so if the marker is near the switch he'll stop and uncouple with most of cutoff cars blocking the yard ladder. So move the marker to the buffer end, now he drops them in the right place. But now the pickup can't find a path to that marker since the cars are in the way, so I need to go back to the route editor and add another marker to the switch end of that yard track, then back to the session editor to tell him to couple at the new marker instead. Same thing with triggers and signals, route editor, session editor, driver to test, back to route editor and make adjustments and additions, back to session editor to make a few changes, back to driver to test again.
I'm not saying we shouldn't have a separate session forum, all I'm saying is that since what you do in the route editor affects the session and what you intend to do in a session affects how the route is designed, they're going to be interdependent anyway.