fixed Su-27 "Unwanted Guest" mission - Flight lead doesn't resume escorting Su-25s

[Funky Monkey]

In the "Unwanted Guest" mission for the Flaming Cliffs Su-27, I saw the message saying "(227): 227 flight, resume escort."  But the 227 group that represents the flight lead did not actually resume escorting the Su-25s.  I followed him around in his orbit for a long time while the Su-25s flew home.  Eventually the 227 group did return home but we were too far away from the Su-25s to trigger the last couple messages that are supposed to show up.  I played through this mission twice and saw the same thing happen both times.

I forgot to save the track for this but I've attached a TacView recording showing the Su-25s departing while 227 and I just keep orbiting.

Breaking it down further, the trigger named "227 RTB----------F710---------------------------" did fire because I saw the message it sends.  That trigger also turns on flag 710.  The follow-on trigger is "227 RTB FLG----F711---------------------------".  That trigger waits 8 seconds after flag 710 is set and requires flag 600 to be false.  Flag 600 would only be true if I had initiated combat and I didn't do that, so it should be false.  This second  trigger pushes an AI task for group 227 to escort the Su-25s.  I don't know whether this trigger didn't fire or the AI task didn't work, but group 227 did not break its orbit 8 seconds after the message from the previous trigger.  I also don't know whether 227 eventually returned home because of the trigger or because of something like low fuel.

Tacview-20250331-134512-DCS-Su-27 - Syria - Unwanted Guest.zip.acmi

[NineLine]

So I just flew this mission and everything worked as I expected. We resumed escort when stated and the mission was completed as expected (even with my poor landing). 

If you try again and have the same problem, save a track and I can take a look. 

Thanks!

[draconus]

1 hour ago, NineLine said:

We resumed escort when stated and the mission was completed as expected (even with my poor landing).

You mean the lead 227 returned to escort the Su-25s and you followed him? Then got "Thank you" from the 425 flight near the base? (I'm just guessing basing on the triggers)

I flew this mission and have the same problem as Funky Money. The lead did not go back to escort after "227 flight, resume escort" message. He kept flying orbit so I followed the Su-25s instead and landed but there were no more messages since. Su-25s landed and the lead 227 eventually came back too but something is off with the task push to escort.

Track (file expires after 7 days) - https://limewire.com/d/BqHyd#vOqi8GCqXb

Edited April 1 by draconus

[NineLine]

Yeah, everything worked as expected for me. We escorted the Su-25s back.

[Funky Monkey]

@NineLine thanks for looking into it so quickly.  I played through it one more time and got the same behavior, and remembered to save a track this time (attached).  227 still doesn't resume escort after he says he will.

After playing this, I did a repair with "Check all files" but I checked the md5sum on this mission file before and after the repair.  It was cfb098a38f51596bdd398844002139af both times.

This time around, I also noticed a few typos/voice line issues so I looked through all the triggers:

• Trigger "425 TAXI------------------------------------------": the message says "taxing" when it should probably be "taxiing".
• Trigger "227 TAXI---------F11-----------------------------": the message/voice says to taxi to runway 17 right but all the AI takes off on 17 left.
• Trigger "227 PRE-------------------------------------------": the message/voice says "internals" when I think "intervals" is meant.
• Trigger "F15_5-------------F305----------------------------": the message says "(227)" but I think it's supposed to be from "(F-15)".
• Trigger "227 FINAL-----------------------------------------": the message/voice says "17 right" but the 227 AI landed on 17 left in my playthroughs.

su-27-unwanted-guest_lead_wont_resume_escort.trk

[NineLine]

Ok, I will check again. Thanks!

Oh side note, I realize now I checked this in an internal build, so its possible it was an issue that's been fixed already. 

[Funky Monkey]

This is fixed with today's update to version 2.9.15.9408.  Flight 227 now actually resumes escort a couple seconds after saying he will.