xracer Posted August 18, 2013 Posted August 18, 2013 - As recommended mission building style the manual states that if possible we should use an EVENT in Triggers so to free up CPU cycles. The below setup works but if i change the CONDITION from UNIT DEAD to GROUP DEAD it doesn't seem to work. Why is that? The CONDITION should be evaluated every time a UNIT is DESTROYED so when both units on the site is DEAD i should get the message? Bug? System spec: Intel Core i7 920@4.2Ghz (stable, 65degC fully loaded), EVGA GTX-780, Asus P6T Deluxe V2 v.5.04 BIOS, Saitek X52, 1TB/500GB WD HD for system/storage. Kingston SSD 120 GB for DCS, 250GB Samsung 840 SSD for the rest. 16GB Kingston KHX1600C9D3 Memory, 9 GB Pagefile, EK HFX-240 Watercooling, Corsair HX-1000 PSU. HAF-932 Tower, TrackIR-5, Win64Ult [sIGPIC][/sIGPIC]
Grimes Posted August 18, 2013 Posted August 18, 2013 It is a bug that is already fixed within the testing build. Basically when the event is passed it doesn't register that the unit is dead yet. If another destroy event occurs, the message should appear. Side note: In the grand scheme of things, the triggers don't exactly take a whole lot of CPU cycles, so the events are more or less a further narrowing down of when you might want certain logic to occur. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
xracer Posted August 18, 2013 Author Posted August 18, 2013 Ok, thanks for the info! System spec: Intel Core i7 920@4.2Ghz (stable, 65degC fully loaded), EVGA GTX-780, Asus P6T Deluxe V2 v.5.04 BIOS, Saitek X52, 1TB/500GB WD HD for system/storage. Kingston SSD 120 GB for DCS, 250GB Samsung 840 SSD for the rest. 16GB Kingston KHX1600C9D3 Memory, 9 GB Pagefile, EK HFX-240 Watercooling, Corsair HX-1000 PSU. HAF-932 Tower, TrackIR-5, Win64Ult [sIGPIC][/sIGPIC]
Recommended Posts