ChillNG

Hi I couldn't replicate the issue, just tested and all worked as should. Also checked a play-through on YouTube and that showed correct behavior as well. The trigger conditions for this are pretty simple, it is just the radio setting so I can only assume the issue lies with this (unless you accidentally pressed backspace when the press space-bar command was awaiting input - this cancels the spacebar command I believe). The Growlers should not be able to be shot down, did some checking and that's an error in the mission so will be corrected asap.

OK thanks, I'll do some more tests, see if I van get them to fire this time, maybe somethings changed in the AI.

OK that's interesting, to be honest in testing I could never got the MANPADS to fire on me...I'm assuming because they couldn't see me in the dark, didn't have your lights left on or anything did you?

Thanks for the comments, appreciate the kind words. Yeah there were definitely a few things I learnt building Persian Freedom, a few CAS technical errors in it for sure so always grateful for the feedback.

I usually go with CCIP, PR. Dive around 30-40 degrees. Always found that pretty successful.

Hi, thanks for the feedback. I'll take another look at the mission, it used to be that the Tornados would get through the MANPADS ok so sounds like an AI tweak that needs some attention

The second line of the nine line is the heading you should use as your final attack heading, just make sure you're at the IP and on the correct heading when you call in

No worries, glad you got it sorted.

Are you on the open beta version of DCS? On steam you need to select this manually under properties.

Campaign Updates - OB 13/04/23: Persian Freedom (updated Feb OB) M14 - Adjusted RPG team position. M8 - Adjusted MANPAD position on last task. All - Updated radio presets Cerberus North M3 - Fixed rare chance for mission to be failed if player doesn't press spacebar. M15 - Adjusted Tornado behaviour to avoid blocking Incirlik runway. Modified Mystic 3 enagement. Adjustements to AI behavour. Kerman Campaign M3 - Added elevation to task 3. M6,7,9 - Adjusted missions to correct for issues with GBU-12.

Ah thanks so much, I hadn't got back round to this yet so that's a huge help, reported to ED.

It won't be campaign related as all the lasing is self designated, but maybe someone else can offer any insight?

Update should be with us pretty soon, I'd normally put the files out but on this occasion it's nearly a third of the campaign that needed a minor fix, so too many to put out there this time. But update has been submitted and ED reporting the GBU-12 as fixed internally so shouldn't be too long a wait. The missions can still be completed no problems though, you just won't be able to max out scores or in some cases complete every task on the mission.

Thanks, glad you're enjoying! Yeah the presets are fixed on the next update, the new ARC 210 radio update for the A-10 messed them all up as ED added a new pre-set option in the editor.

Have you looked on the spoiler above on June 14th 2022. I list all the main strategies you can try there.

Awesome thanks! Yeah the knee-boards/briefings will give you the load-out for the mission ahead, but during the campaign you'll use the following: GBU-12/16 Laser Mavs (self designated with TPOD) Dumb bombs/rockets/cannon - but without TGP so recommend you're comfortable targeting with the DMT. Cluster bombs APKWS No JDAMs used in the campaign. Hope you enjoy the campaign! Thanks so much, hope you enjoy the rest of the campaign just as much!

Hi, thanks for trying the campaign! Kerman shouldn't be overly taxing on any systems, especially either of yours. I'm not sure on how you do what you're asking, but I know some who have tried on other campaigns, I think the encryption of the campaign file is an issue. @SMN did you ever get anywhere with this on Cerberus North?

Just checked the mission, this isn't affected by the bug I mentioned (that is for the AI using GBU-12). Ran a short test but couldn't reproduce any issues, Chief cycled through all the available targets as he should in sequence. If anyone else sees any issues on this mission please let me know and I'll take another look.

Hi, had a look through the mission triggers, was wondering if I'd set another condition that triggers the abort...but nope nothing in there that would do that. Is there any possibility you may have accidentally selected the abort option, or do you use anything like voice attack that would select an F10 option for you? Only other possibility would be DCS randomly turning a trigger on on it's own, which I wouldn't rule out but I've never seen happen.

I'll have a check, there's a new bug affecting the AI when using certain weapons so I'll see what's going on.

Thanks, glad you've enjoyed the campaign so far. There's a new bug affecting the AI when it drops a GBU-12, after dropping the weapon the AI does what you've seen and flies away and cannot be controlled further. This mission is designed to have the wingman support you in taking out targets so this is a real pain in the backside. I have isolated the bug and reported to ED so hopefully we'll see a fix soon, in the meantime I will update the mission to swap out the GBU-12 to 38s instead.

Thanks very much

Thanks!

Thanks v much, good news, think we've found the reason for the same bug thats been troubling me for a while on my Viper campaign, was seeing the same post drop 'fly away' behavior on a mission there. The common factor is the GBU-12, I've tested other weapons and it's this bomb that breaks things - I'll report to ED. For anyone else that runs into this error while we wait for a fix, the mission has fail safe triggers built in so just wait and the mission will progress no problem and your wingman will re-spawn in working order.