Group items tagged

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,

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.

I finally got back to this one. Here's what I did, you can adapt it to your requirements. BTW this is in TRS2004 but all later versions should be identical or very similar. Layout: One baseboard, one straight track. In order: Where the loco starts Trigger TR1 Trackmark TM1 Trackmark TM2 Trackmark TM3 (It helps to put a building alongside each trigger/trackmark so you know where they are when driving) Place a loco at the starting position The objective is to make the loco drive to TM1, then drive back and forth between TM2 and TM3 forever. Rules (where each > represents one level of indent): Startup options - as normal Driver Setup - Drive to TM1 Driver Command - as normal Trigger Rule - Trigger TR1 > Ordered List - This process will be repeated 1 time > > Driver Setup - Drive to TM2, Drive to TM3, Repeat I hope you can copy this and get it going, and that it's of some help to you. I find one of the trickiest things is to keep the difference between Rules and Driver Commands clear in my head. John

SD40-2 UP United Way snoot release As I promised my SD40-2 snoot #3300 with the United Way paint scheme is ready for download. http://uslw.net/downloads.php?action=view&id=253 All assets created by me are included in the CDP. The only ones that are not are the horn sound by 007007 at the USLW DL site found here, http://uslw.net/downloads.php?action=view&id=157 and the engine sound made by Wolf_9 on Aurans DLS found here, http://www.auran.com/TRS2004/DLS_dow...wnloadID=67344 Happy 4th of July and enjoy it everyone.

just doing a catchup in the last few weeks after not being able to upload for sometime. Recently I have uploaded a lot of oz stuff including new station buildings yard buildings of varying types and bridges. I have also been uploading locos and rollingstock, some of these are Vline grain hoppers and a refrigerated 4 wheel wagon, NSW 30 and 79 class locos as well as private and govt. 4 wheel coal hoppers.

I have two sw engines. Each one operates on a trigger. The first goes into the yard, couples to a consist and then takes the consist to a factory and loads. It returns the cars to another spur and uncouples and returns to the stall and waits for the trigger. A portal train brings empties and leaves them on the first track and then goes to the spur and picks up the fulls and takes them to the portal. On the exit it trips the trigger and the process starts over. The second sw operates much the same with a 10 minute wait before it begins. This system works great but you have to state in the trigger rule the name of the loco. You might call the trigger train "Chem-Train" or "Milk-Train" and then that is the only loco that can trip the trigger.

The best way to learn about triggers is het up a new track and draw a line of track that goes from one side of the start grid to the other side, -Then pick a train and make sure it has a driver.

In the cases of Accipiter777 and Mr_D using the post message and the wait for message and clear commands would eliminate the need for the trigger being set of by another train and would not require Double engined trains to have the AI at the front. These commands dont need to know what engine is being used it has its own tags that the driver sends out and any driver set up to wait for it will then carry out the next task. __________

Top left of screen, in dropdown surveyor menu select edit session, then in new window select driver commands, in next new window click on add then scroll down till you find schedule library select it and click on the green tick. You will also need the (copy commands from) command found the same way. Don't forget to name and save your schedule so you can recognise it next time you want to use it

Append attaches commands after commands that are already in the driver's command line, insert places a whole string of new commands.

I don't have TS2009 yet but since no one else has tried to help yet i'll give it a go. Once you have loaded the map you want you will have to place at least one loco before you can start a schedule. Placing the loco should aut

Layout: One baseboard, one straight track. In order: Where the loco starts Trigger TR1 Trackmark TM1 Trackmark TM2 Trackmark TM3 (It helps to put a building alongside each trigger/trackmark so you know where they are when driving)