baltic_dragon

That seems like core DCS problem, I didn't change anything in the mission so it must be something introduced with the last patch. I'll check it but doubt I'll be able to do anything because those things are out of my hands

Hey. We're also talking on Discord, but one of the bug testers checked the mission and it worked well on his end, just as it does on mine. These things are super difficult to troubleshoot, because it seems many factors can play into AI being dumb. Did you try the full (long) repair?

Hey! Yes, I have updated only the A-10C II version, as keeping both running is getting more and more difficult. I'll ask ED to remove the old A-10 version because it takes too much time to constantly update two versions of the campaign, which at this point differ because of frequencies etc. In A-10C II all should work fine, just submitted some final fixes for it.

Yep, internally fixed, will be out with the patch next week. Not sure what changed, but I managed to find a way to make it work again.

@picholas @CH4Pz I think I have M01 fixed, it should be out with next patch. Currently looking into M08 and hope to have that one fixed tonight. The carrier issue in M01 is something new that was introduced (broken) with the most recent update. I know it is a bummer to run into such a problem on campaign start, I am sorry about it - but it is completely out of my hands. That's just DCS EDIT: I confirm I have the issue in M08 nailed and hopefully fixed, running some tests.

OK, I think I got it nailed down, we're now testing if everything works as it should.

Hey, I have no idea with how PointCtrl works, so there is not much I can do to help here. I know I have to revisit the missions and fix some things, but I am currently stretched super thin and hope to have some more bandwidth once the Strike Eagle is out..

@Turboboy997 thanks, glad you like it! Still, we found some issues with this mission and will update it for the next OB patch.

Hey. I'll check, thanks!

Are you flying it in A-10CII or old A-10C? The campaign got an overhaul for the new A-10 and in my tests all worked fine (after some bug fixes). Unfortunately it won't be possible anymore to keep it up-to-date for the old A-10 because there are too many discrepancies, I'll ask ED to remove it from the store for the old Warthog.

@Emuyen it was like this and worked fine, but then ED changed something and FM radio will mess up the AI comms with Tower and AWACS. Since I don't have custom ATC in this campaign, I had to redo all the radio logic for the whole thing unfortunately. I have a few notes / things to fix so I'll have them ready for the next DCS update.

@cheefbird thank you for this report. I will add a note to the briefing to make sure players do the same, this is a very useful piece of advice - appreciate it! @Reflected very well said, LOL!

No, this is just an DCS AI bug in Nellis, been there from the day the campaign was released (didn't happen before, so I assume that patch introducing the campaign also contained this bug). Nothing to do about it but move on, it doesn't happen in any other mission oddly enough.

Well, Biff is only human and even he forgets to include some stuff in his training

@SpartanZero1 are you sure you don't have it switched to FM freq? That is a very common user error. Please check the attached pic.

@AngelAtTheTomb I can't reproduce this on my end - it was suggested above that running a repair fixed the issue. Also, I can't stress enough how important it is to play DLC campaigns with clean DCS, without any unofficial 3rd party mods - as it has been proven that they can somehow break the AI logic and campaign triggers. Something completely out of our hands as mission makers...

Still the case, a year or so after reporting it...

Thanks, reported and I am trying to find a solution.. something changed in DCS super carrier logic and of course I cannot recreate it in the vanilla mission to be able to report it. Will keep you posted.

OK, I'll check it and have it fixed for the next patch. I don't understand why the AI starts doing this randomly in various missions... but hope to find a fix. I hear you. I wish I had some control over this (when I submit campaigns to ED they are 100% checked and work as they should), but each update brings some new bugs and I don't think that will ever change. For all my future campaigns the lesson learned is to keep the same level of fidelity while having smaller strikes and less AI flights to depend on plus give them simpler tasks to make the campaigns more bug-resistant, but this will always be part of the experience unfortunately I'm afraid...

@zaphatit should have worked normally provided you stayed on Overlord freq (which is on AM radio, so if you were still on Guard you couldn't have heard it). But I've added a note to switch back to OL and also one missing line for Pontiac I didn't include, so there is big added value in this report. Thanks!

It is but currently on hold due to crazy workload I have. But I'll get back to it, promise.

All the missions are built in exactly the same way @Turboboy997. I know M3 has some issues (I should have them figured out for the next patch), but can you tell me what is the problem with M4-6?

That's super interesting... I'll make sure to include it in some notes. @fizzymany thanks for the info!

I don't think it happens in all the missions, I'll see if I can reproduce and fix somehow. Will get back to you. @cheefbirdcan you specify in which mission / missions it happens?

Hey! To get the full experience out of this campaign it requires you to be able to achieve goals in certain order, in this mission - to correctly run the intercept on the first bogey before moving to the marauder. I could probably try to work out some kind of fail-safe thing, but that would require delving deep into the mission, altering triggers, checking if all other triggers work and test it a few times to be on a safe side, and I am currently stretched so thin on different projects I just can't commit to such changes. But when I do an overhaul of the campaign at some point like I did for The Enemy Within, I'll have a look at it!