baltic_dragon

If I work on any French module next, that might be the Gazelle. I did quite a lot for the M-2000C and I have a lot of other modules I'd like to work on, even if I really enjoy the Mirage. But I don't plan making any new campaigns for it in the next 2-3 years.

Hey @gszaloki - I suspect you have the Easy Comms set to ON. All my campaigns use realistic radio procedures and won't work if you don't operate the radios correctly or if the Easy Communications are enabled in the options menu. Let me know if that is the case and if not, happy to help you find solution - I am pretty sure the problem is somewhere in the way you work the radios, and not the campaign itself. Let me know!

Thank you @JGS! It is my first and I think I learned a lot since I created it, so hope you'll enjoy the others too!

No news at the moment, but yeah - we need to wait a little for the current situation to be solved.

It is possible that you didn't follow the flight plan and thus the triggers got borked. Did you pass through Waypoint 1 and then turned to WP 2? I recently had someone reporting exactly the same issue and that was the culprit. Unfortunately in scripted campaigns we often rely on "unit in zone" trigger and that is why it is important to follow the flight plan during the missions. Another thing may be the radio setting - are you using the new top radio for FM comms or the bottom (old) one?

Thank you so much @PoliticalPuffin for this feedback, means a lot. And I am happy you're enjoying it! Unfortunately I still don't have any news on part 2, but there is quite a few hours of fun in #1 to be had

Well the helo should take off for sure. I'll check this.

This is a bug that has been there forever and nobody seems to be interested in fixing this. Core DCS AI issue unfortunately that I cannot do anything to fix on my end.. fortunately for some weird reason this only happens in M01.

Thanks! I'll check the mission and update it for next patch. Appreciate you taking the time to report all this!

I'll submit fixed version of this mission for next patch. I have both issues resolved already, going to test it tonight.

OK guys, I found the reason - it seems the SCUD range has changed since the release of the mission and their targets were set too far, so they never fired. This is fixed, but while I am at this mission I'll try to update the whole thing to a new standard. Also fixed the issue with tanker refueling from another tanker.

@Viking 1-1 thanks, will check it.

What was the last thing you heard? Looks like your radios are set up correctly. Perhaps somethig with missed zones. I am wondering as I recently spoke with someone who had no trouble with any of the missions and all worked well in M02. Will try to fix whatever causes trouble.

@Romeo I have M2 internally fixed now, just flew it. While at it I'll add some other goodies and enhancements.

@Rudel_chw feel free to PM me or best hit me up on Discord, happy to chat!

Thank you for kind words! Stealing them and posting on my FB, as positive feedback (and constructive negative of course) mean a lot! And M-2000C Red Flag is not that popular, so always good to share some good reviews. Many thanks!

Hm.. possibly ground AI did something stupid again (their pathfinding ability is pathetic and sometimes new patches break things as well). I'll dry-run that part of the mission and see how they behave. Thanks for the info. @TheFlyGuy can you PM me here or on Discord with extra details what went wrong?

OK I'll have a look and see if I can do something about it.

I am not sure, never used it but I think you'd need to disable it and try again. And run quick DCS repair before just to be sure. I am pretty certain this is the culprit as for most people Biff behaves normally in this mission...

OK will have a further look at it. Just to clarify: the F10 option is not there in the radio menu, correct?

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?