MitchJC93

Another one for you. I've created a sub routine that checks for spawning and despawning of main AOs. We used it to fault find on our defines a while ago. I've just ran it on your defines and it does have a semi serious issue. It eventually crunches itself into a single AO or an undefined controlled AO error. Here's the final few outputs with controlled zones disabled - When it's enabled it fails well before as there's an issue with it calling an AO when all zones are controlled. I say it's semi serious at it gets to around 15-20 AOs before it gets to broken so I suspect that's within server restart territory. Sadly we use a different method for calling AOs so I can't offer you an instant fix on this one. 14:31:30 "LRG_Log: Next AO: AAC_Airfield" 14:31:30 "LRG_Log: Next AO: Molos_Hill" 14:31:30 "LRG_Log: Next AO: Molos_Hill" 14:31:31 "LRG_Log: Next AO: Molos_Hill" 14:31:31 "LRG_Log: Next AO: Molos_Hill" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: Ochrolimni" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: Ochrolimni" 14:31:31 "LRG_Log: Next AO: Ochrolimni" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: Ochrolimni" 14:31:31 "LRG_Log: Next AO: Ochrolimni" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: Ochrolimni" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:31 "LRG_Log: Next AO: AAC_Airfield" 14:31:32 "LRG_Log: Next AO: AAC_Airfield" 14:31:32 "LRG_Log: Next AO: AAC_Airfield" 14:31:32 "LRG_Log: Next AO: AAC_Airfield" 14:31:32 "LRG_Log: Next AO: AAC_Airfield" 14:31:32 "LRG_Log: Next AO: AAC_Airfield" But here is a cheap one for free Defines\MainAOs.hpp 256 class Aggelorchori_Factory { Changed to: 256 class Aggelochori_Factory { Typo in 'Aggelochori' You've got it commented out anyway but there's the fix if you should need it. Just in case you're not busy Mitch

While I'm here: Suggestion: Missions\Main\SubObj.sqf You still have the old global notifications for task completion. Now that you have EH in place for both I can see no reason why you can't clear down the remoteExec Notifications. This I believe is legacy stuff from before BIS Tasks and now they just stack with BIS_fnc_taskSetState. 77 ["CompletedSub", "AmmoCache"] remoteExec ["AW_fnc_globalNotification",0,false]; 140 ["CompletedSub", "Radio Tower"] remoteExec ["AW_fnc_globalNotification",0,false]; I'll go back to watching from a distance now Mitch

Slightly off topic but not sure where to post this. Error Fix. Missions\Side\secureradar.sqf 141 ["secureRadarTask", "Succeded",true] call BIS_fnc_taskSetState; Corrected to: 141 ["secureRadarTask", "SUCCEEDED",true] call BIS_fnc_taskSetState; Typo in "Succeeded" Will clear down an old task state error that you guys have had. Hope you don't mind. Mitch