repeating rules

[Lokostefan]

Here my problem/idea/question:

I created a rather big scenery. Part of it is lot of industrie. Part of that is a locomotive that is suposed to do a complicate job. I created this as rules/orders (sorry, my Trainz speaks German, I don't know all the English Trainz-therms) to the Lokomotive Driver. And now the Lokomotiveis doeing the Job.

But I would like to have it repeat all, after it is through with all the orders/rules.

And then I would like to have it repeating again and again and again (indefinite numbers of agfains), to create the effect of an endless randomly different busy industrial railroad traffic around a main route, while driving on that very main route, passing all the harbours, airports, industrial areas and so on.

How to make a lokomotive driver repeating all the ordersw/rules that he got assignet at the very beginning?

And yes, you did guess right: I want to do this repeating thing to several different locos at/in the very same scene to creaty this effect of a very busy hill of ants.

 

[celje]

At the end of the schedule put in 'repeat'.

 

[trev999]

Issuing a list of driver commands

Hi Stefan - Are you able to download from the DLS? The items you need are:

Schedule Library <kuid2:192082:12:4>
Copy Commands From <kuis2:192081:1:6>

The schedule library is a rule that you add to the session. You then set up the sequence of commands for a train. You can make many entries and just copy then to whatever train you want.

The other is a driver command which can copy the commands from the library entry that you want to the train driver schedule. You can do it for any train at any time.

By using 'Copy Commands From' you can copy the schedule from the driver of one train to that of another. It only works well if you copy it at the begining of the session because, as soon as the driver starts executing his schedule it will roll around. Therefore the first method is recommended.

To make the schedule repeat:

Method 1. Place one or more 'Copy Commands' commands in the driver setup and then select repeat. (Recommended method)

Method 2. At the end of the library schedule, place another 'Copy Commands From' command and the driver will call up that library again, or another one if you specified a different command entry. This is like chaining entries together.

If you cannot download the kuids you can get them from
http://www.js-home.org/trainz/index.php

Please ask more questions if this is not clear.

Trevor

 

[Lokostefan]

Yes, I'm able to download from trhe DLS.

Actually I did not create schedules so far, never did. I just had rules pushed into the driver command field and noticed them to disapear while the driver is working them down and now wondered how to make him repeatingly following them if they went away by working them down.

Thus I have no clue about creating schedules. I even never thought about them, as I always had in mind they would need parameters like time and day and so on like the real schedule on a real scheduled train, whilke I had in mind to have those lokos doing there job independend from any day time.

But I'll try the schedule-thing. If it does not need any daytime to any command, than it is fine.

And if it is also possible to put trigger-reaction-commands in it, then it would be perfect to me.

With thanks and regards,
Stefan

 

[trev999]

Using driver orders or commands

Hi Stefan - A schedule does not need to have a specified time, it is just a list of jobs that the train driver must do. The most typical are drive to trackmark , couple, uncouple, wait for x minutes or x seconds, drive to industry, load or unload goods, drive to portal. These are known as driver commands or driver orders.

The simplest way to tell the train driver to do his job is to right-click on the train and select a job. You can give more than one order to a driver by clicking on the small green arrow after the last order and adding another one.

If you want to make the train wait until you have all the orders in position, click on the picture of the driver and select "Stop Train". Add as many orders as you need and then click the picture and select "Continue Schedule".
To stop the orders from disappearing, click the small green arrow after the last order and select "Repeat". The orders will then re-appear on the right-hand end of the schedule.

There are many different types of orders that you can give to a train driver. One is Wait for Trigger, which holds the train until another train arrives at a green trigger object.

Rules are something different. Some rules are built into a session when you create it. A rule can apply to all trains or just some of them. You access rules by clicking on "Edit Session" from the main menu in Surveyor.

The Driver setup rule has a picture of a man in a blue uniform. If you select the picture and click the "Edit" button it will bring up the schedule for each driver. There has to be a locomotive on the tracks for a driver to be able to drive.

You can set up a sequence of orders on the schedule bar just as you do in "Driver" mode. Use the repeat command as the last one to make the schedule repeat over and over. When finished, click the green tick mark to accept the schedule. Click the green tick on the next screen (Edit Session) and then press Control and Function key 2 to let the driver drive the train.

Hope this helps to start you off.

Trevor

 

[Lokostefan]

Dear Trevor,

now I understood the repeat-issue.
The other rulel-adding-stuff I allready understood and made. (It is kind of self-explaining by doing it (in all the German language Trainz-Versions since Pro Train Perfect).

You've been a great help.
Thank you very much.

With very berst regards,
Stefan

 

[JCitron]

Hi Stefan,

If you use the Copy Commands from, put in a Wait 20 seconds before it to give the AI time to settle in and execute their commands.

John

 

[Lokostefan]

Hi Stefan,

If you use the Copy Commands from, put in a Wait 20 seconds before it to give the AI time to settle in and execute their commands.

John

Thank's John.
I never waited so far. I never had, since I use to assign commands only to AI-Trains in the surveyor-mode, not while actually playing a route. And I never created a copy command before, but I guess "repeat" is a kind of "copy command". Thus I'll give the AI driver a minute or so before going on. If it is a repeat of every command before, then it is easily to hide the waiting time by starting the command-circle with a "wait" where it is needed anyway to then go through all the commands until the "repeat" is been set.

I mean, that it is, a never ending circle of commands. And where to start that circle only is pending on the fact where at the layout the AI-locomotive is being parked with what wagons behind in the very moment the game is supposed to get startet in the driver-mode.

Thus, thanks John for that additional advice, I'll now go to be be aware of that too.

 

[JCitron]

Thank's John.
I never waited so far. I never had, since I use to assign commands only to AI-Trains in the surveyor-mode, not while actually playing a route. And I never created a copy command before, but I guess "repeat" is a kind of "copy command". Thus I'll give the AI driver a minute or so before going on. If it is a repeat of every command before, then it is easily to hide the waiting time by starting the command-circle with a "wait" where it is needed anyway to then go through all the commands until the "repeat" is been set.

I mean, that it is, a never ending circle of commands. And where to start that circle only is pending on the fact where at the layout the AI-locomotive is being parked with what wagons behind in the very moment the game is supposed to get startet in the driver-mode.

Thus, thanks John for that additional advice, I'll now go to be be aware of that too.

When I place in my commands in Surveyor, I place a wait at the beginning for about 20 seconds. I've even done some staggering so that the AI don't all start their driving at once. With this method, I find that overall this gives the computer time to stop loading up scenery, trains, and other stuff needed to get the simulator running. When I've not done this, the AI drivers seem to get "smarter" than they should, and start to do their own driving instead of following what's given to them. This might be attributed to a lot of threads being executed at once instead of a few at a time.

John

 

[Lokostefan]

Very good hinch. Very good. Thanks. I'll be aware of that. Regards,
Stefan