Group items tagged

more realistic AI-driver attitude I would like to see (as an update to all Trainz-Versions or at least as part of any new Trainz-Version) more realistic artifical inteligenced drivers in Trainz.

As for the "Ball and Flag" system given in this and another thread, we have the "Wait for Trigger..." driver command, which, I admit, is hidden by default. Go into the driver commands rule to make it visible. With enough forethought, it behaves in exactly the same way, Just on triggers and has to be inserted for every driver using that single track. Though that only works with AI. Us humans have the layout map. Having these automated systems would be a help, but there are already driver commands that work the same way.

I agree that the shortest route thing is annoying as well. I've gotten around it by by placing a trackmark on the main track, and I use that when I'm programming the drivers. Another thing I've done is to place a freight car or two on the sidings to force the AI to take the mainline instead of driving through the yard. I agree with Stefan. The routing should be based on locale rather than built-in short-distance seeking algorithms, which I think cause a lot of overhead on the program because the AI system is constantly seeking for an open path. John

Hi PikeWake, Yes it is possible so long as you have enough patience, it will take quite a lot of commands. Extra commands you will need are "Couple At Trackmark" kuid 57145 81100 "UcouplezFrom" kuid 66277 80005 "Uncouplez" kuid 66277 80000"Hornz" kuid 66277 80001 You will also need trackmarks on each siding both the pick up sidings and the drop off sidings and one on the main exit line.

Bill69 has already said what is needed. You need to add to the track two trackmarks, one at the buffer end (not to near the buffer as the buffer stop will effect it) and one just inside the junction. Do this for each spur and name the trackmarks (say 101B at buffer end and 101J for junction end). Commands would be :- couple at trackmark 101J uncouplez from two couple at trackmark 102J uncouplez from four couple at trackmark 103J uncouplez from six drive to trackmark 001B uncouplez Then repeat the above using the names of the next spur.

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

I have a situation in a session where I need AI trains to drive to one of four possible refuel points. The target trackmark must of course be unoccupied. I Have downloaded the driver command 'Drive To Trackmark List' (Kuid2:61392:1050:?) which appears to offer the solution.

Hi Andy and thanks for your interest in my DriveToTrackMarkList driver command. to use it to drive to one of your 4 refuel points, you need first to add under surveyor a trackmark to each of your refuel points and name each trackmark like : myrefuelpoint(1) myrefuelpoint(2) myrefuelpoint(3) myrefuelpoint(4) and save your route.

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)

If you have your train drive to a trackmark and uncouple. The first section then departs via a trigger. A spare engine is parked in a siding and when the trigger is activated its driver moves to the remaining part of your train and then drives it in accordance with the instructions you have already input for him. i.e Main train has instructions similar to.. Drive to trackmark, Uncouple from, Drive to London. Spare engine has instructions similar to ... On trigger move to unit x. Drive to Bristol.. This should also work in reverse so that you can re-couple the two sections of your train and return the spare driver to the spare loco.

Ive been doing this for years, dont use a trigger as another train can sometimes set it off. You need a spare driveable asset (I use a car parked in the station car park), it will need a driver which you set up with all the commands for the tasks he will do as the second train. You need two trackmarks at each end of station named say P1 Dn and P1 Up. You will need the commands Post Message and Wait for Message and clear also the move to train at trackmark. Dont use move to train as the commands dont go with the driver. Add to the start of spare drive the command Wait for Message.

In the schedule Library rule you give a name to the first schedule then place all the driver commands for that section of the route you want it to take. This includes all industry or stations plus trackmarks. (Make sure you have the drive via or drive to trackmark commands ticked in the driver command rule) Select the next/add schedule give it another name etc etc. One of the driver commands is copy commands from. Place this in your selected train, even ones created in a portal, and you will get a second menu appear with amend or insert. Highlight one and another screen appears which you select to copy from another train or from the library. Pick Library and you get a list of all the routes you put into it. When AI gets this command he will then follow the route in the library.

Ive been doing this for years, dont use a trigger as another train can sometimes set it off. You need a spare driveable asset (I use a car parked in the station car park), it will need a driver which you set up with all the commands for the tasks he will do as the second train. You need two trackmarks at each end of station named say P1 Dn and P1 Up. You will need the commands Post Message and Wait for Message and clear also the move to train at trackmark. Dont use move to train as the commands dont go with the driver. Add to the start of spare drive the command Wait for Message.

Have you looked at the Couplez command? I think this allows for a longer list.

Atilabarut's 'Couple to vehicle facing trackmark' allows any distance between the vehicle and the trackmark. I have found it near bombproof... Andy

CoupleToVFacingTrackmark. The trackmark does have to be the correct way around, but otherwise never a hint of a problem in 06, though I guess there could be an issue if you are using a later version. Andy...

under TRS04 and 06 , I often use 'ControlDiamCross' <kuid:131986:1036> as a Block Token, the train takes the 'token' and conflicting signals are set to red so preventing AI from entering the single line, once the train has passed the exit trackmark, it releases the 'token' and allows the next train to take possesion of the 'token' and proceed onto the single line. The request for the token can be achieved automatically by using the 'Schedule at trackmark' rule <kuid2:61392:2001:4>. This rule can insert the command to ask for the 'token' when passing a specific trackmark, before proceeding with next command. Another possibility is the 'Path' rule which can exclusively set the entry and exit of the single line and in doing so, automatically block AI until the path is free again.

Here is a tip for moving Track marks. If you want to move track marks beyond spline points, use the move function for track objects (i.e. signals etc.) it works on track marks of all kinds. cheers, andyz

In the above image, you can see the result. The fill under the two tracks in the backgound is part of the track and was not added after the fact. It bridges the dip in the ground very nicely. Search for "1t spoordijk grind MRT" or 70337:38035 to try it

I have setup one of my AI drivers to drive a schedule which consists on "coupling" to freight car and then driving to the freight car then hauling to to unload and then i have it set to repeat. My question: Is there away or a rule to remove the "couple" command from the schedule during the session., besides doing it manually?

I would set up in the schedule library two sets of commands: the first with the couple/uncouple command and the second one omitting it. Use the 'copy commands from' and insert the first library command, then 'enable repeat' and then finally the second library command. What this does is the first time the train will perform the couple/uncouple action and then in the future repeats of the route this action will not be performed.

I have these commands and I use them on one route, as the basic concept should have been "default built-in" in my view. Yes, you only get the single icon - until it is used, and then it expands to the commands you are copying. But any command you have that are "specialised" like, I use "movetoloco" - these are kept to the original, so you'd have to change to what you need. Hope you understand what I'm saying as I'm not sure that I do!!! Chris

If you use Move to train at trackmark the commands will go with the driver. Ive used this a lot for placing the driver from one task to another with a different train. __

Yup use "Path Command" with "Drive to" and that most excellent "Trainz Schedule Library" you can't go far wrong. Takes a bit of time to set up but once done it only takes one click to give a Drive a whole complicated route.

drive to and drive via will not work with select part you have to autodrive or TPR drive hope this helps

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.

You want the copy commands from and the schedule library rule kuid2:192081:1:6 and kuid2:192081:12:4 Place the tasks you want repeated in the library and use the copy command to call up the task in driver set up __________________