Wait for Trigger Command

I realize that the problem of the Wait for Trigger command greying out has been mentioned on several occasions before. I know how to set up the Trigger Check Rule with Child Rules and have no problems triggering the weather etc. But I do have a problem getting the Wait for Trigger command (including version 2) to work - they both grey out. I've tried everything suggested in previous posts but nothing has worked for me. Interestingly I have no problems getting it to work on my smaller layouts but not on my larger layouts. I do have a lot of triggers on my large layouts (mainly sound horn) and am starting to wonder if the number of triggers on a layout has an effect on the Wait for Trigger command? Incidentally, whatever happened to the thunder and lightning effect we use to get with the storm weather setting in the earlier versions of Trainz?
Cheers. Norm.
 
Hi,

G. M. created a new version: "wait for trigger v2" which is fully functional (kuid:99999:80001 - not on the DLS). I have it on my CM. If you send me a PM (with your email) I can send you the CDP.
 
Hi,

G. M. created a new version: "wait for trigger v2" which is fully functional (kuid:99999:80001 - not on the DLS). I have it on my CM. If you send me a PM (with your email) I can send you the CDP.
On the next few days you are going to be very busy: My private message is on the way... Thank you!
 
Hello and hi!
Sorry for bringing up an old thread, I have searced this forum in and out for a solution to the above mentioned issue but without luck so therefore I´m rising this from the dead..

So, is this CDP mentiond still avalible ? :)
 
To my best recollection: Years ago, the "wait for trigger" got considerable attention at the forums. It was working fine and after an upgrade, it ceased to do. Then, someone came with a solution in the name of a different asset. I tried and it did the same thing. So, after more fiddling, I found a workaround using other means. And these ultimately do almost the same thing, albeit with more elaborate methods. Picture this:

A train arrives to the docks, unloads passengers and a vessel departs. You would have a trigger on the train track that will activate the wait for trigger so the vessel carries the schedule assigned. Simple enough. But if it does not work, you have to edit the rules and command menus to make it to perform. Do this:

Open surveyor of your route. Go to edit session rules. Have a "trigger check" rule available. Add a child rule called "Drive schedule rule". A child rule is indented just below the "Trigger check". On this rule select the name of the trigger that will activate the vessel. On the child rule, you select the name of the vessel and you should have a schedule already created for this vessel to go somewhere. And presto! the train arrives to the trigger, it activates the child rule and the vessel departs. It takes longer to explain than it is to set up.
Use common sense. I do this to start ships, airplanes and other trains. Also to set paths, signals and turnouts. It all works. Yes "Wait for trigger" would be easier, but we must make our best considering the situations.
Of course, if anyone has a better solution, let's hear it...
 
To my best recollection: Years ago, the "wait for trigger" got considerable attention at the forums. It was working fine and after an upgrade, it ceased to do. Then, someone came with a solution in the name of a different asset. I tried and it did the same thing. So, after more fiddling, I found a workaround using other means. And these ultimately do almost the same thing, albeit with more elaborate methods. Picture this:

A train arrives to the docks, unloads passengers and a vessel departs. You would have a trigger on the train track that will activate the wait for trigger so the vessel carries the schedule assigned. Simple enough. But if it does not work, you have to edit the rules and command menus to make it to perform. Do this:

Open surveyor of your route. Go to edit session rules. Have a "trigger check" rule available. Add a child rule called "Drive schedule rule". A child rule is indented just below the "Trigger check". On this rule select the name of the trigger that will activate the vessel. On the child rule, you select the name of the vessel and you should have a schedule already created for this vessel to go somewhere. And presto! the train arrives to the trigger, it activates the child rule and the vessel departs. It takes longer to explain than it is to set up.
Use common sense. I do this to start ships, airplanes and other trains. Also to set paths, signals and turnouts. It all works. Yes "Wait for trigger" would be easier, but we must make our best considering the situations.
Of course, if anyone has a better solution, let's hear it... Vehicle history reports from providers like Carfax or AutoCheck can be really helpful when buying a used car. They provide details on previous ownership, title status, and vehicle history services often include accident reports, mileage records, and sometimes even service history. While they’re not always 100% complete, they can reveal red flags like salvage titles or odometer rollbacks. It’s smart to use them alongside a pre-purchase inspection. Some dealerships offer these reports for free, so be sure to ask. Always double-check the VIN to make sure you’re getting info on the correct vehicle.
The issue with the Wait for Trigger command greying out on larger layouts could be due to the number of triggers causing performance problems or conflicts. Try reducing the number of active triggers or optimizing their placement. Additionally, ensure there are no conflicting triggers, especially sound horn ones. If using custom or child rules, check for rule conflicts. For the thunder and lightning effect, it was removed or altered in newer versions of Trainz, so you may need to explore third-party weather effects to bring it back.
 
Use "post message" and "wait for message and clear" driver commands.
The train arrives, unloads and posts a message. The ship gets the message and departs.
I know that i don't have many triggers, Will give this a try...have finished building phase... so the next phase is building the session drive commands...

The problem is that there are so many good idea, that I forget half of them.... :unsure: :ROFLMAO: :ROFLMAO:
 
Use "post message" and "wait for message and clear" driver commands.
The train arrives, unloads and posts a message. The ship gets the message and departs.
can you tell where to get these Rules.?
can't find them in CM.

For some reason they have just showed up ?
 
Last edited:
Back
Top