Trigger Help
- Thread starter tallboy22
- Start date
A valuable resource which may help you is found at
http://www.auran.com/TRS2006/index.php
It is found listed under Downloads/Sessions Guide
The TRS2006 Sessions & Rules Guide
Have fun, It is light reading
Regards,
Lenny
http://www.auran.com/TRS2006/index.php
It is found listed under Downloads/Sessions Guide
The TRS2006 Sessions & Rules Guide
Have fun, It is light reading
Regards,
Lenny
for the sake of an example, say you have a long section of single track, you place a trigger on the eastbound track after the single section. the westbound train drives to a trackmark prior the single section, the next command he will follow is wait for trigger XXXX to be triggered by any train.
the eastbound goes through triggering the westbound to go onto the single section.
Basically you can make events happen in a sequence you want.
the eastbound goes through triggering the westbound to go onto the single section.
Basically you can make events happen in a sequence you want.
So, If I had a single track that led to a seaport lets say, Would it be possible to have a small engine bring a load up the single track to the mainline, then using a trigger have two UP's take the load to its destination, return, uncouple (hit trigger) and the switch engine would take the emptys back to the seaport to get loaded?
yes, the switch engine uncouples goes to siding A on the way hits trigger XX which triggers mainliners to couple up and follow their orders. they bring consist back uncouple going to siding B on the way hitting trigger XXX which will bring the switch engine out to follow its loading procedure.
you can use drive to t/mark + couple at trackmark command. before uncouple and after couple commands give a wait 10 or 20 secs command.
you can use drive to t/mark + couple at trackmark command. before uncouple and after couple commands give a wait 10 or 20 secs command.
Last edited:
stagecoach
75377
A trigger is placed and named at a point that you want another train to activate it. The train you want to start operating needs the wait for trigger comand which you will have a choice of a named trigger and of selecting a named train or all trains.
Sometimes it might be easier to use the post message and wait for message and clear commands. In this case your dock engine will goto anywhere and wait for message. the arriving train will post a message when it has arrived and as soon as has done it the train waiting for message will start its duty. Useful if you use portal trains as the engine will not be the same one each time it comes out of portal.
In your dockyard i would prefer the second way this avoids an incorrect train setting off the trigger. You could have single line from dock split into a double track before the mainline (up and down) place a trigger on the up track and a trackmark on the down track then make trains stop at trackmark and wait for the up trigger to be activated by any train.
Sometimes it might be easier to use the post message and wait for message and clear commands. In this case your dock engine will goto anywhere and wait for message. the arriving train will post a message when it has arrived and as soon as has done it the train waiting for message will start its duty. Useful if you use portal trains as the engine will not be the same one each time it comes out of portal.
In your dockyard i would prefer the second way this avoids an incorrect train setting off the trigger. You could have single line from dock split into a double track before the mainline (up and down) place a trigger on the up track and a trackmark on the down track then make trains stop at trackmark and wait for the up trigger to be activated by any train.
Accipiter777
New member
Please Note the following about Triggers. I use three on my route... two work, the other does not. In the yard i'm working on, the shunters are in pairs. the shunters working the departure yard would not trigger the departure engine to procceed with his schedule. The shunters go into the classification yard, couple up and move that consist to the departure yard, it hits the trigger on the other side, then returns to a staging area until the next consist in the classification yard is ready, then it repeats. the depart engine waits for this trigger, goes to the depart yard, and couples up then continues on its way. I moved the trigger to another area, it works, move it back, it does not. turns out, when the depart shunters get to the other side of the depart yard, it CHANGES direction to come back. the trigger was set to the front engine, which is now not being drivin by the AI. I redirected the trigger to sense the engine that is now in the front at this point and it works. just make sure the trigger is assigned to the engone with an AI in it. the AI moves to the front most engine when it changes direction 
http://www.smileydesign.co.uk/TrainzLab/2locos.htm
But hurry, because the site will be closing soon.
Smiley.
But hurry, because the site will be closing soon.
Smiley.
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.
-Then put a trigger halfway down the track,
-Create a junction a bit further down so that we can switch it later
-Go onto the Rules menu and add Trigger Check
-Click the 1 time only button,
-Set the driver of the train, so that noly that train will trigger it,
-Set the trigger(this is what you called the trigger when placing it on the track)
-then hit the tick button,
If you want the junction to change do the following
-open rules menu
-add "Switch Junction" command
-pick the junction eg: Junction 1
-Set the junction the oposite way it is at the moment,
this will then change the junction as the train goes past the trigger,
-Then pick a train and make sure it has a driver.
-Then put a trigger halfway down the track,
-Create a junction a bit further down so that we can switch it later
-Go onto the Rules menu and add Trigger Check
-Click the 1 time only button,
-Set the driver of the train, so that noly that train will trigger it,
-Set the trigger(this is what you called the trigger when placing it on the track)
-then hit the tick button,
If you want the junction to change do the following
-open rules menu
-add "Switch Junction" command
-pick the junction eg: Junction 1
-Set the junction the oposite way it is at the moment,
this will then change the junction as the train goes past the trigger,
stagecoach
75377
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.
MailtruckChris
New member
Except when it doesn't.Please Note the following about Triggers. I use three on my route... two work, the other does not. In the yard i'm working on, the shunters are in pairs. the shunters working the departure yard would not trigger the departure engine to procceed with his schedule. The shunters go into the classification yard, couple up and move that consist to the departure yard, it hits the trigger on the other side, then returns to a staging area until the next consist in the classification yard is ready, then it repeats. the depart engine waits for this trigger, goes to the depart yard, and couples up then continues on its way. I moved the trigger to another area, it works, move it back, it does not. turns out, when the depart shunters get to the other side of the depart yard, it CHANGES direction to come back. the trigger was set to the front engine, which is now not being drivin by the AI. I redirected the trigger to sense the engine that is now in the front at this point and it works. just make sure the trigger is assigned to the engone with an AI in it. the AI moves to the front most engine when it changes direction
What you just said had been working for me untill I placed my last trigger. This trigger just won't. I've tried flipping the triggering consist around, moving it onto a piece of track so the track direction agrees with the drivers direction. No go. Is there another driver command I can use cause i've about had it.
