NightFlier Posted February 16, 2021 Share Posted February 16, 2021 (edited) Hi guys, I spent all the day long trying to find out why the same CAPs where not engaging with "Search then engage in zone" in the same base mix I'm using for a cooperative campaign. After hours of testing, I found out it happens during night / darkness times! As soon as I changed to a daylight time they worked perfectly. Regards Edited February 17, 2021 by Night Flier Night Flier _________________________________________________________________________________________ i7 9700K, MSI RTX 2080, 32GB RAM (3200 MHz), SSD m.2 1TB, Monitor 32'' WQHD 2560x1440, Windows 10 Pro Link to comment Share on other sites More sharing options...
Grimes Posted February 16, 2021 Share Posted February 16, 2021 Which aircraft? 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 Link to comment Share on other sites More sharing options...
NightFlier Posted February 17, 2021 Author Share Posted February 17, 2021 F-14A (HB model) and F-4 enemy, F-16 and F-5 Blue to be engaged (me) Didn't try others Night Flier _________________________________________________________________________________________ i7 9700K, MSI RTX 2080, 32GB RAM (3200 MHz), SSD m.2 1TB, Monitor 32'' WQHD 2560x1440, Windows 10 Pro Link to comment Share on other sites More sharing options...
Grimes Posted February 17, 2021 Share Posted February 17, 2021 Posting a miz file would be helpful to get an idea of other factors that might be at play. 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 Link to comment Share on other sites More sharing options...
Bunny Clark Posted February 18, 2021 Share Posted February 18, 2021 Search Then Engage is sensor based, the unit will not engage anything it cannon detect. And AI sensor ability in DCS is based on available light levels, sometimes even when they shouldn't be. Oil In The Water Hornet Campaign. Bunny's: Form-Fillable Controller Layout PDFs | HOTAS Kneeboards | Checklist Kneeboards Link to comment Share on other sites More sharing options...
NightFlier Posted February 20, 2021 Author Share Posted February 20, 2021 (edited) On 2/17/2021 at 11:50 PM, Grimes said: Posting a miz file would be helpful to get an idea of other factors that might be at play. Yes, here is a new one but with the same problem: the AI is not engaging, they start to intercept and then they go back soon to the CAP holding again. It's a simple miz with 1 blue vs 2 reds in CAP with Search then engage in zone, 1 EWR. Everyone is within the EWR and the Blue is just out of the zone to be searched for the engagement. If you start and go straight you are in the zone in about 30 sec. I noticed that, given the same light (complete darkness at 2 o'clock local in the PG), changing date gives a different outcome! The mission here attached is on 14th June 2016 at 02:00LT. If you change it to something like 23 June (same time and light stays at an equal level...pitch dark), they engage correctly. TEST Search then engage in zone DARK.miz Edited February 20, 2021 by Night Flier Night Flier _________________________________________________________________________________________ i7 9700K, MSI RTX 2080, 32GB RAM (3200 MHz), SSD m.2 1TB, Monitor 32'' WQHD 2560x1440, Windows 10 Pro Link to comment Share on other sites More sharing options...
Grimes Posted February 24, 2021 Share Posted February 24, 2021 Reproduced it. Weirdly the behavior isn't consistent with different unit types. 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 Link to comment Share on other sites More sharing options...
TOViper Posted February 4, 2022 Share Posted February 4, 2022 (edited) Grimes, for which unit types did you get it work? Currently, the F-4 doesn't respect the action with a radius of 60000m, because once the unit is set to general task "CAP", it starts engaging everything within 400 miles. Edit: the problem here was that the aircraft was set to ROE = Weapons Free Edited February 4, 2022 by TOViper Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1 Link to comment Share on other sites More sharing options...
Grimes Posted February 4, 2022 Share Posted February 4, 2022 IIRC this was fixed. I found my local copy of the mission posted above with the F-4E and it worked as expected. If there is a different situation then I need something showing it to test. 1 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 Link to comment Share on other sites More sharing options...
Recommended Posts