Reflected

good news, ED fixed it internally, it's coming in the next patch!

Same issue here, Quest 2

You need to push the actual push to talk mic button on the throttle, the comms menu only works on the ground.

The most underrated map. My favorite!

After engine start. Usually you do it before shutdown “for next time” but that’s not possible in dcs

You can go above 120 initially, as long as you keep the rpm below 1500

Yes, Nellis AFB where Res Flags take place in real life too

Just out of curiosity I flew Mission 8 today. The coldest one in the middle of January. 5 minutes from mission start (not engine start) my temps were good for takeoff - I could have taxied even earlier. So just keep that oil dilution button depressed for a minute, and as pressure drops, keep increasing the boost.

I'm opening a beer now to celebrate: I finished the last of the kneeboard maps for my upcoming Red Flag 81-2 campaign. There are a total of 97 of these in the campaign. 97 times I had to draw the lines and measure the distance remaining as well as the minutes passed. These are modeled exactly after originals, and these will be your best friend as you navigate across the ridgelines to meet your time on target. One of the most satisfying things I've done in a flight sim, dropping my bombs within a few seconds of the briefed time.

Your way of thinking is not wrong at all but you need to realize it's not the campaign that broke, but Ugra, the map developer implemented some unannounced and drastic changes to their maps, and THAT in turn broke every campaign that uses their map. We, as campaign makers can only do one thing: try and find workarounds, change the missions hoping to find a way to make them work. This takes time and sometimes it's not even possible and we require the map developer to fix their bugs. What would help a lot is if Ugra had warned us about these changes before the public release, so we could have updated our missions by the time it was released. I know Baltic and I'm sure it won't take 'months'. All the campaign makers prioritize fixing their campaigns and make them bug free, but often we cannot do this in 1-2 days after such a curveball. But again, I agree, such bugs shouldn't be left in game for a month but I'm also pretty sure they won't be. After all, for you as a customer it doesn't really matter WHY the product is broken, only that is IS, and believe me it's bothering us just as much as it bothers you.

For me oil dilution seems to be working ,you just have to keep the button depressed for long enough to take effect. I never had any problems warming up the engine and I've played these missions at least 50 times each. But I'll see if I can extend the timings without having to redo all briefing and kneeboard visuals. In none of the missions do you have only 2 minutes, something is definitely wrong there. Can you give me an exact mission number please? In all missions you have approximately 10 minutes to start up and take off. That should be plenty enough. If not, I recommend practicing startups and warmups in simple cold start missions. EDIT: I just checked, it's not possible to change the mission timings. Either I'd need to redo all visuals because of it, and/or it would open up more breaking possibilities if the player warms up normally. What you can help me with is to campaign with ED for a 'warmed up engine' option. I've already asked them but that's just me.

No, you fired a F1, and later you fired a F3. Then when Paco fired a F1, you fired a F2. And a few more. It's very simple. If Paco fires a F3, you fire a F3. If Paco fires a F1, you do too. That's how the intercept goes. There are 1000 ways people can ignore the very specific instructions given in the briefing, I can't possibly set up a trigger for each scenario. I need the player to play along, and be able to assume that he's following at least the gist of the instructions, especially when the mission is already so complex.

Wait, I watched your track. Of course it doesn't work. You've been completely ignoring Paco's instructions and commands. When he fires a Fox 3 you fire a Fox 1 for starters. Then when he fires a Fox 1, you don't. And in between you just keep spamming the bandit with all kinds of missile shots. So I guess the 'timer' in the game doesn't even start because the mission has no clue what you're doing

https://forum.dcs.world/topic/361637-mission-8/?do=findComment&comment=5546636 but it’s like 30 seconds. If hits don’t register for longer than that, make sure you have no mods installed and run a slow repair

Thank you, I appreciate it! Glad you had fun!

Arctic Thunder teaser. You know me, the campaign will be full of unexpected challenges

You really need to milk it...

Also HOBOS - no TV picture

It's a training and they want you to practice dogfighting. So for a short time after the merge the kill's not counted.

From the briefing: "We’ll fly over the target at 11K, once you tell me you have the target acquired, I’ll break up and left to 15K, 400 kts, 3 miles abeam. You follow 10-15 seconds later, when I call Abeam. Good?" and later: "Remember, stay level at 15K, 400 kts, in a roughly 3 mile arc." And the whiteboard: null And in case the player missed all of that, I put the message on screen that's also visible on the screenshot I took from your track.

This campaign is not about destroying the target, but about learning to do it realistically, the Navy way. I'll leave this screenshot here from your track, it has all the clues you'll need null

Please send a screenshot of your message history after you got stuck. my guess would be you didn’t fly the pattern according to the brief. Or maybe you didn’t come around for a 2nd pass? How many passes are briefed? What anout the pullout? Check the briefing again please.

No there is no such script. You need to ask ED, I already have. For me oil dilution is still working though

The ability to launch or the lack thereof is core supercarrier logic, I have no influence in the mission editor. Remove all unofficial mods if you have any and run a repair. @[ED]Ben any updates please? Such a mission breaker bug shouldn't be left unfixed for 4 months now. Thanks!