MBot Posted December 30, 2018 Posted December 30, 2018 (edited) The presence of an EWR unit (1L13, 55G6) causes flights with air-ground tasks to ignore their ROE and constantly switching between their designated target and targeting the EWR unit. After destroying their designated target, flights will loiter around the EWR unit, initiating and braking off strafing attacks ad infinitum. This all happens despite the flights being set up to not attack targets of opportunity. It only seems to happen with an EWR unit present. I couldn't recreate it with other radar units. Please see attached mission demonstrating the setup. Thanks for checking this ASAP, as this is a mission breaker.EWR_Target_Switch.miz Edited January 16, 2019 by MBot
RedeyeStorm Posted December 31, 2018 Posted December 31, 2018 A verry old problem that is around since lomac days. I once made a mission with EWR setup far behind the frontline and AI F16’s flew there all the way to attack with guns and to run out off fuel. Thing like that always lead to me putting the game down for a while.
Guille H. Mono Posted January 2, 2019 Posted January 2, 2019 Hi, just tested it. You have to give it a ROE the same way you gave it a 'Reaction to threat'. Solved it by ROE = Only Designated. You have other ROE states You can play like 'Priority designated'.
wrl11 Posted January 2, 2019 Posted January 2, 2019 I have a mission with CAP flights along the coast. The fighters never engaged the EWR until the last update. Very strange. .
Guille H. Mono Posted January 2, 2019 Posted January 2, 2019 I see, I've been experiencing this since few updates ago, it is solved the same way. You have other options to restrict AI behaviour in the ME waypoint menu. For flights with more dynamic tasks (CAP, SEAD, CAS) I would recomend to delete de default task in the ME waypoint menu, wich appears since WP 0 as a continuous task and create your own in a latter WP. Notice tha every time you change the aircraft type in the flight, this will automatically appear again.
Guille H. Mono Posted January 2, 2019 Posted January 2, 2019 Mbot, I modified your mission to make clear what I wanted to explain. I also added 2 CAP examples for WRL11, one simple set up will attack EWR. The other one is the setup I use for CAP and will behave well. You can chek the 'Late activation' box of each if you need a more clear tests. I Hope it helps!EWR_Target_Switch how_would_i_doit.miz
MBot Posted January 2, 2019 Author Posted January 2, 2019 Hi, just tested it. You have to give it a ROE the same way you gave it a 'Reaction to threat'. Solved it by ROE = Only Designated. You have other ROE states You can play like 'Priority designated'. This doesn't work. I checked your sample mission and it displays exactly the same problem.
Guille H. Mono Posted January 3, 2019 Posted January 3, 2019 (edited) Sorry I totally missed the point of your thread and mixed others problems in my replys. Let me add some considerations: - I'm on OB latest build. - I've done further testing with your setup: it egresses to WP2 but never in a straight line and eventualy starts tu turn in circles. No atemps of starfing attacks. - This behaviour decreases as I move WP2 to the South, or the EWR to the North. It will leave the area towars WP2 after a minimal amount of erratic fly. - Tried to force "switch to Waypoint two" via trigger activated when target is destroyed with no luck. - Tried to replicate your setup but changing task 'attack Group' for its equivalent in 'enroute task' with no luck. - What ROE do You expect them not to ignore if there are none defined in your mission? This is a serious no ironic question, I don't want to seem rude. By experience I think AI allways try to attack by default, so I use as many ways as I know to restrict this Skynet thing. Edited January 3, 2019 by Guille H. Mono
MBot Posted January 3, 2019 Author Posted January 3, 2019 You are overcomplicating things. ROE Only Designate is a default behaviour, it will always be active if you don't set anything else. We don't need to search for workarounds. AI trying to attack EWR without being tasked to do so is a bug that was introduced with the last Open Beta and needs to be fixed. It is as simple as that.
Guille H. Mono Posted January 3, 2019 Posted January 3, 2019 Look MBot, right now I'm the only one who toke some time to see whats happening with your mission. My english sucks, it is a pain to read my typos and I'm not the most advanced ME user but I'm here trying to help, not to argue if this is a bug or to say your complain is wrong. So please take in count what I'm telling you: - I know forcing things with triggers is overcomplicating, I did it for the sake of testing. Ofcourse this is not how it should work. - AI does not attack EWR if given the most basic setup in WP options in my latest OB. AI follows the ROE I give it. It happened to me months before latest OB but hardly affected me because I always: 1.- Delete default enroute tasking that appears in WP 0, add my own when is relevant. 2.- Define a ROE at the begining and set it to change if mission requires it. - There is still the Erratic fly after egress that may be caused by the proximity of EWR to traget and the relative position of WP2 to the elemements mentioned before. It decreases if you change their position. So yes, EWR can be inducing some weird behaviour on the AI. But again, no mockup starfing runs for me. These are my conclusions and I'm not doing more testing until ED or some ME Pro jumps in.
Recommended Posts