Triggers don't work anymore

[Reflected]

All week I worked on a mission full of trigger zones:

 

https://www.digitalcombatsimulator.com/en/files/2255088/

 

Now I flew it after the update, and NOTHING happens when I enter the trigger zones. Before the update everything worked like a charm, I played the mission like 30 times. What is going on here? :(

[Reflected]

Bump. Can any one of you experienced mission makers check out my mission and let me know why the triggers don't work anymore please? Thanks a lot in advan e!

[feefifofum]

Uh oh this doesn't bode well haha...

 

Do you remember what trigger you used to detect friendly units entering the area?

[feefifofum]

Okay, had a look.

 

It appears you are using PART OF GROUP IN ZONE to detect whether the player aircraft has entered a specific area. Try changing these triggers to UNIT INSIDE ZONE, here's why:

 

Since DCS 1.5 PART OF GROUP IN ZONE has been unable to detect client aircraft in a multiplayer session. If you were playing your mission in multiplayer or on a dedicated server PC, none of your triggers would fire as DCS doesn't recognize your client Hueys as part of the group.

 

They can still detect client aircraft at the individual unit level, you'll just need to change the pilot name to something recognizable.

 

Note that ALL OF GROUP IN ZONE and PART OF GROUP IN ZONE still work just fine for AI; if you need this function for client aircraft things can get a little messy. For a two ship it would look something like this:

 

Triggers -

All client in zone (1 ONCE, NO EVENT)

Conditions-

UNIT INSIDE ZONE (helo1, thezone)

UNIT INSIDE ZONE (helo2, thezone)

OR

UNIT INSIDE ZONE (helo1, thezone)

UNIT DEAD (helo2)

OR

UNIT INSIDE ZONE (helo2, the zone)

UNIT DEAD (helo 1)

Triggered actions-

MESSAGE TO ALL ("Everyone who is alive is in thezone", 10)

 

 

If you're handy with .lua you could probably set up something a little more elegant but for something small scale that should work fine. Only looked like a few triggers in there. :)

 

Good luck!

[Reflected]

Hey, thanks a lot for the advice, I would never have figured it out by myself. I will try as soon as I get home. Fingers crossed!

[Ranger79]

Unfortunately, PART OF GROUP IN ZONE is not working in SP missions when the user is PLAYER since yesterday's patch. Many of my triggers in OPF use this command, hopefully it gets fixed soon.

[feefifofum]

Haha yeah they're gonna need to fix that one...we need at least one working trigger to detect player aircraft. :lol:

[Reflected]

Thank you sooo much, I changed it to "Unit inside Zone", and it solved the problem!!!!

[FlightControl]

Maybe this is also a source of inspiration. Approach zones through coding...

[MasterZelgadis]

Wow... I like ALWAYS use "Part of Group in Zone". Seems I have to change somewhat like 200 triggers now. Not to forget check my old missions...

[Grimes]

You could wait for the next patch before deciding to do that. Considering these mission bugs effect a bunch of payware campaigns, fixing it is a high priority.

[feefifofum]

I do recommend ditching PART OF GROUP IN ZONE for anything you plan on using as a multiplayer mission; any GROUP related function has been broken in multiplayer since 1.5 for anyone besides the host of the session, including but not limited to PART OF GROUP IN ZONE, SEARCH THEN ENGAGE GROUP, and GROUP ALIVE LESS THAN to name a few.

 

For single player ops, as Grimes said, I wouldn't bother. I expect we'll see a patch to resolve the SP issues sooner rather than later.