baltic_dragon

Thanks, checking!

Possibly. I'll have a look, this is indeed pretty weird...

@Dataduffy @samsi @mlewis I have fixed it now and made the new version of the mission available for download, so you don't have to wait for the next patch. Also, it will be a good teaser for those who haven't tried the campaign yet. Simply grab the mission here and replace it in your campaign folder. Thanks for the report!

We changed the frequencies to use in-game presets that are now available with A-10C II, and this seems to have messed up the system. Just switch to 251 on the middle UHF radio and you should be good, and I'll fix / update it. Thanks for the report & sorry for incovenience!

That is weird, but I'll have a look and update it when working on campaign overhaul. I'd recommend to just shelve it for the time being and wait for the updated version, which will bring a lot of goodies (and make it compatible with taxi directors when these arrive). I am sorry for any inconvinience, struggling to keep up with DCS changes that are cool, but affect the already released missions...

I'll have a look and update everything when doing the overhaul of the campaign, like for Raven One -which I already started working on!

Yes! It is also explained in M01 of the campaign... and this is a wrong forum as this one is for Raven One: Dominant Fury. But you are right, I didn't think that people will load the updated version of the campaign and continue from wherever they were, doh! Facepalm is on me.

That's because we have no EA-6B (or A-6) in the game still. The Hornet is just a placeholder until Heatblur delivers the A-6, which was in the talks when I was building the campaign but still didn't materialise. So this is not a bug. Still, the campaign will soon get full overhaul and I'll address several different things, like I did recently for Raven One - including intense bug squashing

Hey @ouseler - there seems to be a lot of weird things happening with the carrier.. and which affect Dominant Fury. I'll be runnign a major overhaul of the whole campaign with some new features and bug fixing as I did for the original Raven One, but it will take some time - most likely I won't be able to update all the missions for December patch (having an eye laser surgery which will take me out of action for a few days). I'd recommend to wait until the overhaul is complete and then return to the campaign to save yourself some frustration - it is difficult to keep up with some changes being recently introduced to DCS that affects the campaigns - even if ultimately these are good changes. I'll address this and other issues in the overhaul .

Yes, I can confirm - we just tested it with somebody who had this problem but ran the game in MT. In ST the bug disappeared.

I think so. It is a very simple thing. I'll try to submit it again but then you'd have to wait for next OB patch. Just open ME and delete the AWACS

I haven't submitted anything recently, so it didn't come from me.

Hi, I am unable to replicate this bug, even though I have seen it reported several times. For me it always works, as it does for 3 of my beta testers that checked the mission. It may be linked with the DCS bug about the stop flag not working for some people (I know @Reflected was able to reproduce it) and it has been reported to ED, but the fix is out of our hands; trigger-wise everything is as it should in the mission and, as I say, for me it works every time... One other thing that helped some people - to uninstall any unofficial 3rd party mods and run a full repair and then try again.

Hey! I've heavily modified this mission and it is now fixed, should be out together with the whole Raven One overhaul in November patch.

Hm.. maybe try to watch one of the old videos to check if you didn't miss anything (like this one): I'll try to have a look if one of the triggers is not faulty. Thanks for the report!

Hey. The radio silence may be because of the new radio system introduced recently by ED. Looks like all my campaigns will need to be adjusted, which will take some time. We're currently working on Iron Flag to have it ready for the November patch. As for taxi and AI - this is something I have very little control over and it seems that Nellis is much more buggy than any other map...

OK thanks. This is a super complex mission and if one element stops working then other things may fall apart... I'll have it properly fixed as part of campaign overhaul. Still, I'd strongly recommend to switch to OB, because campaigns on stable versions are fixed every 6 months and no wonder they don't work as intended

OK, I'll try to re-work the triggers and the logic when I update the campaign. I need to finish the Raven One first and there is no need for me to try to fix single issues when I'll have to revisit whole campaign with major overhaul in the coming weeks... so I beg you guys for a bit of patience, once I am finished you will get a much more enjoyable experience, promise

Will be fixed with the campaign overhaul, hopefully for December patch!

Thanks! Well, apart from M01 I have no control over the AI landing and the carrier pattern so those things are completely out of my hands... but I am really glad you enjoyed it!

The RTB is linked to time on station so if you take too long to find targets this may happen. Still, I am about to start the overhaul of whole RO:DF in preparation for taxi directors so I'll make sure this mission works as intended.

Yeah, but there can be ways for me to fix it too. In any case I will soon be updating whole campaign (making it ready for taxi directors) so will try to address this issue as well. Many thanks for the report @dggoofy

I'll make sure to update the coordinates when doing the RO-DF overhaul. Thanks guys!

Glad to hear that. I am almost done with the update for the Raven One and I'll get on RO:DF next, fixing bugs and updating stuff - will have it done hopefully for December update.

Hey! I know there are issues with M11 and thanks for this detailed description. I am now working on major overhaul of the campaign (today on M10) and I intend to spend as much time as it takes to make M11 work as well as possible. Now, first JSOW is intended to miss but yeah, the wingman is absolutely necessary for this mission - I’ll fix his behaviour. You can expect a fully refurbished campaign during November update. I’ve already stumbled upon problems with AI flights that took hours to fix somehow (sometimes deleting the old flight and creating a new one from scratch). Thanks!