AI SEAD Escort flies significantly far away from encountered threat before attacking

[SnappyComebacks]

Setup:

• Three Blue AI flights (Package)
  • ToBeEscorted:  Flight flying from WP0 to WP1
  • SeadEscort: Flight with SEAD main task and Escort advanced options task, escorting "ToBeEscorted"
  • AirEscort: Flight with Escort main task and Escort advanced options task, escorting "ToBeEscorted"
• One Blue AWACS
• One Red flight flying parallel and in opposite direction to the package, offset by a distance, with "Nothing" task
• One Red SAM site (SA-3) near the package's flight path

Expected:

• When SeadEscort reaches the Engagement Distance of the Red SAM site, the SeadEscort flight engages the SAM site in a reasonable amount of time.

Actual:

• When SeadEscort reaches the Engagement Distance of the Red SAM site, the SeadEscort flight flies directly away from the SAM site to about a 50 mile distance from the SAM site, then return and attack the SAM site.

Mission, Track, and Tacview attached.

AI_SEAD_Escort_FlyAway.zip

Edited May 14, 2022 by SnappyComebacks

[toutenglisse]

1 hour ago, SnappyComebacks said:

...When SeadEscort reaches the Engagement Distance of the Red SAM site, the SeadEscort flight flies directly away from the SAM site to about a 50 mile distance from the SAM site.

Mission, Track, and Tacview attached.

AI_SEAD_Escort_FlyAway.zip 679.48 kB · 1 download

You've deleted the SEAD task in wpt actions and put "escort task" in first place - that means that as long as escort isn't over not any of following options are active. I've put wpt actions in correct order (sead - all sead options - formation and then "escort") and Vipers engage SAM TR as soon as possible.

AI_Escort_Testing.miz

[SnappyComebacks]

I deleted the SEAD task in waypoint actions on purpose.  I do not want the SEAD escort to attack every SAM site on the map, just the ones within the engagement distance.  In the modified mission you shared, the SEAD flight attacks the SAM immediately, instead of when the flight reaches engagement range.

Edit:  In the shared mission, the distance between the SAM and the SEAD flight is almost immediately at engagement range.  You can test this by moving the flights starting position further away.

Edited May 14, 2022 by SnappyComebacks

[toutenglisse]

1 hour ago, SnappyComebacks said:

I deleted the SEAD task in waypoint actions on purpose.  I do not want the SEAD escort to attack every SAM site on the map, just the ones within the engagement distance...

I overlooked that, but it's obvious regarding escort options. To be more specific the option responsible of your issue for not being enabled before "escort", is Reaction on Threat - Evade fire.

[SnappyComebacks]

I have tried the following waypoint actions:

I removed the Reaction To Threat action and removed the Jamming action as well.  Still no change in behavior.

[toutenglisse]

55 minutes ago, SnappyComebacks said:

I have tried the following waypoint actions:...

You misunderstood me.

AI_Escort_Testing.miz

Edited May 15, 2022 by toutenglisse