Help wanted with delaying Triggers

[skybaby68]

Question on delayed triggers

 

Hi. Hope all are doing well during these crazy times. Could someone give me some helpful advice on how I go about tackling a delayed trigger?

 

I’ll explain .. I’m creating an L-39C startup and simple circuit tutorial mission with the inclusion of custom kneeboard plates for the start up then switching over to multiple ‘rear seat instructor’ voiceovers for the flight phase.

Take off from Kobuleti, fly a wide left-hand circuit before coming in for run-and-break, Landing circuit with one touch and go and finally landing circuit to stop!

 

All going well with the 33 detailed start up kneeboards in place and instructor voice overs throughout the flight up until the final approach before the touch and go.

 

All voiceovers are using triggers and I have these in place along the runway and climbing out (“rotate, “gear up”, “flaps up” etc) and these are set to ‘switched condition” as I’d like them repeated if the player is back on the runway but over a certain speed, intending to ‘go around’

 

I want to put another trigger in place, on the runway, telling the pilot to “put flaps to mid and full power” to complete the touch and go but this trigger will share the same space as the initial take off triggers of “gear up” etc.

 

A long-winded and perhaps over-complicated way of getting to my question (I’m crap at explaining things on text) ... but my question is ... How do I go about this “touch and go” trigger? I don’t mind it being a ‘ONCE’ trigger as there’s only one go-around before coming into land.

I don’t want to use a ‘Time More than’ condition because one player might take 3 mins perform the ‘start up’ before getting to the runway and another may take 30 mins.

 

Do I use flags somehow and if so ... how? I’m not terribly great with the concept of how the flag system works and so help needed.

Would it be something to do with ‘Time since Flag’ etc?

It’s worth noting that I’ve tried learning lua scripts in the past and it was like trying to read and understand Japanese (no offence intended to

the Japanese language). My brain just doesn’t function like a computer programmer ????

 

It’s probably a simple solution and my waffling has somewhat over confused things but any help would be graciously received and learnt from.

 

Thanks

Edited April 23, 2020 by skybaby68
spelling error

[Exorcet]

I'm not sure if I completely follow your question but it sounds like you want to use Time Since Flag. Have a trigger to turn on a flag when the plane reaches the condition to initial go around and then activate the voice over with a Time Since Flag trigger to get it to play at the correct time.

[Rudel_chw]

... but my question is ... How do I go about this “touch and go” trigger? I don’t mind it being a ‘ONCE’ trigger as there’s only one go-around before coming into land.

I don’t want to use a ‘Time More than’ condition because one player might take 3 mins perform the ‘start up’ before getting to the runway and another may take 30 mins.

 

Do I use flags somehow and if so ... how?

 

Hello,

 

Each DCS trigger is a separate entity, by default it knows nothing about what other triggers have done or might do on the future.

 

Flags are a way to "take note" of events, so that a trigger can now things like if this is the first time it is being run, or if some other trigger has already acted, etc.

 

Flags can either hold a logic value (True or False) or a numeric value (integer only). The most usual is to use a logic value.

 

For your case, you can set Flag 101 (flags dont have names, they are identified with a number .. I keep a Notes text file for each mission, where I document what each Flag stands for) to know if you have just taken off, or if you have already went through this trigger.

 

For example, set Flag 101 to False at the beginning of the take-off run, after you have sucessfully taken off, set it to True. This way, when you get back for the touch and go, your triggers can test for Flag 101 to know if this is the first time or not that you have been passing through that zone.

 

Best regards,

 

 

Eduardo

[skybaby68]

Hello,

 

Each DCS trigger is a separate entity, by default it knows nothing about what other triggers have done or might do on the future.

 

Flags are a way to "take note" of events, so that a trigger can now things like if this is the first time it is being run, or if some other trigger has already acted, etc.

 

Flags can either hold a logic value (True or False) or a numeric value (integer only). The most usual is to use a logic value.

 

For your case, you can set Flag 101 (flags dont have names, they are identified with a number .. I keep a Notes text file for each mission, where I document what each Flag stands for) to know if you have just taken off, or if you have already went through this trigger.

 

For example, set Flag 101 to False at the beginning of the take-off run, after you have sucessfully taken off, set it to True. This way, when you get back for the touch and go, your triggers can test for Flag 101 to know if this is the first time or not that you have been passing through that zone.

 

Best regards,

 

 

Eduardo

Thank you ... if and when you had the time I was wondering if you could do me the great honour of supplying a quick miz file exampling your last incredibly helpful paragraph.

It would help enormously to see it and its parameters and thank you very much for taking the time in writing such a helpful response

[Rudel_chw]

Thank you ... if and when you had the time I was wondering if you could do me the great honour of supplying a quick miz file exampling your last incredibly helpful paragraph.

It would help enormously to see it and its parameters and thank you very much for taking the time in writing such a helpful response

 

OK, here is a simple example, it uses three Flags:

 

98: True if the aircraft has taken off.

97: True if the aircraft has touched the runway at least once.

96: True if the aircraft has landed.

 

It allows for just a single touch & go, it won't detect a second attempt.

 

Here you can see how it goes:

 

-dliW1vNPpA

 

Best regards,

 

Eduardo

L-39C - Take Off, Circuit, T&G, Landing (by Rudel_chw).miz

[skybaby68]

OK, here is a simple example, it uses three Flags:

 

98: True if the aircraft has taken off.

97: True if the aircraft has touched the runway at least once.

96: True if the aircraft has landed.

 

It allows for just a single touch & go, it won't detect a second attempt.

 

Here you can see how it goes:

 

-dliW1vNPpA

 

Best regards,

 

Eduardo

Words fail me to the level of time and detail some people on here go to to help others!!! Many thanks indeed for this.

[Rudel_chw]

Words fail me to the level of time and detail some people on here go to to help others!!! Many thanks indeed for this.

 

:thumbup: no problem ... share your mission once you are content with it :)