DD_Friar Posted January 18 Posted January 18 (edited) Salute Please may I ask was it the intention that using the new feature added in the December release should enable us to stop the marker smoke as soon as the command is issued? and not have the 5 minute plus delay we have at the moment? For example I am using the below triggers but the smoke does not seem to stop when the second trigger is activated? Please can someone who has used this new feature advise? Edit : I actually cannot see the command as specified in the release notes? regards DD_Friar null Edited January 18 by DD_Friar Visit the Dangerdogz at www.dangerdogz.com. We are a group based on having fun (no command structure, no expectations of attendance, no formal skills required, that is not to say we can not get serious for special events, of which we have many). We play DCS and IL2 GBS. We have two groups one based in North America / Canada and one UK / Europe. Come check us out.
landstorm Posted January 18 Posted January 18 maybe if you upload the ME file so we can test it and help if we can is better
Honez Posted January 20 Posted January 20 Put it on "repetitive action" and it will keep going till you turn it off with a flag or trigger. Same goes for flares.
cfrag Posted February 4 Posted February 4 To me, the big problem is that the 'effect smoke stop' action is (another) API call that's currently not available (AFAIK) from scripting for the smoke that is created with smoke(): we have no ID to reference the smoke to stop. I'll have to investigate if smoke() now returns an ID that can be used, and if it still turns off by itself after 5 minutes. Or many effectSmokeBig now accepts colors? If so, hopefully the known smoke colors, not the smoke generator (smokewinder) colors that are different - and different again from flare colors. What a mess. Methinks the DCS API downslide is accelerating.
buur Posted February 4 Posted February 4 (edited) vor 36 Minuten schrieb cfrag: To me, the big problem is that the 'effect smoke stop' action is (another) API call that's currently not available (AFAIK) from scripting for the smoke that is created with smoke(): we have no ID to reference the smoke to stop. I'll have to investigate if smoke() now returns an ID that can be used, and if it still turns off by itself after 5 minutes. Or many effectSmokeBig now accepts colors? If so, hopefully the known smoke colors, not the smoke generator (smokewinder) colors that are different - and different again from flare colors. What a mess. Methinks the DCS API downslide is accelerating. You can stop the smoke via API. If you trigger the smoke with local someZone = trigger.misc.getZone('smoke').point trigger.action.smoke(someZone , 3,"uniqueName") You can stop it with trigger.action.effectSmokeStop("uniqueName" ) The unique Name does the trick edit: example mission added caucasus_smoke_test.miz Edited February 4 by buur
cfrag Posted February 4 Posted February 4 50 minutes ago, buur said: You can stop the smoke via API. Thank you so much! That helps a lot. <blush> Did I miss that somewhere in the docs? Also (will check myself asap), will the smoke still time out after 5 mins when we supply a name?
buur Posted February 4 Posted February 4 vor 9 Minuten schrieb cfrag: Also (will check myself asap), will the smoke still time out after 5 mins when we supply a name? Haven't tested.
cfrag Posted February 4 Posted February 4 1 minute ago, buur said: Haven't tested. Just did, and thank you for your example miz. Answer: smoke WILL TIME OUT AFTER 5 MINUTES, so you will have to continue re-starting a smoke started with smoke() (obviously this is not required for an effectSmokeBig() ) Here's a demo miz (doesn't require mods) for the frogfoot. requires 5 minutes worth of patience. Thank you @buur again for the info! smokin zonet.miz
Recommended Posts