Add on a new separate line:
-freeintcam
into the Trainzoptions file
Alt+U or Alt+V might work also
Edit: Use the keyboard arrow keys to roam
__________________
"Add on a new separate line:
-freeintcam
into the Trainzoptions file
Alt+U or Alt+V might work also
Edit: Use the keyboard arrow keys to roam
__________________"
Where the green dots are signals, and track direction markers are the yellow arrows.
Make sure you have enough space for the longest train that will run before the first signal in the loop, this will stop a train being held at that signal from blocking the exit from the opposite track...
Edit; if this is for overtaking then you will have to use triggers, i'd suggest...
There is also a limit to the number of threads that can be run in a scenario which I believe is 64. I have found ways to increase the number of trains that can be run within this limitation and can explain them to you if you ever reach the limit.
The sessions of the Crewe route run to careful timetable and I have documented the method in various threads. This is the only method I have found that works reliably.
I am just putting the finishing touches to a Crewe session '100 Trains' during which more than 100 trains pass through Crewe on a strict timetable over 3 hours including engine changes, shunting, breaking down and making up trains etc. the existing '50 Trains' session already uploaded utilizes all the control techniques I have configured to achieve timetable working - and it works GREAT!
DAP wrote:
Your suggestion worked. First, I removed the assets from the route. Then I copied my library and portal assets to a cdp. Then deleted the original copies listed in CM2. I then loaded the the route (the library asset was still there and doing it's init routine). Then save it. Upon loading it again, the persistance was broken and the library functions were no longer happening.
Try the Portal Timetable Rule found on the DLS.
http://www.openspeedway.net/files/pics/ptr.jpg
You can set which portal you want it to come out of with "Emitting Portal
You can set what time it comes out with "Add New Timetable"
You can set what train comes out with "Add an existing saved consist"
You can select a driver with "Add Driver to Consist"
You can use the command bar to add and save commands for the AI to follow.
To add another train just click on the "I" box at the bottom.
You'll need to be a bit cunning with this one. I'd go with something like this in your Scenario thread...
Scenario
OnAnnouncement Make_AI_Train
AddTrainToRoute My_AI_Train
And then in the PlayerTrain thread you'd need something like this...
PlayerTrain
OnTrackMark TrackMark_X
Announce Make_AI_Train
So when the PlayerTrain hits TrackMark_X the Scenario thread will see the announcement and add My_AI_Train to the route.
Make sure that you're not going to hold up absolutely everything in the Scenario thread though.