baltic_dragon

This should be fixed now. Also, added a sentence to the briefing telling the player to hold between waypoints 9 and 10, which should push the mission forward properly. Thanks for the reports!

@cuervo111 @arneh @Pyrocumulous fixed internally. I had a small explosion set up that would damage the helo and make it look battered and with holes, but apparently someting changed with the AI damage model and the tiny explosion now destroys it. Removed that and the mission will be good to go as of next OB patch.

I'll make sure to fix this for next patch. Thanks! Had some IRL issues that kept me busy..

Appreciate the kind words!

Sorry, it's internally fixed. We added radio presets that are now available to A-10C II, but didn't notice that it sets the one from ARC-210 radio so if you don't tune to 251 manually on the old one, it won't work. Only affects M01 AFAIK and the fix is super simple @PryingMantis - just tune the middle radio to 251 at mission start and you're good to go. Sorry for trouble!

Yes, I'll try to have M14 fixed for the next patch, that is reported. Something must have changed with Super Carrier logic.

Update: I found the problem with SA-6 I think. The mission wouldn't progress normally if the SA-6 did not shoot, which was very stupid mission building tactics from my side. I've added another trigger which will make the mission continue even if the SA-6 does not shoot. Sorry it took me so long!

Anyone else experiencing this after Nov patch? I ran a quick test and the AI seemed to be landing OK, also everything (course and wind dir) is set OK in the ME...

Thanks @Tess! I'm in the process of updating the whole campaign and hopefully squashing the bugs like the one with the tanker... it is pretty annoying that these things get broken every few months without any input from my side, but guess that's life of 3rd party dev for DCS Amazing that you've flown the Tornado! As you know I was asked to work on the one that will come to DCS (although if I am not mistaken it won't be GR4) - but if you'd be willing to share some experiences and help me out here and there I'd really appreciate it!

Chronologically, RO:DF is before Raven One, but I think I would still first fly Raven One after reading the book, and only then move to RO:DF.

Sorry, it turned out that after we set up the presets, it affected M01 because the initial frequency changed. This should be fixed in the next OB. You can also set up the frequency manually to 251 at mission start, should work too!

You likely won't make the campaign to work on Stable build. The DCS is so fluent that the best option is to use Open Beta for the campaigns... And if you get stuck with a bug (which is very likely because Stable release is not chosen based on campaign stability) then you're stuck with it for very long time...

Hm, come to think of it, the new radio system introduced recently does heavily affect older camaigns and it is possible that some messages are no longer played because of this... I am honestly not happy at all with changing the rules during the game and forcing us (mission makers) to spend hours updating stuff that used to work well before and now doesn't, but guess that is life of all products... in any case, I don't think I will be able to return to M-2000C campaign anytime soon to check it (especially that I spent 2 months on general overhaul of it not that long ago)... so can't promise anything, sorry.

Thanks! This is one of those mysterious things in DCS, because the cut away for Smoke before refuel is exactly the same trigger-wise as the one after. For some people it always works (including me), for others it doesn't - and here this is mostly in MT and mostly on lower-end machines but not always. Sometimes third party unofficial mods are to be blamed as well, we've seen that removing them helps (not sure If you have any installed). My advice is to just skip M02 and move on to see how it goes. Thanks!

I don't know what is happening. @YMadDog since the mission is not protected just remoce the AWACS in Mission Editor and save the mission, I sent the corrected version few times... will check with RB.

It is difficult to tell without a track file. It is true that the AI got much more lethal which would probably require full checking of the campaign mission by mission, but given a lot of other things I need to address (like new radio system added to DCS) I doubt I'll be able to change it anytime soon. Will try to have a look ASAP.

This unfortunately is not related to the campaign and has been reported across different campaigns. Do you have lower-end specs of your PC? As these issues are happening much more often with weaker machines. ED is aware and I hope they can find the solution. I tried to solve this on my end with people reporting this bug (I cannot reproduce it) but nothing seems to work, so this is completely out of my hands. This is a problem with the game not registering stop command for a follow task, and thus not commencing the next one (switching waypoint in this case).

It works well on my end every time, but then the ground AI is super finicky - especially if there is smoke or destroyed vehicle anywhere near. Did you fly in ST or MT? In MT these things seem to be more buggy.

Thanks, appreciate it! Also, if I am not mistaken, there is a sale of Raven One series on Kindle so those of you who have not tried them can get them really cheap - and it's totally worth it.

This is a touch and go with the AI.. I've built this campaign ages ago and since then I generally stopped using the stock AI wingmen, because quite often they are dumb as bricks - but changing whole Enemy Within would require A LOT of work, so we have to live with them. The buildings in the missions where they are to be targeted are usually ground units, so try to use general command. But there is not much that can be done here. And thanks for the kind words!

This may be related with the new radio system implemented by ED that will be haunting campaigns for quite some time until we're manage to pinpoint the problematic missions and fix them, so thanks for the report. @Highwayman-Ed tagging you here as well.

Thanks. @Highwayman-Ed can you have a look at this?

It is not yet implemented in DF, as it takes a lot of time. Due to eye surgery I won't be able to have all the missions updated for December patch, but at least will try to focus on a few where I know there are reported bugs, and have the rest ready for January.

Correct - custom Marshal comms were necessary only for M01. Supercarrie handles that part very well, so no need to duplicate.

There may be an issue with the AI helicopters not being able to land... apparently reported to ED. But we'll have a look. Thanks!