baltic_dragon

@JesterIsDead the short version is now internally fixed and will be released with next OB patch.

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!

You just need a DL - having said that, new link4 system is being implemented now and things should be better once it hits the OB. But I have no control over all that and the "dolly sweet" call is more for immersion than anything else in this campaign 🙂

Turn the labels (even as dots) on, that will help with seeing the Clementines. I know I know this mission by heart, but DCS has its limitations. Because of these I would assume people will be using F10 map, otherwise many missions would get ridiculously difficult without live comms ability... from my perspective there is really nothing that can be done apart from removing the only threat there is to Clementine on the way. 

I think I'd do them in order in which they were released, so original R1 first and then Dominant Fury. Also because RO:DF is more advanced and I think a bit more difficult.

Should be fixed with the next update, at least works internally now. 

@DMousetook me a while, but checked it. As to the initial departure, it should be on Comm1 as is - you are asked to switch to Strike only at the RDV point, all looks OK to me.
You are right about the kneeboard and frequencies not matching, fixed - thanks for reporting!

When you hover the cursor (forgot how it is called in F-18, I am too deep in F-15E right now) on the SA page, it should show you the fuel state below the callsign etc. 

Most likely the AI HARM attack is bugged and they are unable to destroy their targets. I will work in a safeguard to explode the SA6 if AI misses (sigh). If things like this continue to happen to the AI, I really don't see the Dynamic Campaign working well... 🙂

@Guican I just checked the mission and it works fine for me, wingman detaches correctly no matter what is the position of the MA. Having said that I found a little bug with reporting MA off which I fixed. 

Probably because it was shot down. While realistic, I think the Grisha is way too effective against the SLAM-ER. I will disable her shooting it down. 

As for the cats, I will update that - although I guess IRL these things would not be briefed at all, so it is my bad 🙂
As for the D/L - it doesn't really matter, the freq is for flavour only because this functionality of Datalink is not simulated at all, it is just ON or OFF that matters 🙂

Yes, this is a new DCS bug introduced with last hotfix I believe.. (sigh). Reported and we need to wait for another fix. 

That might be an option. I will still try to get to the bottom of it, some people reported that disabling the F-14 module in MM does help with CTDs... there also is a potential fix in the changelog. But if anyone tried to roll back and can report if it helps, it would be great. 

OK @Sandman1330, I did a quick troubleshoot (the problem with AI not pushing is a new DCS bug with triggers). 
If you want to give it a shot, please use this mission. For testing run it as standalone. Let me know!

50 is always on mission start. Otherwise the campaign can move back to previous mission. So it is always 50 + whatever is in the guide

OK I was certain it worked that way (ie would allow you to force things). If not I will update the missions for next patch, no problem.