Mission 10 - Rotor Bugged *Spoilers*

[Gilligan]

Encounter a bug today regarding Rotor's AI behavior while playing through Mission 10. I'm not exactly sure what happened, and I don't have a track file as my wife was rushing me to wrap up and go get groceries, but I do have a tac view file if that helps diagnose what's going on.

Mission went as follows:

Took off from Akrotiri, ingressed through silver, dropped GBUs on the Fan Song and Low Blow at Mezzah. 

Spoiler

Had Rotor Engage Two Pop up SA6's and an SA11 with HARMs. All kills. Strike went as planned and both flights of strikers hit their targets and egressed.

During Egress the Mig 29 attack triggered but I kept flying on to waypoints 11, then 6 to egress silver, 6 being on a north easterly course from waypoint 11. I got the radio dialog option with rotor thanking me for not engaging with the Migs, then about 30 seconds after that dialog ended, he came back on the radio, chastised me for choosing to engage with the migs (Which I did not, I was still heading to WPT 6), and turned nose hot to engage. 

I followed him initially, but then decided that maybe if I could get to waypoint 6 and trigger the egress via silver part of the mission he'd come back. I did trigger the egress via silver with sentinel, and got radio confirmation from Rotor that he was with me, however he was still making low passes over mezzah according to my datalink. 

On the way to waypoint 4 the radio conversation between Rotor and Forrest triggered, but all that came through when rotor was transmitting was static, so I just heard Forrest's lines. Rotor was no where to be seen at that time, visually or on DL. 

 

When I checked the tac view afterwards it looks like he diverted to, and landed at An Nasiriyah after dodging AAA and the SA13 at mezzah.

Oddly the tac view did not show his 2nd and 3rd HARM launches.

Tac View Link:

https://www.dropbox.com/scl/fi/3e7zyho7x3cl27zpte64s/Tacview-20241222-133426-DCS-LOWOS-Mission-10-FINAL.zip.acmi?rlkey=zeiu46txjfn3ck5h78ic5b53x&st=o4yw4y66&dl=0

 

Edited December 22, 2024 by Gilligan
Link Added

[ChillNG]

7 hours ago, Gilligan said:

Encounter a bug today regarding Rotor's AI behavior while playing through Mission 10. I'm not exactly sure what happened, and I don't have a track file as my wife was rushing me to wrap up and go get groceries, but I do have a tac view file if that helps diagnose what's going on.

Mission went as follows:

Took off from Akrotiri, ingressed through silver, dropped GBUs on the Fan Song and Low Blow at Mezzah. 

  Hide contents

Had Rotor Engage Two Pop up SA6's and an SA11 with HARMs. All kills. Strike went as planned and both flights of strikers hit their targets and egressed.

During Egress the Mig 29 attack triggered but I kept flying on to waypoints 11, then 6 to egress silver, 6 being on a north easterly course from waypoint 11. I got the radio dialog option with rotor thanking me for not engaging with the Migs, then about 30 seconds after that dialog ended, he came back on the radio, chastised me for choosing to engage with the migs (Which I did not, I was still heading to WPT 6), and turned nose hot to engage. 

I followed him initially, but then decided that maybe if I could get to waypoint 6 and trigger the egress via silver part of the mission he'd come back. I did trigger the egress via silver with sentinel, and got radio confirmation from Rotor that he was with me, however he was still making low passes over mezzah according to my datalink. 

On the way to waypoint 4 the radio conversation between Rotor and Forrest triggered, but all that came through when rotor was transmitting was static, so I just heard Forrest's lines. Rotor was no where to be seen at that time, visually or on DL. 

 

When I checked the tac view afterwards it looks like he diverted to, and landed at An Nasiriyah after dodging AAA and the SA13 at mezzah.

Oddly the tac view did not show his 2nd and 3rd HARM launches.

Tac View Link:

https://www.dropbox.com/scl/fi/3e7zyho7x3cl27zpte64s/Tacview-20241222-133426-DCS-LOWOS-Mission-10-FINAL.zip.acmi?rlkey=zeiu46txjfn3ck5h78ic5b53x&st=o4yw4y66&dl=0

 

Ok thanks I'll take a look. The fight should only trigger depending on your position so wonder if you just caught the edge of the zone as you egressed.  I'll check through and put more safeguards in.

[Gilligan]

That is kind of what I figured, but I also was trying to make sure I flew North/North East towards waypoint 6 while staying out of Lebanese Airspace. I was right outside the SA2 threat ring. In hindsight I probably could have stayed on a more northly heading for a bit longer but once I got that first dialog I thought I was good to drift east a bit.

 

Didn't matter in the end. Got the 100 score, and to be honest this is the first bug I've encountered across both of your Weasels over Syria Campaigns, which, considering their complexity, is no small feat. 

[ChillNG]

On 12/23/2024 at 1:44 PM, Gilligan said:

That is kind of what I figured, but I also was trying to make sure I flew North/North East towards waypoint 6 while staying out of Lebanese Airspace. I was right outside the SA2 threat ring. In hindsight I probably could have stayed on a more northly heading for a bit longer but once I got that first dialog I thought I was good to drift east a bit.

 

Didn't matter in the end. Got the 100 score, and to be honest this is the first bug I've encountered across both of your Weasels over Syria Campaigns, which, considering their complexity, is no small feat. 

Found a slight trigger vulnerability - a 12 second gap where you could potentially trigger both outcomes.  It's possible this is what happened so tightened the trigger up for future update.

[yumemi5k]

I got the same bug in the patched version. I did the recent update, and missions 1, 10 and 13 .miz files show a more recent modified time in windows than the rest, so I believe I do have the updated version correctly. The behavior was just like @Gilligan described in his original post.

[ChillNG]

41 minutes ago, yumemi5k said:

I got the same bug in the patched version. I did the recent update, and missions 1, 10 and 13 .miz files show a more recent modified time in windows than the rest, so I believe I do have the updated version correctly. The behavior was just like @Gilligan described in his original post.

Ok thanks, I'll have another look through, see if I missed anything,

[ChillNG]

Fixed internally, seems the Migs getting a missile off at the eagles was triggering the players involvement.

[yumemi5k]

That could be the case, Rotor called missile in the air out of the blue before heading back to WP9 in my case.