attackUnit and attackGroup is unreliable in antiship roles

[Insonia]

Instead of let "anit-ship -a" do it automatically. I was trying to timing and quantify expend an attack from different waypoint or trigger/script under single flight. Su34 with AshM/ARM, just keep aegis busy. 

Since GUI in CAS role cant select ship as target. I choose anit-ship role and "anit-ship -a" action was removed in my flight.

It seems something preventing next attackUnit and attackGroup applied on the same target. Only the first attack command on new target is performed. Apply attack command on same target at later waypoint is unpredictable. most of wp attack were ignored, depends on different groupAttack, expend and attackQty configurations, very rarely few attack actions beside the initial one was performed.

I have tried using stop condition or poptask()/ resettask() then pushtask() to clear potential stucked actions. No luck. regardless what i do. most likely only the first attackUnit or attackGroup waypoint was working.

Although GUI wont allow user target navy unit under CAS role from beginning, switch antiship back to CAS or manually edit the mission lua will work. Under CAS attackUnit and attackGroup works fine in rest of waypoints. Only the attack pattern and quantity is different.

Im still working on constructing a miz that isolated and reproduce this issue.

 

Not sure it's AI thing or mission editor issue. reported or not. Please move if necessary.

Edited May 2, 2023 by Insonia