fix issue with helo taxi

[amanuense]

if he helo taxi is destroyed no new helo taxi will be called.

an event should be tied to the helo taxi so if the helo taxi is destroyed a new one could be respawned.

[CaiusAjiz]

A cursory look at support/taxi/helotaxi.sqf (lines 72-80, 108-116, 143-153, 166-175, 191-199, 223-229) appears to have code to address the various stages where the helo can crash/be destroyed and re-appear as a menu option 15 seconds later.

I'll go though when I have access to the dedi (or a computer that can run arma3) and check what happens when the helo is destroyed at various stages. I can do this from Sunday.

I'll pick this up. Looking at the above SQF, instead of writing the same check 6 times in the script, is there a way I can define the action earlier and then just call it in, or is it not worth it in this instance?

[amanuense]

https://community.bistudio.com/wiki/compileFinal

There are a couple of other ways but this one can be applied locally

On Feb 6, 2018 06:59, "Caius Ajiz" notifications@github.com wrote:

A cursory look at support/taxi/helotaxi.sqf (lines 72-80, 108-116, 143-153, 166-175, 191-199, 223-229) appears to have code to address the various stages where the helo can crash/be destroyed and re-appear as a menu option 15 seconds later.

I'll go though when I have access to the dedi (or a computer that can run arma3) and check what happens when the helo is destroyed at various stages. I can do this from Sunday.

I'll pick this up. Looking at the above SQF, instead of writing the same check 6 times in the script, is there a way I can define the action earlier and then just call it in, or is it not worth it in this instance?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/amanuense/DUWS-R/issues/16#issuecomment-363447946, or mute the thread https://github.com/notifications/unsubscribe-auth/AL6AvSJnRZvWhrL_Z9QNk2JDPN6C1rwCks5tSGi0gaJpZM4R6P-A .

[amanuense]

Forgot to mention there is a basic difference when calling compiled code. Use call to do inline (useful when you need something to end before you can proceed). Use spawn to call on a separate vm (useful if you want to do something in parallel)

Same thing applies to exec and execVM

On Feb 6, 2018 08:28, "Oscar Alberto Arias Rios" amanuense@gmail.com wrote:

https://community.bistudio.com/wiki/compileFinal

There are a couple of other ways but this one can be applied locally

On Feb 6, 2018 06:59, "Caius Ajiz" notifications@github.com wrote:

A cursory look at support/taxi/helotaxi.sqf (lines 72-80, 108-116, 143-153, 166-175, 191-199, 223-229) appears to have code to address the various stages where the helo can crash/be destroyed and re-appear as a menu option 15 seconds later.

I'll go though when I have access to the dedi (or a computer that can run arma3) and check what happens when the helo is destroyed at various stages. I can do this from Sunday.

I'll pick this up. Looking at the above SQF, instead of writing the same check 6 times in the script, is there a way I can define the action earlier and then just call it in, or is it not worth it in this instance?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/amanuense/DUWS-R/issues/16#issuecomment-363447946, or mute the thread https://github.com/notifications/unsubscribe-auth/AL6AvSJnRZvWhrL_Z9QNk2JDPN6C1rwCks5tSGi0gaJpZM4R6P-A .