Badger633

Thanks @witcohe @Shurik75 Will take a look and address. I will get back to you.

@h4ruuu UPDATE: Just found the issue, a change in AI behaviour. Have provided a fix and will be in next update.

Hi @h4ruuu Could be, there has been a lot of AI updates especially SEAD. Have you got a track of your mission or a Tacview file. If so that would be really useful. Also which version mission are you using, have you tried more than once and are you running any mods.

Hope they do it soon. It’s taken a lot of work adapting every mission in every campaign but your right the new deck crew really adds to the missions. One big issue is the the fact that the Stennis SC currently does not support the deck crew, so had to temporarily change every mission to the Truman.

Hey Petr Good to hear from you. No I don’t, last time I tried it they hadn’t. Told them about it but I don’t think they think it is a big issue amongst all the other things. Will give them another shout.

· All Missions: Updated for deck crew. · Mission 12: SEAD strike fixed.

· All Missions: Updated for deck crew.

· All Missions: Updated for deck crew. · Missions 13 Increased Difficulty: F18’s not taking off fixed. · Mission 3, 6 and 8: F4 and F5 update.

· All Super Carrier Missions: Update for new deck crew. Truman used in place of Stennis until Stennis deck crew is resolved. · Mission 2: Timings adjusted. · Mission 8 all variations: JTAC fixed.

@Kiwigaz Glad you got it working. No need for an apology, I’m always happy to help, we depend on reported issues to ensure all the Campaigns remain working with each update. It’s impossible to test some 80 missions every update.

Hi @Kiwigaz Obviously has worked until now, you are the first to raise it. I will check it out. Could you send me a track. Also are you running any mods? So the problem is you cannot send the message not that they are not responding?

Glad you got it working

Hi @Martuste Just played through mission 11. Deployed the JSOWs with no problem. It could be your method of deployment. Send me a track if you are still having a problem.

Hi @Martuste The inability to release the JSOW will either be the weapon setup or a main DCS bug. Its not normally controlled by the mission scripting. I will jave a look to see if get the same.

@RLTick Hi Yes, it’s not a surprise, there is a change in the SEAD AI behaviour. I have put a fix in place now which will be in the next update.

Yeah, could be, just need to think of a plot in the period after Operation Green Line .

Hi @L4key Thanks, glad you enjoyed. Trying to think what Ford will do next.

Hi @RLTick Found the issue. It appears the SEAD aircraft did something strange and attacked the wrong SAMs which impacted a trigger. (Changing AI responses, you just got to love em. ) Will get it fixed hopefully in next update. Thanks for the heads up.

Hi @RLTick Thanks for the Tacview. Uzi was right to keep orbiting. The problem being for some reason the two Migs which you are supposed to meet and clear first did not spawn for some reason which has broken the mission. Will check this out, as obviously worked fine before. Can you confirm at what level did you play the mission on Veteran, Ace, trained etc. Also can you confirm you are not playing with any Mods Thanks.

· Missions 13 all variants: F18’s not taking off fixed.

· Mission 2 and 5 to 13: Old F18 model replaced.

· Mission 4: Issue preventing success fixed, Old F18 model replaced. · Missions 1 to 3, 5 and 6, 9 to 12: Old F18 model replaced. · Mission 7: Success zone extended in hanger, Matrix fail safe time reduced.

Hi @rajdary They are shouting . Only joking, never really thought about it, maybe in the future. Unfortunately cannot change the existing titles as they have to be kept the same once issued. This to allow updates without impacting people’s existing positions in the campaigns they already have.

@db349 No it is a temporary fix that does not prevent you from passing any of the campaign missions. In fact quite the opposite the fix ensures you will not fail when your wing goes AWOL instead of refuelling.

This now fixed in update of the 16th October 2024