baltic_dragon

I'll have a look at this one. I noticed problems with SCUDs, maybe something that ED needs fixing. I'm wrapping up the Gamblers and then I want to go back to RO:DF and completely overhaul it, just like I did with the Raven One - streamline some things, add some safeguards to triggers, remove all space bar presses for freq changes etc. Will keep you posted. Apologies it all takes so long, but I am still bogged down with full-time job - but as of the summer I am planning to move to DCS full time and then both reaction time to bugs and releasing new missions will be much quicker!

This will be fixed. Thanks for the report!

This will be fixed for the April update!

Hm, according to my notes there were two updates since, but not on the issues you mentioned. At the moment I don't have bandwidth to update older campaigns to include new stuff added to the modules (especially that I have to revisit almost all of the old missions to update them to the new radio system introduced by ED and prepare all the carrier ones for the upcomig taxi directors, on top of normal bug hunting after each update)... so for the time being the answer unfortunately is no, but perhaps after the summer when I'm planning to move to DCS full time I'll be finally able to revisit older campaigns and refurbish them.

I just checked the mission - don't have time to fly it, but trigger - wise everything looks fine. There is trigger zone (pretty large) at WP 1 and there is trigger adding F10 menu to correct group, so I am at a loss what can be the problem there. So you get to WP1 but the F10 does not appear at all?

Weird, we had this mission tested recently and all worked fine. I'll have a look ASAP.

He should spawn every time, but is low and often you won't see him. Still, I'll have a look. CTDs are not my department, these usually are on DCS itself... I'll check what happens there, should finally have some more time in the next few weeks (although I am hard at work on testing and releasing the Gamblers campaign, high time to have something new out!)

I'll check, thanks guys!

I'm afraid not much I can do about the in-game JTAC, the way he works is 100% on DCS and out of my hands... I'll check though.

That is a very old thing and I did it on purpose in several missions because there is no better way of learning things than by using one's own mistakes. Yep. One advice there: don't use specific attack command (attack AAA using mavericks from the north), but the general ones (attack AAA). That tends to help. Sometimes.

I think you have to be in a really tight formation with Biff when overflying the Strip.

Yeah, my impression is that with ARC210 a lot of people are getting very confused with frequencies. As a rule of the tumb always use the middle UHF radio for comms with BIFF, and the front one mainly for VHF transmissions, that should help a lot. We're still looking into problems brought with the new radio transmission system recently implemented by ED, which does cause problems with campaigns and require massive work sometimes from us as devs to adjust older missions. We'll get there!

Sounds to me like the stop trigger bug that is caused by several things on user side (I cannot reproduce these in any campaigns): 1) On weaker machines this tends to happen when flying in MT (try to switch to ST) 2) You have VAICOMM or Voice Attack installed (it messes the triggers often) 3) You have unofficial mods installed (especially UH-60 or C-130) - they also tend to mess up the triggers somehow. Is any of the above true?

Thanks! I know it is complex and best played several times. At least nobody is rushing you

This is an old DCS bug reported ages ago that I cannot do anything about - just AI being AI. Happens to some people, for some it doesn't. Just go ahead and take off I think, until ED fixes AI taxi logic in Nellis on their end nothing can be done. On the bright side it seems this happens only in M01.

Thanks for the report. I'll check this, but the mods (especially UH-60 and C-130) tend to mess up the campaigns quite heavily unfortunately. I will soon begin the whole process of updating Raven One: Dominant Fury mission by mission, logging this report for checking. Also, the tanker bug may be on DCS side, it returns from time to time...

Thanks, indeed this is a very complex mission and I might have missed some things when updating it - like the PICK issue. I'll have a look again. Weird with the fuel, because the tanker is set to unlimited fuel and should not have trouble like this. Smells to me like another AI tanker DCS bug and if it is, may be out of my hands to solve it. I'll have a look still.

Thanks for letting me know! Perhaps it would make sense to contact their devs and talk about it, many people are having this issue.

Please keep me posted. With the new radio there is an unusual number of problems, but many of them are mostly user errors (fortunately!)

@NavalAV8TR for R1 I think only M2 is causing trouble for people for some reason... have fun with the rest!

It should be fixed with the upcoming patch, so on 21 Feb

Will do. I knew this new radio system will bring nothing but problems... working hard to get it working again.

This sounds like the DCS bug with stop flag not being fired for some people. Do you have any 3rd party mods installed? Do you have Vaicom or Voice Attack? Finally, are you on MT or ST? All these things may be the reason.

AFAIK this can be something else, but colours make most sense. I've seen it being used by USMC (as described in one of the books) and also USAF, so I guess this would be the most standard procedure. And thanks for the kind words!

Just replied in the other thread. Seems that all is fine on your end. I'll try tomorrow and see if it works for me. They are tinkering with the Supercarrier for the flight directors so it is possible that something got borked, but all the waypoints and triggers are set correctly for Smoke and I have no idea what I could do to change his behaviour. Will report back.