fixed internally Mission 13 - Sword 22 goes crazy

[Jasonmoofang]

Made 3 attempts at this mission, and in all 3 attempts Sword 22, after being directed to attack Sapphire, seems to do his run in to Sapphire, but does not actually shoot anything, and instead proceeds to go crazy and do a long low level pilgrimage, hugging the terrain, to the hawk site at Bandar e-Jask, where he empties all his weapons into that site - including AIM-9s!

In all 3 attempts I had no choice but to hit Sapphire myself. Sword 22's radio calls are played as I fire on Sapphire, but the mission is otherwise able to proceed with this. It only leaves me with 1 mav for the sub later.

My aim wasn't great and I didn't manage to down the sub in all three attempts - so in the last attempt in a fit of rage I decided to gun the damned thing, very nearly submarining myself in the process. And guess what, it frikkin worked. The sub got gun-sunk

[Jasonmoofang]

Oddly, in mission 14 Sledge 22 also goes crazy Upon reaching WP6 instead of climbing with the rest of the formation Sledge 22 turns 90 degrees east and goes on his own joy ride. This one doesn't affect the mission too much other than Sledge flight being noticeably just three jets after WP6. I played this mission 4 times and it happened every time

[baltic_dragon]

Seems like I am going to have to check almost whole campaign for AI issues. I love when these things happen... 

[baltic_dragon]

@Jasonmoofangthanks for report, indeed Sword was doing some really weird things. Changing maverick type from E to F solved it (nothing else would). Should be fixed for next update. 

Sledge 22 behaviour should also be fixed. 

Edited September 6, 2022 by baltic_dragon

[Jasonmoofang]

Much appreciated @baltic_dragon . Looking forward to flying  the fixed versions in the next update