rob10

Was going to suggest that would be the likely error. If you use any of the lights in VPC it causes a crash in the background. Fortunately the fix is very easy. In that folder duplicate the fake_omni_lights2.fx and fake_spot_lights2.fx and rename the copy to take out the 2 and it will work fine. I think something changed in base DCS over time and maybe the mod hasn't been updated. Note that because that's in core files, the copied files will likely get deleted at some point (esp. if you do a repair).

Ya, it's pretty relaxed in terms of the position you need to be in and will move you over if needed. I've rarely had an issue with not ending up in the right place and almost always it would be user error (inattention) and I can tell before I even try and get them to hook me.

Since the 3.8.10 files there are only E and F preset available and IIRC you get F if you set to ULTRA and E if you set to anything else. The tweak hacks earlier in the thread are no longer required (or at least not really useful anymore) as I understand it.

Gotta say, not sure that should be an issue. Mine happen to be alternating screen/ddi buttons and I've never had an issue. Setup videos are here:

In DCS you do a 180 (with NWS on HI you can turn in a verrrrryyyyy tight radius) and go back down the deck and retry. You can safely run over the deck crew without causing issues.

Well I'm glad you asked question because while I knew it was supposed to be gradients of green still, I didn't realize what was actually added and what it was for!

I agree with the theory of that, but if it let you manually unchock that's likely going to break more than it solves. Yes, if you're just flying a mission with your own squadron it wouldn't matter because you could all agree to do that and work around the deck crew. But how would you reset things on an open server? The only real solution is for ED to keep working on it (which they are) and make it work properly.

Checking that displays are set to extended as Mustang Sally suggested is definitely 1st thing to check. It looks very much like those screens are mirroring your main screen.

Glad you got it fixed. Ya, it's a weird one. I know people had problems turning it off, but you're the first I've seen having trouble turning it on.

But have you tried SAVING it again with it enabled in both? If it was initially saved with it turned off in client that saved it, it might not matter that it's on in client now.

As a starting point, maybe some details on your hardware and a log from one of the crashes, then maybe someone could give you some hints. But just because your AV or hardware has been working fine until this point doesn't guarantee something hasn't gone wrong with it.

Could be a reverse issue of new Deck Crew showing up even when disabled in mission. Try making sure you have the new deck crew ENABLED on client machine AND in the mission then resaving it. Currently if you have it turned on in client when saving a mission it ignores the setting disabling in mission.

Happens often enough to virtually guarantee it's an anti-virus issue (McAfee, Avira, ESET being amongst the most common offenders). Uninstall/reinstall is also virtually never required with DCS. There is a repair option which will solve almost any problem that uninstall would and will be much faster than downloading the whole thing again. In this case uninstall isn't going to help you anyway because the anti-virus will simply quarantine the same file again (unless it happens to have updated to whitelist the file in the meantime). You will, however, need to do a repair to get the file back once you get your antivirus sorted.

It is definitely a weird quirk, and would be nice if it ever gets fixed. But at least we have a message history now, so I can live with the quirk for a bit longer

I only pointed out paying attention to the brief because in this campaign (more than many) it's easy to miss things that will cause you challenges in the mission if you're not reading it carefully. Nothing wrong with that fact, and personally I like it, but seems to be tripping up a number of people trying to fly Arctic Thunder.

Are you binding them in the correct column in DCS? And the correct MFD buttons in DCS? There should be a separate column for each physical MFD and in the bindings there are separate binding for right, left and centre MFD OSB buttons.

Assuming you can open the livery, add the following at the very end of the .lua for it and resave. Note - 0.0 = turned on, 1.0 = turned off -- ADD AT VERY END OF LIVERY .LUA -- custom_args = { [27] = 0.0, -- top of tail [1000] = 0.0, -- flaps [1001] = 0.0, -- nose high in front of cockpit [1002] = 1.0, [1003] = 1.0, [1004] = 1.0, [1005] = 1.0, }

Do you have any SPACES in the name of the sound files? That can cause issues. NVM, I see from the upper part it has the name and it doesn't. I might try and take out the dashes too, but I don't think that matters.

If you read the briefing (or check your kneeboard) it will tell you that for this mission "Base altitude for today is set to 10,000 feet". So base + 5 would be 15,000 ft not 20,000. Worth paying attention to the details in the briefings because base altitude changes throughout the missions.

That makes sense. I've really noticed it in Kola (or Marianas) with wooded areas with roads running through them that it's not nearly as easy to find and hit targets as on less foliage maps. Thanks for coming back with your findings!

Not sure if you're aware of this, but if you go into the "messages history" when you return to the game it will still be paused. You need to hit ESC a 2nd time and then resume again and it will start again. Weird little quirk since they added the messages history ability way back when.

How would ED fix this short of submitting every patch to ALL AV providers prior to releasing it? The AV's are (in part) looking for changes in certain file types to "predict" that it might be something malign, so there is really nothing that ED can do. And interestingly there are 3 or 4 AV programs that consistently cause issues so it's not even all AV's. Maybe those ones need to tweak their programs to not throw false positives.

Already reported here. Has been happening before last update. Likely challenging to fix since not all users are experiencing it and track replays aren't showing it. Any further details to recreate it would be better in this existing thread.

I was lucky that I happened to offset to the right so it didn't take me, but others have gotten caught with it damaging them . That's probably a random luck of DCS thing.

Agree with L4key's points. All you need to do to advance to the next mission is click SKIP in the campaign mission selection window. Since that's available I don't think it's on the campaign creator to add it as an F10 menu option.