Session problem

[kihara]

I have laid a circular track, put 2 locos on it ,in close proximity, and am trying to create a schedule such that the first loco will start moving round the track, and when it reaches a certain point the second will start on the same journey (under AI control). The first loco behaaves as desired. The second starts off OK but each time round the circuit its schedule accumulates more and more commands, seemingly without end. Could this be because although both schedules have repeat commands (which sometimes seem to disappear!) only the second has a trigger command? Any advice would be welcome.

 

[trev999]

Hi kihara - Circular tracks present some difficulties for Trainz as the track is a closed circuit. Try placing some junctions at a few places to break up the 'short circuit'.

The repeat might be the cause of the accumulation of commands. It is not easy to diagnose with so little info. Can you show us a list of the commands you are using so we can see what you are doing? Use the # button in the toolbar to wrap code tags around the text when you reply.

Trevor

 

[kihara]

Hello Trevor,
I'm afraid I don't really understand about the toolbar and code tags, but I hope what follows will make things a little clearer.
I think the relevant parts of the session are:
DRIVER SETUP commands:
Loco 1 :#wait 5 secs# #insert comms from library entry 1# .
Loco 2 :#wait 10 secs# #append comms from library entry 1# #Wait for trigger to be triggered by loco1 # #Drive schedule# .
SCHEDULE LIBRARY entry 1:
#Drive to trackmark no.1# #wait y1 secs# #Dr. to TM no.2# #wait y2 secs#
etc.......#repeat# .
TRIGGER CHECK
Loco 1 specified; trigger only once; when train is heading forward into trigger.
I don't really know which child rule(s) to put below the trigger, since I can't find how to simply insert the Command "Drive to".
And when the session is running the Repeat signs have disappeared.
I look forward to your comments.

Kihara.

 

[colourlight]

I can see why you end up with a million commands. All you need is one schedule, one trigger and one "wait for trigger" command and a repeat if both trains are going to follow the same schedule. In surveyor place a trigger on the track where you want the first train to be when the 2nd one starts it,s schedule. give it a name if you wish so you know what it,s for. You will also have to tick the "wait for trigger" in the list of driver's commands. You already have your schedule or schedules if you are using a diffent schedule for each train. Now go into driver. 2nd Train append schedule from library and wait for "append" to disappear and the schedule to start. Select command to stop AI driving schedule. Add "wait for trigger" (name) any or a specific train to the beginning of the schedule and "repeat" to the end of the schedule. Now select command to start AI driving the schedule. 1st train. Same as 2nd train except you won't need the "wait for trigger" command.

 

[stagecoach]

Dont use the repeat as the commands will keep adding. The append will add the schedule to the end of the commands already listed in driver.
If you simply want to have two trains go around the same circuit doing the same thing then there is an easier way.
Schedule library
Do as you have shown below but dont put repeat. Place wait for trigger # # and the copy commands insert from library entry 1 as the last two commands in the schedule. Set the trigger for any train.
In loco 1 use Copy commands insert from library entry 1
In loco 2 use wait 10 sec and Copy commands insert from library entry 1

Both trains will use the same schedule and will wait for the train in front to pass the trigger so keeping the space even.

 

[kihara]

Session Problem

Grateful thanks to all of you who came up with advice and comments.
I've now got the problem sorted, also my understanding of AI has advanced slightly!