Mistermann

A sidewinder, a sidewinder, my kingdom for a sidewinder.

Please consider adding a new type of "Skill" option for us when adding module units to a mission. I would like to see a new option that blends client and AI slots. For example, I want to create a 4-ship group for up to 4 human players. However, if only 2 players join the mission, I'd like to see the two remaining slots become AI flights. Yes, we'd have to determine a point where the mission converted the client slot to an AI plane. This would be great for MP mission designers. Thanks for considering.

100% agree with Badger633 on this one, @Metalwerx. Tacview is invaluable in giving you a post flight view into what happened when. Its a great tool. Another tip for you - record your flights. I record every DCS flight with software called OBS (Open Broadcast Software - https://obsproject.com/). I am not affiliated at all and its free. I now have recording of every flight that I can go back on and see what I did right/wrong, etc. Since this is recorded from my vantagepoint, I can see exactly what I was doing in the cockpit and what the instruments were telling me - tacview cannot do this. Coupled with tacview, I have a great system to learn from. Added bonus, my squadmates all use this same tool and we post our post mission videos for all to see. Its neat seeing my jet/helo from my wingman's perspective. Welcome aboard the obsession that is DCS!!

No luck. I honestly stopped trying. I did apply the collision fix and also tried it vanilla - neither worked. As soon as HB's A6 arrives that mod is dead in the water, so I don't hold much hope that its going to be maintained any more. My post has sat unanswered for 2 weeks now and that pretty much sums up the state of that modification, I think. Regardless. Your campaign sounds great. Looking forward to its release.

Sounds good - looking forward to checking out. With Heatblur's recent announcement regarding A6 AI coming this summer, it might make sense to hold off on releasing before they do. I tried inserting the VSN EA6B Prowler mod into a mission specifically designed for the A6 (but used an S3 in place) and it wouldn't work. There might be some bugs in the current A6 mod that need addressing. See this thread

I've played the first 4 missions. None are hot start thus far. Which mission(s) that you've found are hot starts? I'll happily change any mission that isn't a cold start, per @Scotch75 suggestion - this campaign is really good! I highly recommend people try this out.

As long as I don't have to create a static object to copy/share triggers. I have triggers for missions to determine things like when to start (waiting for all players for example) that are just a collection of triggers. Doesn't make sense to associate with a static, I don't believe. Maybe as a way to name the collection??? I agree there are often zones and other elements associated with triggers, but not always. My ask is don't over complicate the ask for simple trigger copies.

Oh heck yeah! My mates and I are on Mission 3 (CAP) and love that you're continuing to add missions. We've had a lot of fun this far. I believe I read this is ultimately going to have 24 missions? Thanks for continuing the investment, @Jenson.

Please give us the ability to copy triggers or groups of triggers between missions. Allow us to share triggers within the community like we can scripts.

Oh wow, this looks great! I have been trying to find this (hiding in plane sight) for a few weeks since starting the Operation Hormuz Hornet campaign found in the ED downloads. In the opening mission the designer uses an S-3 in place of a Prowler. Mission works great, but I was hoping to insert this into it and play with the actually intended AI aircraft. Mission starts with the S-3 on Cat-1 as shown below. When I go into the mission editor and replace the S-3 with the EA-6B, DCS doesn't recognize the Prowler and spawns another Hornet on Cat-1 (its a busy deck at the beginning of this mission) which merges the models. The merged planes break the mission and the clogs the deck. Nothing takes off from Cat-1 or Cat-2. I downloaded both zip files from the OP (shown below) I replaced the content of the first zip with the content from the "Taxi_collision" file. I've also tried is without the "Taxi_collision" file and get the same results shown above. I'll post the mission in case anyone wants to test on their machine. Replace the S-3 with the Unit Name "Dodge 1-1" with the Prowler and fly. You'll spawn into a Hornet waiting for the Cats to free up. Hopefully, I've messed up the install somehow and the Prowler can work in this mission. Thanks in advance to anyone that can assist! Operation Hormuz Mission 01.miz

Glad to be of service! The way my brain works is .MIZ=.ZIP I'm sure there are folks who can elaborate at a much deeper technical level.

You're in the right place. Those .MIZ files are really just compressed ZIP files. Open them with your favorite ZIP extractor. For example, the first mission is called "Persian Freedom TK 1 FINAL.miz". Open it in your zip tool of choice and you'll see this: Open the file called "mission" in Notepad++ and edit per the instructions above.

Thanks so much for confirming this @Ouzo! I posted to Hornet bugs forum so it lands in the right place for ED to review and correct.

I started a thread here - The community confirmed this defect exists beyond just my install. Here's a video showing the problem. I am also posting the track file from the above video. Hopefully this is an easy one to correct. Thanks ED!! TextureIssue_VFA97.trk

Still trying to figure this out. A few more data points. Here are the steps I am taking Enter mission editor for the mission Select the main player jet (HAWK 1-1) from the units tab Select the payload tab (you'll see the missing textures from the fuel tank in the model viewer) Remove the payload from pylon 5 Change the paint scheme to VFA-113 Add the fuel tank back to pylon 5 (it will have the proper texture) Save mission and then FLY to see if the jet looks correct - it will. So ... if I change all the VFA-97 paint schemes in the mission to something that works (say VFA-113), I solve the problem. HOWEVER, I really want to understand why. I don't have any custom liveries loaded so this is completely base. My flying buddies also experience the same missing texture issue and they don't fly modded DCS. I suspect that the base VFA-97 paint scheme .LUA file is pointing to a missing texture. If I create a brand new mission with a VFA-97 jet and fuel tank, the tank is missing the texture. Can anyone confirm this behavior in their system? If so, I'll post a track and bug report for @BIGNEWY

I downloaded a mission the other day that introduced a new one on me ... missing textures. Here's the mission in case anyone wants to look. https://www.digitalcombatsimulator.com/en/files/3325580/ When I flew with my buddies, we all were missing textures on the fuel tank. At first, I thought maybe I was missing the generic tank texture on my computer. What's odd however, is I can't correct it in the ME. I can remove the tank, but when re-selecting it for the mission payload, it always comes back with "missing textures". If I add a brand new hornet to the mission, with the same payload as the one already configured above, it's tank shows up just fine. Its as if the jets the mission designer created for the mission are all tied to a fuel tank with a missing skin. Any of you ME experts out there know how to correct this problem without deleting and recreating all the original jets in the mission? Thanks for the help! EDIT: Further testing outlined below. This might be a bug?

This thread may shed additional light on how to accomplish. https://forum.dcs.world/topic/309795-f6-and-f10-views-available/?do=findComment&comment=5106509

Three. It was a hosted private mission.

Bravo! ... thanks for keeping hope alive .

Known issue for quite some time. Multiple threads combined over the years...

Me and my flying buddies are about to start this campaign. Can't wait to see how we do! Thanks for putting together co-op content. We need more of this from/for the community. Thanks!

In my experience, he does miss shots on moving targets. When this happens, its often due to the target moving behind an object for a small period of time where I suspect he's losing the lase. I personally don't think this is a bug. It'll be interesting to see what ED says. For example, in the video below there are 3 moving BMPs that appear at timestamp 08:00. In the video, I take a shot that misses as does my wingman. 2 shots - 2 misses. From that point forward, however, the 3 BMPs are taken out with 3 hellfire shots from George. Take a look at the VID feed on the last BMP shot at timestamp 09:50 where its clearly moving and George takes it out. Maybe George's lasing skills could use some tweaking? Possibly, never been in an Apache. Love to hear from an SME on this topic. I wonder what @Casmothinks?

A big shout out to Rodz88 for posting this mission in the DCS Downloads - https://www.digitalcombatsimulator.com/en/files/3325649/ This is a great single player mission with some awesome voiceovers and compelling gameplay on the Syrian map. I flew this mission in SP and immediately set forth updating it for Multi-Player. My friends and I flew this the other night and below is my recording of the MP experience. Hope you enjoy.

No issues here. I have tacview advanced through steam and standalone DCS. Running mt.

Thanks for the feedback. I only wish I had done this at the beginning of the video series. Oh well. I will do it for whatever missions we tackle next. Nice design touch having those Ninja Hinds, BTW. Had to be satisfying as the Mission Designer seeing those come into play. As for your question, "yes" is the short answer. For us, this happened a number of times. Nothing that drastically altered our ability to do the mission. Also, I'd wouldn't consider us a group that spends much time "planning". Admittedly, we often find ourselves in-cockpit starting things up and asking "what are we doing in this mission?". So while there were times when we weren't sure what we were "supposed" to do, we always progressed and figured it out.