Msg with time delay.
 

I am trying to send a msg to a sub with a time delay.
Made one tricker for a sub to enter a area at a certain speed and depth to launch seals, then a other trigger which will fire after the first ones requirements are met. But i won't get it to work.
Perhaps some one tackled this one already?


Like this:
http://home.hccnet.nl/wico.p/Time%20tricker..JPG

On the first page of the trigger, did you set trigger activation to automatic? Also, I don't think the "completed trigger" clause is needed as "time since trigger fired" implies that it has been completed, however this is probably not the reason for the trigger not to fire. I suppose if you remove the "time since trigger fired" clause, it works? (without any delay of course)

the delay is very easy to manage, and as said inetd, you just have, on the second trigger, to use "time since trigger fired".

But check you didn't made a mistake in the first destination trigger, sending a message to test it when it is fired (message you will remove later).

Yes it is set to automatic.
And the tricker works, only there is no time delay.

I have to admit I never used that time delay feature. But according to OKO, it should work fine.
Try this: Create a new test mission just having the objects and triggers needed for that specific time delay thing. If it works, try to find out what you did or did not compared to your actual misson. If it doesn't, upload the file to a webserver like http://rapidshare.de (free, no registration required) and I will have a look at it.

Another thing that just crossed my mind: If you set the first trigger to refire after t < 60s, then maybe the second trigger will not fire until the first one stopped refiring. (that could be wrong though, depends on implementation of TimeSinceTriggerRefired).

From what I see, it should work. And, I always include the first check (to see if the trigger fired) like you did, as a conditional with the time delay.

Do you have any other triggers or doctrine with the same name? If so, that's a no-no and can lead to strange behavior...

Also, is it possible that the trigger is firing, but the message isn't being "sent"? Make sure the message is being sent to the desired unit (last page of trigger definition).

I use only the 'time since trigger fired', and it always work
may we have a scenario copy of the test please ?

Sure you can have a copy, just PM your mail adress.
It's just a one sub, two trigger map to test if it works.

And the msg's is send Bill, just before the XO: Conn,XO. The Special Operating Forces are away, report.
It's not that the trigger won't work, it's me doing something wrong. :hmm:

I found the problem =>


that was the problem :
ALWAYS send a message to check if a trigger is correctly fired, (on test, and remove the message later)
you didn't do that on the destination trigger
And this trigger wasn't fired because you used an attached goal
If you had made a message to confirm the first trigger, you will saw it is never fired ;)

I changed the attached goal to a normal goal, and the destination goal is now fired when you enter the specific destination zone

But I don't get the point of your goals =>
1th trigger is to check if the seawolf entered the zone
that's OK

but what is the purpose of the second one ?
=> launch seals AND time since trigger fired destination seawolf > 180 sec

launching seals need more than 3 mn so this trigger is just useless, and will always be fired, you don't have to use "time since trigger fired destination seawolf" here

I don't understand what you exactly want to do, can you give me more information please ?

here is the modified mission file =>
http://okof4.free.fr/missions/DW/A-time%20test%202.zip

Could be in the map I send to you the msg was not send correctly. I made numerous maps. :damn:
What I want is, to suggest, the seal launch is seen from the island and later radioed to a sub. LATER thats what the problem is I want a delay in the msg sending. The 180 seconds is just to check it works. And it doesn't.
Perhaps I don't understand the TimeSinceTriggerFired trigger not correct. :hmm:

He he, its fixed. :)
The first (completedTrigger Trigger 3: detect1 ) had to be removed.
Thanks to Jogary. :up: