Mission 10: Co-Ordinated Strike Escort VO Bug

[speed-of-heat]

Hi me again

Spoiler

if you progress the mission without pursuing the AWCS, you still get the VO for Killing the AWACS ... Nice shot, I worry about my career as a strike lead etc...  does it spear in or land ? 

here is the Track (the event takes place at just before the carrier so about 90 mins in!)

and here is a video of the relevant bit:

 

[Sandman Simulations]

2 hours ago, speed-of-heat said:

Hi me again

  Reveal hidden contents

if you progress the mission without pursuing the AWCS, you still get the VO for Killing the AWACS ... Nice shot, I worry about my career as a strike lead etc...  does it spear in or land ? 

here is the Track (the event takes place at just before the carrier so about 90 mins in!)

and here is a video of the relevant bit:

 

Thanks again.

Sounds like trigger problem but weird again because haven't happen in tests. There was no track in your message but very informative video. Do you have a tacview track showing what happened to the AWACS?

[Sandman Simulations]

3 hours ago, speed-of-heat said:

Hi me again

  Reveal hidden contents

if you progress the mission without pursuing the AWCS, you still get the VO for Killing the AWACS ... Nice shot, I worry about my career as a strike lead etc...  does it spear in or land ? 

here is the Track (the event takes place at just before the carrier so about 90 mins in!)

and here is a video of the relevant bit:

 

Spoiler

Just checked the triggers. It's possible to go like that if the AWACS crashes to mountains for some reason. I hasn't done it before but everything is possible. I'll make a fix to this.

Did you flew some northern route back as the AWACS to be killed shouldn't even spawn if before player gets close enough? There is a copy-AWACS circling before that and if it crashes it shouldn't fire the trigger. 

Spoiler

I think I found why trigger fired. AWACS was spawned for some reason. It may happen if you fly about 70 miles to north from the planned route. When you are ordered to contact approach that AWACS is deactivated with other non-important units for performance reasons and then it is counted as a kill. I'll fix that.

 

Edited May 11, 2024 by Sandman Simulations

[Sandman Simulations]

12 minutes ago, Sandman Simulations said:

  Reveal hidden contents

Just checked the triggers. It's possible to go like that if the AWACS crashes to mountains for some reason. I hasn't done it before but everything is possible. I'll make a fix to this.

Did you flew some northern route back as the AWACS to be killed shouldn't even spawn if before player gets close enough? There is a copy-AWACS circling before that and if it crashes it shouldn't fire the trigger. 

  Hide contents

I think I found why trigger fired. AWACS was spawned for some reason. It may happen if you fly about 70 miles to north from the planned route. When you are ordered to contact approach that AWACS is deactivated with other non-important units for performance reasons and then it is counted as a kill. I'll fix that.

 

 

I was wrong with my last message. It seems that now deactivated unit is counted as killed even if it hasn't spawned at all. So you are not needed to fly too north to make this happen. Totally my fault.

[speed-of-heat]

No worries, sorry I must have forgotten to add the link for the track I can still do it if it's helpful?

[Sandman Simulations]

52 minutes ago, speed-of-heat said:

No worries, sorry I must have forgotten to add the link for the track I can still do it if it's helpful?

I'm pretty sure problem is found so maybe no need. I'm only wondering what has changed because the mission has worked fine last time I tested it. But need to admit it's quite long time ago 

[speed-of-heat]

Here is the link to the track file i forgot to include escort strike (no AWACS).trk and the ACMI file for the same mission Tacview-20240511-140904-DCS.zip.acmi

[Sandman Simulations]

2 hours ago, speed-of-heat said:

Here is the link to the track file i forgot to include escort strike (no AWACS).trk and the ACMI file for the same mission Tacview-20240511-140904-DCS.zip.acmi

Thanks. My last guess seems to be the most likely explanation.

Spoiler

In your track the AWACS running away when player gets close was not spawned as you flew normal route as supposed. So the only thing that could fire the trigger was when that non-spawned unit was deactivated and then counted as killed.

I'll make a patch to fix this one too but it might take some time to get it out as I just got previous patch submitted to ED.

[speed-of-heat]

no worries, it doesn't impact progression just a little "strange"