investigating M13: Multiple bugs at WP3

[adirtynurse]

After Twister cleans out the SAMs, Chevy 2 won't break off to go and engage their targets.

Also Chevy 2 reports engaging targets once you get to the anchor point, not after twister tells them to do so.

So essentially I still get stuck in the same place.

EDIT: To clarify. After playing this a couple of times, it looks like CY2 runs one of its triggers too early...as soon as you reach WP3 for the orbit. And after twister has triggered all of its actions, CY2 doesn't have the trigger to run again AND that trigger did not work as intended earlier. Long story short, no action compels CY2 to unfollow the player.

Edited November 12, 2022 by adirtynurse

[adirtynurse]

So been trying my hand at this for another few times now. There's another bug I think. Every other time I've played this mission or so, a bunch of F4s jump the Tornados and shoot them down, before all of them can launch their HARMs, not killing all the SAMs and releasing the triggers.

Unfortunately I'm going to have to shelf this campaign again at the same mission for the second time.

[baltic_dragon]

Well.. I spent two months fixing this campaign. But on the very patch that released the updated version, there were bugs introduced to the core DCS system that likely broke most of the campaigns (there are a few problems with core AI mechanics). So what can I say...

[adirtynurse]

18 minutes ago, baltic_dragon said:

Well.. I spent two months fixing this campaign. But on the very patch that released the updated version, there were bugs introduced to the core DCS system that likely broke most of the campaigns (there are a few problems with core AI mechanics). So what can I say...

Thanks for the good work, Baltic. Keep it up!

[adirtynurse]

Still an issue as of now

[adirtynurse]

Do we know if this is campaign side or another ED AI bug? Because it seems like a trigger issue.

[baltic_dragon]

Worked for me before I sent the overhaul of the campaign to ED. Last update introduced some new bugs with the AI (again). I'll see what I can do (if anything).

[adirtynurse]

The only issue I encounter now is that CY2 doesn't break off and do its thing. Once I reach the orbit waypoint Chevy 2 is still following me and the moment I hit the Orbit WP they say something to the effect of "on our way" and that's it. Its all stuck from there on out. I tried to go and attack my own targets regardless (with Chevy 2 flight following me), but nothing. Triggers are out of order atm from the 

[baltic_dragon]

There seem to be a problem with AI not stopping to follow player through numerous campaigns; however I cannot reproduce it in Closed Open Beta, so I assume it was internally fixed after last OB patch and should be fine with the next one. 

[adirtynurse]

Here's to hoping

[baltic_dragon]

Let me know if it still happens after yesterday's update. 

[adirtynurse]

So. Funny thing  I'm playing it right now. On my third try. First try, CY21 broke formation as they needed to, but Twister failed to create desired effects, so got stuck at that point.
Second and the current third Twister destroyed citadel, but CY21 does not brake formation

[adirtynurse]

If you want I can give you my track files. One where Chevy 21 breaks off, but Twister doesn't destroy the SAMs and two track files where twister destroys the SAMs, but Chevy won't break off.

[adirtynurse]

Chevy 2 also reports "in formation" at WP3, not earlier. Is that by design?

[baltic_dragon]

I'll check the mission when able. I fixed this so it makes me pretty damn unhappy that the AI behavior got broken again... 

[adirtynurse]

I get it. If it makes you feel any better, even though I'll end up skipping this mission. Tops remarks on this campaign. Still love it. Something about this whole campaign. I can't put my finger on it. The atmosphere or something. It's just right. I love it.

[adirtynurse]

Okay is it just me that's having this? Same issues in M14. Noble won't break off from Metal. It did the first time I played it (got shot down), second time this happens. Its like with M13, it only works once

 

EDIT: M14 also has a non-applicable IFF code on the kneeboard. IFF is octal codes, but the kneeboard has it 1499, which you cannot input.

Edited January 7 by adirtynurse
IFF

[RimanDk]

I know this response comes almost a year after the last post, but it's still relevant.

My experience on the first try was great - right up until I got shot out of the sky by a surprise Igla at point blank... My bad, I suppose.

Second attempt included an unfortunate accidental ejection between WP2 and 3. We won't go into that...

Third attempt is the one that matters, as it appears it missed a whole lot of triggers.

I flew past WP3 on the left and anchored around it in a circle with a radius to WP3 of maybe 5nm, while climbing to 25k. Chevy 2 remained glued to my wing throughout, where, in my first attempt, I flew right over WP3 and Chevy 2 detached straight away.

Got the migs spawn, pointed East and lit the burner, while CAP dealt with the threat, but got zero indication that the Migs were down. No comms or otherwise. Turned back when the M disappeared from my RWR and a quick F2 step-through of air assets revealed no Migs around. Went back to tracing circles above WP3 and must somehow have gotten accidentally close enough to trigger Chevy 2 leaving (didn't realize what the trigger to get them to leave was, but I guess it's actual proximity to the WP)... to go... on a merry patrol of the area, nowhere near the target, never dropping bombs on anything and never making a radio call for me to follow up with a run in.

After a while just tracing rings in the sky, I finally got a "Good job, everyone! Let's RTB!" call from Twister...

Stepped through the dialogue, then decided to go <profanity> up my target anyway, because I felt rather cheated... but no iglas this time and no active target assets. RTB'ed uneventfully, got a 55 score with zero mention of me launching rockets nor of my rockets hitting anything at all, though I clearly hit some mockups.

[baltic_dragon]

Thanks. I can't promise to have a look at this any time soon, as I have a lot of issues in other campaigns to deal with that were introduced with recent DCS features that require me to go back to old stuff and update missions that used to work for ages. In general for Red Flag I think the revamp of AI flying skills may have made the campaign much more difficult than initially planned. 

I'll have a look at it as soon as I can and will get back to you & apologies for being slow with addressing some of the bugs. Being only one person with full time job and 3 kids makes it quite difficult to follow all the new problems introduced between updates. 

[RimanDk]

9 hours ago, baltic_dragon said:

Thanks. I can't promise to have a look at this any time soon, as I have a lot of issues in other campaigns to deal with that were introduced with recent DCS features that require me to go back to old stuff and update missions that used to work for ages. In general for Red Flag I think the revamp of AI flying skills may have made the campaign much more difficult than initially planned. 

I'll have a look at it as soon as I can and will get back to you & apologies for being slow with addressing some of the bugs. Being only one person with full time job and 3 kids makes it quite difficult to follow all the new problems introduced between updates. 

No worries, mate! I'm mostly managing to figure out the bugs and navigating my way around them through trial and error. Annoying, but still making progress. I did a 4th run at it and passed it with an 80 (was Winchester and couldn't deal with the follow-up).

To any, who might be running into issues: The mission appears to be on a script with rather tight tolerances. You must overfly WP3 within 3nm for everything to trigger correctly! If you do, the script plays out as expected. If not, trouble ensues.

I still didn't get any comms telling me the Migs were down and I got no indication that I should switch frequencies towards the end, so I only learned about additional tasking when an F10 prompt description came up. Suffice it to say, without having heard the radio call preceding it, I was pretty lost on what was expected.