fixed again Mission 2 : Cut away is incorrect + Tanker visual trigger

[MrRoper]

Hi just updated to the new open beta and decided to re-run the Raven one campaign.

 

It seems that smoke goes back to the boat rather than the training area when cutting away and so the next trigger is never hit

Also in 4 attempts I only got the trigger to press space when visual with the tanker twice. 

 

 

[Abr]

Similar problem for me. He went back to the tanker and sat in the observer position instead of going to the training area. Can send track file if required. 

 

Really frustrating how each new patch seems to break these awesome campaigns.

[Captain Fluffy]

Have you guys found any solution for this yet? 

[PowerBlade34]

+1 

Just played this mission twice. I get to WP4, Smoke cuts away and I can tell from TACAN distance he reaches about 30nm away, but the next event is never triggered. I flew in a holding pattern about 15 mins then shutdown the mission both times. I watched a YT video and noticed Smoke should report in after about 10 mins. 

 

Edit: ok, I flew this last night one more time. What I see happening is that Smoke returns to the carrier group as noted above instead of going to his WP 2 Training area (confirmed via F10 map). He seems to circle the group, then he DOES proceed to his assigned WP and announces "Tapes On", but I had to hold over WP4 about 20-25 mins. From there the scripting seems to operate as expected. I have attached a track file. 

Mission02.trk

Edited January 2, 2023 by PowerBlade34
Added track file and explanation

[PorkinsFury]

Does the same for me. Seems to go to the boat after cutting away. Haven’t held long enough to see if he goes back to the mission

[baltic_dragon]

I spent a few hours to update this mission for the last update. It worked. Then the update came out and it broke something else in the same mission. Seriously makes me want to take a long break from DCS... (sigh). I'll have a look, but it may be something only ED can fix.

[arneh]

Same issue for me, Smoke goes back to the boat, and just keeps circling it.

On second mission attempt he did not break away from the formation at all, and just stayed with me as I circled WP4, despite him saying he was cutting away (and I could see initially that he did use the speed brakes in what I assume was an attempt to break away, but then next time I checked he was still in formation).

[baltic_dragon]

@arneh @PorkinsFury @PowerBlade34 I just flew the mission and everything works correctly for me. Smoke breaks away, flies to waypoint 30m away, then turns back and the intercept part begins, and after that the next one. I am on Close Open Beta, so I assume something was fixed under the hood and should be OK with the next update.

[PowerBlade34]

Thank you @baltic_dragon  Will fly again after the next update. 

[baltic_dragon]

Hey guys, I checked again and indeed it was broken. I had to do some magic with triggers (which worked perfectly fine for over 2 years) and it should work fine again, at least it did in my latest test. Please report back after the next OB patch if it does indeed!

[PowerBlade34]

Thank you again @baltic_dragon  I just downloaded today’s OB and flew mission 2 and Smoke now cuts away properly. Thank you!!

[baltic_dragon]

@PowerBlade34 many thanks for letting me know! That's a relief!

[PowerBlade34]

Side question: Is ACLS mode 1 enabled in these missions? (Autoland) I did not see a carrier datalink frequency on the mission card and the ACC datalink fails on the default link 4 frequency. 

 

Edit: OK, after reviewing some old posts, looks like this is a bug in DCS whereby the carrier scripted before ACLS doesn't provide Mode 1, even after being added to the scripting. So I'm assuming the answer here is still No.

Edited January 27, 2023 by PowerBlade34
Found the answer(?)

[baltic_dragon]

It is added on my end to all missions, but there may be some problem with it. I think it olny worked with newly created ones..