baltic_dragon

It looks like in current DCS version the easy comms is being enabled by default after each run of the game, make sure it is set to OFF before running any of the missions. Let me know if that is the case. Most likely the launcher always turns it on by default.

I am almost certain this is because of the launcher. Might talk to ED about this!

Though I guess I should prepare one

Thanks, we'll check it.

Thanks, good points both! Noting down for further fixes.

You know you can turn on invulnerability for the MANPAD part at mission start, right? Using F-10 menu. MANPADs are too dangerous ATM in my opinion, that is why I built this option into the mission.

Hey guys! Is it possible that this also affects my Reverb G2, as OpenXR is also used by WMR?

Thanks, we will check. We spent hours fixing issues there, and it seems something new reappeared. I love the AI and patch cycle...

To use the yardstick you have to set your TACAN as described in the kneeboard - 31 sets his to 34X and you set yours to 97X and then it works. I know you should also see him if you set up 34X, but I went for the way it should be done for flight lead - wingman in real life. Glad you're enjoying the campaign!

Hey, I checked the triggers and everything is set up as it should - and it used to work. I can't do anything about it on my end, looks like core DCS thing...

Perhaps it is part of the Dynamic Campaign AI upgrade... and things will get better eventually. I certainly hope so!

The mission should be fixed now, AI refuses to perform a simple bombing task, so had to include some workarounds that hopefully will solve the matter for good and the attacks now look better than before.

With regard to the shelter - negative, the shelter is correct, 31. Just checked.

OK this should be internally fixed, though a lot of trouble is caused by a core DCS bug with a bombing task for the AI... so can't guarantee it will work as intended until ED fixes things on their end.

We identified the core bug causing this and found a workaround. Trying to implement it now.

This affects a lot of missions in already released campaigns.

@_Delta13_ fixed for next update.

LOL rather a full-time DCS 3rd party developer, I am not part of ED.

Probably nothing. Last update broke A LOT of AI behaviours, so this is probably that. Not sure if I'll be able to fix this or if we need to wait for ED, but I will certainly try.

Thanks for letting me know!

That is interesting. AFAIK there is nothing different there than all the other missions and I never had any issues.. anyone else having similar problems?

Thanks, we're investigating this. There should be the RTB call at some point but it seems the mission waits for too long. Will try to fix ASAP.

I know, but neither me nor my testers can reproduce this at this stage... I have no idea how to fix this as it works fine for most people. I'll think about it some more and also merge the threads.

Yeah, I tend to over-complicate stuff

Must be a DCS thing, trigger-wise all is fine in this mission.. let me know how your second run goes.