resolved MissionEditor AI Tasking - Search then Engage in Zone - not working for me

[Mesos]

MissionEditor AI Tasking - Search then Engage in Zone - not working for me

 

Dear reader,

 

By this way I would like to ask/point out about what I think is a bug in the mission editor. I'm playing on the newest version in the OpenBeta.

Whenever I allocate an enemy airplane with the task Search then Engage, with the ROE 'Only designated'  it doesn't work. It seems like the game is not recognizing my commands. I think this because the -a (what i assume is active) is not showing, and the command does not appear white coloured in the list. Below I have a photo of this;

 

Here we see CAP as active

Now when I change that to Search then Engage In Zone it appears as such:

In game it fails to recognize this task and by default will just land at the nearest available airfield. 

 

Does anyone recognize this behaviour? I made missions in the regular version 'stable'  and there it seems to work fine. But since I recently switched to OpenBeta (I am exploring MP) I have this bug. Please help me get this fixed, I rely soley and primarily on this engine and AI tasking to set up my missions!

 

Thank you for your time 

Kind regards,

Duncan 

[Proper Charlie]

At the moment the plane's pilot is thinking "I need to perform CAP while I am en-route, but I'm not en-route anywhere now, so I'll return to base".

If you give the plane an Orbit command, or tell it to follow a bunch more waypoints, it will do its CAP "Search and engage" while it is flying around.

Also, I'm not sure what "Only designated" will do as the ROE, as you are not actually designating a target for the plane to attack.  Fire at Will is probably more useful for you.

[Grimes]

 

4 hours ago, Proper Charlie said:

Also, I'm not sure what "Only designated" will do as the ROE, as you are not actually designating a target for the plane to attack.  Fire at Will is probably more useful for you.

They changed the name of the ROE settings. By assigning a search then engage task it is assigning a target that applies to the "only designated" setting. Basically a "do what you were assigned to do" as the setting. The two settings above it, priority designated and weapon free, allow it to attack other targets. For example if you have a SEAD flight tasking it could more proactively attack air threats. Priority designated simply means it will do SEAD first then worry about air threats.

 

On 4/24/2023 at 9:19 AM, Mesos said:

I think this because the -a (what i assume is active) is not showing, and the command does not appear white coloured in the list.

-a means it was automatically added. 

There is an -x that appears when the enabled box is unchecked. 

[2circle]

I'm having similar issues with this functionality in open beta 2.8.6.41066.1.  I'm trying to set up a DCA with 2 CAPs; a section of F-14's in the North and a section of F-18's in the South.  I select group task of CAP and set up a search and engage zone for the F-14's (the player is on the south CAP so I didn't bother with any AI tasks) that should force it to only engage targets approaching its CAP station.  ROE is weapons ONLY DESIGNATED.  Despite these parameters, as soon as a bandit group appears from the East, the F-14's from the North race all the way (about 80miles) from their CAP (leaving it undefended) to go after bandits in the south CAPs area of responsibility.  Does anyone have any thoughts on to force the North CAP to not engage bandits outside of its AOR?  The search and engage function appears to be broken.

As a separate issue, they were also engaging targets before arriving on their CAP, which I fixed using a START condition for the search and engage enroute task.  

Thank you in advance.