How to set up drive schedule
- Thread starter DonVRx
- Start date
Hi DonVrx,
Simple realy when you think about it, a drive command is one off. A drive schedule is a series of drive commands strung together one after the other. When the AI driver completes one command he will look for the next command, if there is no more commands he will stop. If you have a continuous track i.e. a loop you can place a repeat after the last command, this will cause a completed command to be added at the end of the list and used again after all the others have been completed.
Cheers,
Bill69
paperpusher
paperpusher
Schedule: repeating
I have used the AI tried to build separate schedules for three different line, but when calling up the schedule from the drivers' bar, It is not recognized for the route etc.
I have also tried the repeat command, and it created a backward direction for the unit. (although track directional marker may solve that problem). Sometimes the repeat does not work or stops working.
I have used the AI tried to build separate schedules for three different line, but when calling up the schedule from the drivers' bar, It is not recognized for the route etc.
I have also tried the repeat command, and it created a backward direction for the unit. (although track directional marker may solve that problem). Sometimes the repeat does not work or stops working.
I have used the AI tried to build separate schedules for three different line, but when calling up the schedule from the drivers' bar, It is not recognized for the route etc.
I have also tried the repeat command, and it created a backward direction for the unit. (although track directional marker may solve that problem). Sometimes the repeat does not work or stops working.
Have you told a driver to move to the loco or given the loco a driver in surveyor? The usual problem if a schedule does not start is because there is no driver in the loco. The repeat command cannot cause the loco to go in reverse unless the fist command destination is behind the train. But if you have a loop track you will require at least three trackmarks spaced around the loop to keep the train going in the right direction.
Cheers,
Bill69
Last edited:
nbrettoner
Bret_viS
Perhaps this is a little off-topic & I don't wish to take up space. However as knowledgeable people are here may I ask a somewhat similar question please?.
I have two short loops joined by a single invisible track, on which two motorcycle 'locos' travel.
It starts with one half-way along the track, heading towards a waiting bike at one loop-end.
Once the travelling one arrives, I would like it to "come in behind" & couple to the waiting bike (using a 10-metre invisible link bar), then for them to circulate continuously.
What invisible signalling/points/rules would you suggest please?.
I run TRS2004.
Reply by IM so as not to clutter this thread, if you prefer.
Many thanks,
:wave:
I have two short loops joined by a single invisible track, on which two motorcycle 'locos' travel.
It starts with one half-way along the track, heading towards a waiting bike at one loop-end.
Once the travelling one arrives, I would like it to "come in behind" & couple to the waiting bike (using a 10-metre invisible link bar), then for them to circulate continuously.
What invisible signalling/points/rules would you suggest please?.
I run TRS2004.
Reply by IM so as not to clutter this thread, if you prefer.
Many thanks,
:wave:
Hi Noel,
First let me say I have never tried this, but I will have a go at sorting it.
The waiting bike (call it bike 1) should be just in front of a trackmark, say trackmark A with the invisible link bar attached to it. Also there should be no driver assigned to the waiting bike. The other bike (Call it bike 2) should have orders to drive via a trackmark not far behind the waiting bike say trackmark E and a driver should be assigned to this one. There should be trackmarks spaced around the loop you want them to continue on say trackmarks B, & C, You could also use a couple of invisible speed boards to slow down the coupling bike before it couples and speed it up after coupling. Signals should be used only on the single track, and no signal between bikes 1 & 2 before coupling. You should also use direction markers to avoid bike 2 entering the loop the wrong way round. Then the commands, bike 2s driver commands should be drive via trackmark E, couple at trackmark A, wait for 5 seconds, drive via trackmark B, drive via trackmark C, then commands to take them to the loop at the other end. Use a similar setup at the other loop with different trackmark names of course, you will need at least three trackmarks to get them to drive round the loop. I would only use signals to protect the points on the exit from each loop. After they have coupled you will have to remove the first three commands so they are not repeated, or insert the Repeat command after the first three commands have been completed.
Hope this helps,
Bill69
nbrettoner
Bret_viS
Hi Bill,
Many thanks for this.
I'll save it for now & print out once I get a new black cartridge.
So it may take a few days before I get around to sorting this.
Using a single rail is very relevant for Craig (Seeseeme) & my project;
the old Narrandera_Tocumwal Branch Line in NSW.
Over 100 miles over vast flatlands, but with 'interesting' in-transit education along the way.
The Southern Hemisphere's largest WWII "McIntyre Field" covering 25 square miles at Tocumwal,
& Initial flight Training Centre at Narrandera make for some interesting sojourns
back in time, for some lucky tourists.
Enough said I'll depart. Hopefully Bill your advice for me here may help others too.
Many thanks & my apologies for intruding on this thread. :wave:
Many thanks for this.
I'll save it for now & print out once I get a new black cartridge.
So it may take a few days before I get around to sorting this.
Using a single rail is very relevant for Craig (Seeseeme) & my project;
the old Narrandera_Tocumwal Branch Line in NSW.
Over 100 miles over vast flatlands, but with 'interesting' in-transit education along the way.
The Southern Hemisphere's largest WWII "McIntyre Field" covering 25 square miles at Tocumwal,
& Initial flight Training Centre at Narrandera make for some interesting sojourns
back in time, for some lucky tourists.
Enough said I'll depart. Hopefully Bill your advice for me here may help others too.
Many thanks & my apologies for intruding on this thread. :wave:
I have used the Schedule Library and the Copy Schedule command to build a schedule for my AI drivers.
The Schedule Library lets you setup a schedule of commands all at once and then share the set of command with more than one driver using the Copy Schedule command. This is easier than setting up each command again for multiple drivers.
The schedule command its self is more work. I've used that for passenger trains once, but it was hard to calculate how long a train would take to get between stations because the AI are so unpredictable.
John
The Schedule Library lets you setup a schedule of commands all at once and then share the set of command with more than one driver using the Copy Schedule command. This is easier than setting up each command again for multiple drivers.
The schedule command its self is more work. I've used that for passenger trains once, but it was hard to calculate how long a train would take to get between stations because the AI are so unpredictable.
John
Having a schedule is great for passenger service. Trains leave and arrive at particular times day and night on a consistent basis in real life. By doing this in Trainz, we can make the running more realistic, and have to work the freights in between the scheduled passenger trains as the freights can't get in the way of the highballers.
John