Build 1567/1567.6: ASW Aircraft & Ambiguous contacts

[HalfLifeExpert]

I referenced this in my older report on the "Code Error" issue that has been fixed with Build 1567.6, but it remains in the newest build. I started noticing this primarily in Fail Safe 3- Morning Departure, but I have encountered it in other scenarios as well, so I think there's an issue that was introduced with Build 1567.

When an ASW aircraft is ordered to engage a submarine contact, and that contact is ambiguous, the aircraft will make one searching pass, and then continue on that exact same bearing unimpeded unless interacted with. Essentially, the aircraft make one pass and just stay on that course until (presumably) they hit bingo or run out of gas.

The aircraft do not return to make another pass unless I manually remove the engagement course and (sometimes) leave the selection of a new course unchosen, only under this condition do they turn back an engage the contact.

Basically, the AI engagement logic of ASW Aircraft needs to be examined and tested because there's clearly a major issue here, which effectively requires babysitting ASW aircraft for them to be effective.

[Raptorx7_slith]

Are you sure the aircraft continues to fly on that course indefinitely? Because yes currently they will fly a bit past their target so that they have time to turn and make their attack run properly. This is to fix another issue we were having where ASW planes especially weren't able to turn hard enough to deploy their torpedoes and got stuck just circling targets. Ill need a save where they continue on that course until bingo like you're describing

[HalfLifeExpert]

Are you sure the aircraft continues to fly on that course indefinitely? Because yes currently they will fly a bit past their target so that they have time to turn and make their attack run properly. This is to fix another issue we were having where ASW planes especially weren't able to turn hard enough to deploy their torpedoes and got stuck just circling targets. Ill need a save where they continue on that course until bingo like you're describing

Sure thing! After your post I was able to grab an example:

Attached is a save from a fresh run of Fail-Safe scenario #3- Morning Departure. This is the scenario where I originally noticed the issue, though it has been present in others. (Side note: This might be my favorite Fail Safe scenario, this issue notwithstanding).

Note the airborne CP-107 Argus (404 Sqn #3) that is starting an engagement pass on an underwater contact that I've marked HOSTILE (which it probably is since I know there's a pair of enemy diesel boats in that area from prior playthroughs).

Note that the contact is ambiguous (several minutes since last detected).

I've run the scenario from this save a couple times, and each time, the Argus makes one pass, and continues on that same course until bingo fuel, as I suspected. (I had previously not let an A/C get to bingo before interfering, so I tested and that's what happened)

I did notice in other scenarios that some ASW aircraft take a little longer than before to turn back for another run, which is probably the WAD you referred to, so perhaps this is an issue related to that that needs a tweak?

I don't believe I've seen this issue happen with subsurface contacts that are actively being detected, rather on ambiguous ones that ASW aircraft would normally conduct tight searches for with sonobuoys and dipping sonar

[Raptorx7_slith]

Perfect, I was able to reproduce it, thanks!

Logged as 0016586