kaba

If it is constantly leading to your wingman plowing into a mountain - yes. The behaviour of the wingman here is fully out of my control.

Hey Nealius Thanks for the comments on that mission. I think in a future update I'd like to include an optional CAP flight you can call in if it gets too hot. Until i can find the time to do so, i suggest staying out of the SA 10 WEZ until it goes down to the SEAD flight, then make a quick strike and burn out of there. Thanks

Thanks - So from reading that, it looks like player is delayed if an AI is using a cat at mission start. That is tricky, as many missions have AI on cats at the start... Path of least resistance might be waiting for a fix from ED unfortunately.

I'm trying to work out what has caused this delay at the start of the missions (haven't yet updated on my side). Have AI flights switched which catapult they start from? Or is something else interfered with the cats? That's on hot starts - what about cold starts?

Here's the link to the co-op mission pack. Just throw the F14 folder into your DCS\Mods\Aircraft folder. https://drive.google.com/file/d/1sV1ApFx7R2e2n49A_86HaW3mWtlPMo8G/view?usp=sharing

Hi, the short answer is - there should be! I've had reports that the Co-op missions did not come through in the patch. I've also had reports that the new patch has stopped some people taking off from the carrier I'm hoping for another hotfix. But I can also provide a download link for the Co-Op missions for people who want to revert back to 2.5.5 due to the bugs. Will get this arranged over the weekend.

Hi there, This looks to be a bug with the latest OpenBeta. Carrier starts have been very much messed up. Until this is stabilised by ED I thoroughly recommend reverting to either the prior OpenBeta or to Stable. Sorry that this isn't an ideal solution but I am limited as to what I can do with the available tools.

Hi, this is one of my missions. Something has changed in the latest OpenBeta which has messed up catapult starts, it's the same for some of my F-14 missions. At the moment I'm waiting for the hotfix due for release this week and hoping that this helps, then I will have a look and see if this is still broken. Thanks for flagging this.

Hi, thanks for the report. Can you let me know: Which version of campaign (Cold start, hot start, Co-op)? Which version of DCS you are running? I will have a look. Thanks

Co-op version of the campaign now included (Open Beta 14/02/2020) Key features All missions converted to multiplayer 'single missions' Play with up to two pilots and two RIOs Hot and cold starts possible for each mission - select the relevant slot when joining the mission In-mission options to skip or restart the mission (find these in the ingame Radio menu > F10 submenu) This is still in Beta - please send me any feedback or bugs that you find! As always - thanks everyone for all the kind words and constructive feedback Link to Co-op files if you are having trouble with the new patch: Just throw the F14 folder into your DCS\Mods\Aircraft folder. https://drive.google.com/file/d/1sV1ApFx7R2e2n49A_86HaW3mWtlPMo8G/view?usp=sharing

Beta version of the co-op variant is with Heatblur for testing

Hi, Cold start is on the ramp, engine off Hot start is on the catapult ready to go These are substantially the same, the difference is the state at which you begin the mission for preference. The third (as you say with no indication) is legacy and should not be used - plan is to remove this.

Hi, You are able by default to use both radios from the pilot's seat. You will need to keybind both radio keys in your settings. The binds are called: Mic button UHF1 (ARC-159) Mic button UHF2 (ARC-182) Hope this helps, let me know if not.

Good question - hot start/ cold start are up to date, the third is legacy and should be deleted in a later update. Please use either the cold or hot start versions.

Winchester if you call it in. More generic message if you rtb without calling it in! Because how do they know :smartass:

Thanks for pointing this out - I've tweaked so it should automatically succeed if you RTB after hitting some targets. Should be coming in an update soon.

Im glad to hear you're enjoying the campaign. Ive got a bit more time in the next month to tweak, so please do feel free to provide any feedback or comments.

Air threats are random. Sa6 is timer triggered. AAA and MANPADS switch on in stages if you spend too long loitering. Air threats are a new inclusion. Reason for this change is the feedback from first version that this mission was too easy and a bit stale. I'm not going to change loadout to phoenixes. If the air threat is consistently too heavy to the extent that this is not coming across as a fun mission then I am happy to tweak - but i need your tacviews or more specific feedback (preferably both).

Thanks for the comments . If you could send over a few tacviews from your recent attempts it would be helpful. A lot of time went into getting balance right so it would be best to know which areas are challenging you the most before I make changes.

Thanks, will look at this.

Hey Tiramisu - thanks for the feedback. Sounds like you're having trouble with the 3rd mission, it's a tough one. For me the trick is timing - getting in late enough that SEAD mission is complete, but quick enough that any hostile CAP can't catch you. Annoying about the performance issue - a few people are having similar issues. I can confirm I've got no scripting running in the mission, only standard triggers. This sounds like a bug with either DCS or the tomcat. Do you have a track file we could look at?

Thanks for the feedback guys. A lot of updates and bugfixes have been made in the latest patch. The long-awaited cold start version has also now been included. Co-op version to follow as soon as possible.

Thanks for the feedback everyone. I've made a large amount of changes and bugfixes and hope to have this pushed in an update soon. That's bizarre, the mission logic just plays a sound and sets a flag. Have you had this issue in any other missions? Thanks for flagging - will fix that!

Could you please check to see if this issue occurs outside of the mission? Can you create a quick mission in the editor with just you in the F-14 and an enemy SA-6 site and get it to launch on you, see if this occurs?

Thanks for flagging this Draconus, sounds a bit annoying! Any chance you have a track/tacview I could look at and see if things need tweaking? It sounds as if there needs to be a bit more time between certain things happening. Re the AI, I'm afraid that's out of my hands as a core game issue. Agreed it doesn't look great and hopefully carrier development will improve it. Please do keep letting me know how you find the rest of the missions, the feedback is really helpful.