Matrix Games Forums

Hello,

I've tested the simple AAW scenario with the 998.14 update. The scenario is a pair of J-20 will engage F-2A with only PL-15, and set up the withdraw rule to leave when PL-15 is out.



However, when a group of J-20 has fired all the remaining PL-15 missiles, they immediately follow the withdraw rule rather than providing mid-courses to PL-15, as they turned around and left those missiles blind. It's significantly reduce the chance to hit F-2A when they can easily fly away from their paths.

I saw the update that the AI/EMCOM rule should be polished for ARH missiles, but it didn't work for J-20 still. I would like to let those jets guide those missiles before following the withdraw rule.

EDIT: Uploaded scenario.

https://cdn.discordapp.com/attachments/ ... launch.png (image link)

We'll take a look, but FYI the "Withdraw when..." settings are for ships/subs/ground units, not for aircraft. Aircraft follow the shotgun/winchester doctrine settings.

Just tried this now, using B998.14. A section composed of Sunliner #1 & #2 launched a full salvo of PL-15s against Green Pawn #9 & #11, and then promptly cranked eastwards to provide mid-course guidance. It remained in crank all the way to terminal endgame, and then resumed offensive approach for the next salvo. So this seems to be working as expected.

Can anyone else give this a try?

Scratch that, I see what you mean. They do not crank when the very last weapons are fired. This is definitely an issue.

Thanks for the notice. I've changed the J-20 side's EMCOM with Shotgun: BVR only, no WVR and withdrawn immedaitely. The result is still the same. Like I said, would like to see BVR is guided to the target before leaving. Winchester didn't work because it also follows WVR engagement and J-20 will not leave.

So we're talking about a separate issue now, yes? "Not cranking as expected for the last BVR salvo" and "not obeying the Winchester directive when down to WVR weapons only" are two separate issues.

Fixed for the next update.

Hi,

I was messing around tonight when I witnessed some behavior that reminded me of this thread. Build 998.15, DB3000 v476. I've attached a save and a short video. Please have a look at 'Flight Thud69'.

Thanks!

EDIT: Actually, I still see it in OP's scenario, too.

Hi izud, I believe this bug was fixed in 998.15

Hi,

I thought so too, but here's an image similar to the one Dysta originally posted: https://i.imgur.com/3WuptDE.png

Regards

ORIGINAL: Izgud
Hi,

I was messing around tonight when I witnessed some behavior that reminded me of this thread. Build 998.15, DB3000 v476. I've attached a save and a short video. Please have a look at 'Flight Thud69'.

Thanks!

EDIT: Actually, I still see it in OP's scenario, too.

Thanks; that was a different code path (have I mentioned that the engagement & RTB logics are VERY comprehensive?), and was quite the bastard to solve. Fixed for the next update.