reported Trigger system not working after Update in 3 of 4 missions I checked.

[ThePutzer]

Here is a short video in map view showing the diff. units starting up with No Triggered Conditions being met.Start Command being met. ALL these triggers were working Before UPDATE.

Link is to my U-tube, will take down after you get a chance to look over. I will also attach Server mission file, that the clip is from. So you can look over. It will be ready in 4K in an hr. Sure hope this helps.

 

-DEEP STRIKE 3-(ROTOR & FixedWing).miz

[ThePutzer]

Another example. Link to few minute vid clip showing prob.  Thanks for any help. I have around 2Doz. missions in line up, Sure Hate to have to ReMake!! 100s' of hrs, hopefully not wasted. in mission creation.

https://youtu.be/YTCTRVOZ4Bs?si=y9UFik1FIN6lKsP6

 

-DEEP STRIKE 4-FixedWing Op-.miz

[rob10]

Have you tried removing all mods from your system yet?  There are several mods causing various issues with the latest patch and removing mods has fixed a very high percentage of new problems people have experienced with this patch.

[Flappie]

@ThePutzer I see most units in your mission spawn when "Part of group in zone" is true. Someone has noticed an issue with this function:

I'll check and report.

Thanks for the heads up.

[Flappie]

It's worse than described in the thread above: the "Part of group in zone" is also true with clients which have not spawned yet. I'll add it to the internal report.

Thanks for the heads up.

[ThePutzer]

O my, so thankful someone else has duplicated, the same Bug/Problem, caused by Last Update.    I pulled Mods, Mist scripts file, an do scripts in a mission. And still had multiple Units and groups spawn without trigger conditions being met!

[ThePutzer]

Dec. 28th Update did NOT fix this BUG !     I opened Deep Strike 1 in editor, made a couple minor changes, (unrelated to this Trigger Prob.) closed it out put in Server.  GROUPS of AI start up all on their own, STILL.  And again,, reminder,, all those units Triggered Properly before previous update.    NO JOY here.

[GeoS72]

I cannot express how disappointed I am right now about the broken trigger system that resulted from the past 2 DCS updates. I've seen triggers act as always true (Part of Group in Zone). I also see triggers not working properly, where part of a group is in zone but does not trigger the action. This is completely UNSAT!

As an example, this MP map that my squadron uses has evolved over 3 yrs. It has worked well until the Dec 19, 2023 update. It has broken a lot of my triggers! It has also caused a lot of other problems: AH-64 with invalid loadout - configured for 16 AGM-114L but the SMS page shows 12 AGM-114L plus 19 FFARs.

@Flappie, please review this DCS log and MP track file. The track file is very large so please follow the Google Drive link.
MP Track file corresponding to this DCS Log: https://drive.google.com/file/d/1wo0XaqV___kq3CzcerHkmoyQOEv_Ukwt/view?usp=sharing

As for mods, the map has the A-4, T-45C, UH-60L, & OV-10A modules. This map worked well with these mods BEFORE the 19 Dec update. If I were to remove these mods then that would break a lot more triggers and functions that is currently broken.

dcs.log

[GeoS72]

Here is the same map & mission set in a Single Player environment. The debriefing shows a lot of _#### events. I presume that is related to the broken trigger system of the map.

dcs.log SP-Jousters PG Map_064 Debrief.log SP-Jousters PG Map_064.trk

[twistking]

28 minutes ago, GeoS72 said:

I cannot express how disappointed I am right now about the broken trigger system that resulted from the past 2 DCS updates. I've seen triggers act as always true (Part of Group in Zone). I also see triggers not working properly, where part of a group is in zone but does not trigger the action. This is completely UNSAT!

I've witnessed the same. Breaks all my missions actually.

[GeoS72]

I also just got word that a Client flying a RedFor aircraft caused the RedFor CAP to spawn over the same airfield. For example, Red Client MiG-21 takes off from Khasab causes RedFor CAP wave to spawn over Khasab. For the record, that event is ONLY supposed to be triggered by BlueFor client aircraft.

What was done in the last 2 updates that caused a complete failure of the trigger system? This condition makes my squadron maps (stress MULTIPLE maps) unplayable!

Has the fault been isolated and how soon of a fix will be available?

[rob10]

See: