fixed Smoke doesnt break away M02

[CH4Pz]

Just playing back through this campaign and on M02, we both topped off, headed to WP4, contacted overlord, flip tells smoke to take a breakaway, but he just stays on my wing done a full circle but he was still there. Im pretty sure hes meant to go 50nm SE or something, and i have to find him with radar, before searching for a bogey. Anyone else have this issue?

[CH4Pz]

Just tried again, and he cut away this time but instead of flying east he just wandered south into no mans land, so mission seems  pretty borked atm. Think baltic was planning an overhaul of this campaign soon, so hopefully gets fixed there

[baltic_dragon]

Yes, got that reported but can't reproduce in Closed Open Beta. I think it may be a bug introduced in last OB and then quickly fixed internally, so hope this will be OK with the next update. 

[bushido]

I have the same issue. Go to waypoint 4 and nothing happens, Smoke stay on my trail.

After 10 minutes of circling I eventually go to the carrier, perform landing, but mission is a draw.

Do I have to skip the mission or do you plan a fix in the coming days?

[CH4Pz]

10 hours ago, bushido said:

I have the same issue. Go to waypoint 4 and nothing happens, Smoke stay on my trail.

After 10 minutes of circling I eventually go to the carrier, perform landing, but mission is a draw.

Do I have to skip the mission or do you plan a fix in the coming days?

Yeh i just skipped it, looks like the patch might fix it, as he's on the Closed beta

[bushido]

According to the patch it is supposed to be fixed but that is not the case.

I have updated to the latest OB and the exact same issue happens, Smoke just stay on my trail at waypoint 4 after he say "break away"

Could you please release a fix so that I don't have to wait for a next DCS version in I don't know how many months ?

Thanks

Edited January 26, 2023 by bushido

[baltic_dragon]

At the same time I had people reporting that this is fixed for them and it works as it should in M02. It also works OK for me (I cannot reproduce it, so it is difficult for me to fix this - can't release a fix for something I cannot reproduce). We're in touch with ED to try and find a global fix for this... sorry about that. Do you have any 3rd party unofficial mods installed? Found that these quite often break things in more advanced campaigns, even if they are not actively used...

[bushido]

Yes actually I had mod for the DCE campaign. I have deleted everything, re-try and this time it works as intended.

So the mod might be the issue. Solve on my end, thanks.

[baltic_dragon]

Glad to hear! 

[CH4Pz]

On 1/31/2023 at 7:52 PM, baltic_dragon said:

Glad to hear! 

So i just tried this mission again on the latest patch, and while he breaks away now, he flys directly to the tanker and rejoins (even though he just tanked), instead of flying east and doing the exercise. tbh i didnt wana hang around and wait to see if he does the exercise after as i had already been holding for a while, so i quit.

[Ralphk]

i am having a problem with mission 02 at waypoint 4, the wingman breaks away to get some distance however he goes down to 1000 feet and no triggers happen...

Edited February 9, 2023 by Ralphk

[Ralphk]

i tried the mission again and i noticed the following:

1. upon take off wingman does not rejoin until i finish refueling where he joins to refuel.

2. upon reaching waypoint 4 and break off the fomation to go to the assigned location, he never radios back and flies till he runs out of fuel at 1,000 Ft near the carrier area.

M02 is definitely broken.

[baltic_dragon]

I am extremely sorry. I have been fixing this mission for last two patches and it worked OK. When the patch was out, something new got broken - and these are really basic things. I am not sure what to do with this... the thing @Ralphkdescribes was definitely working on my end for the last update. Unless you are on stable version?

[CH4Pz]

17 hours ago, baltic_dragon said:

I am extremely sorry. I have been fixing this mission for last two patches and it worked OK. When the patch was out, something new got broken - and these are really basic things. I am not sure what to do with this... the thing @Ralphkdescribes was definitely working on my end for the last update. Unless you are on stable version?

All good man, ive done the mission a bunch of times, its just my OCD trying to get 100 on all missions atm!! Cant help but wonder if the background work on the dynamic campaign is creating all this weird AI behaviors atm?? the AI hasnt been following triggers properly since before RODF!

[ocha]

I have a same problem. After the last Open Beta update, Smoke does not rejoin and fly around the Carrier. Although I take off first before Smoke.

However I realized there is a different point in Start up procedure compared with other players who played this campaign. I usually use normal alignment without Stored Heading, so turn the INS swich to "CV" and waiting for 8 minutes to take off. I supposed to don't use "STD HDG" on the Carrier deck, that is a misunderstanding. When I use STD HDG, waiting for 90 secounds to align and take off fast, Smoke rejoin correctly. Hence I suspect that Player stay on the Carrier deck too long from the mission  start, "Follow" task may not fire. 

One more thing, after the AAR with Smoke, There is no conversation about XO's story. When I checked the Comm2 and the display indicate "M" (manual) even I didn't touch Comm2 absolutely. This cause canceled to talk with smoke. so after the AAR I reset COMM2 to Channel1, I could hear the conversation with wingman. Sorry for broken english.

[baltic_dragon]

Guys, I just updated the startup sequence for Smoke, so he takes off behind player for sure no matter how long it takes on deck. Flew the mission all the way to the intercept of the Iranian guy - all the dialogues played, Smoke refueled, rejoined, broke away and did everything he was supposed to. 

If anyone is having trouble with this mission I suggest to uninstall any unofficial 3rd party mods, as well as voice attack which is known to mess up the DLC campaign triggers...