rob10

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.

If you post a track someone will likely be able to tell you what you're missing on your end (or at least confirm it is an issue your end rather than an ED issue).

Personally, at this point, I'm turning the new deck crew off for MP. It still needs some work and unfortunately with it on you have no options to get off the boat if it doesn't work. You can't even do a deck run since you can't remove chocks.

This! I find the F-18 is slightly high for me so I look at the top of the dash and recenter there and when I look ahead at my natural position it's just about right. If you want to see more instruments, just look a little higher when you recenter and you see more of the instruments when your head is in your normal level position.

I'd start by removing your mods. They are always the 1st thing to rule out because they can have unexpected consequences (especially after DCS patches).

Not specifically ME related advice, but try deleting your FXO and METASHADER2 folders in your SAVED GAMES file. Reinstall rarely does more than full repair with delete extra files, but you could try. Also, if you have any MODS installed (check your SAVED GAMES folder, repair should have removed any in the game folder) try it without them.

If you have a target designated it will always drop in AUTO. You need to undesignate your target for CCIP release to be available.

Posting a track of the problem is going to get a lot more traction than posting about it in multiple threads.

And post a track of your LGB issue, because I used them yesterday with no issues whatsoever.

100% agree with your request, but IIRC, this is a DCS thing that Orbx likely has no control over. It automatically repopulates the frequencies to random frequencies, seemingly to drive users that create kneeboards or other info with the frequencies on them crazy, whenever things are changed on the map. Happens with other maps beyond Kola.

Both in game and the pdf version (thanks for those by the way) have the GBU-12's listed as being on STN 5 (which they can't be anyway). They are flipped with FUEL on STN 3. Also, the JTAC at Starfield is referred to ODIN 5 in the briefing and kneeboard, but is CAVEMAN in the mission itself.

You need to turn the physical switches for the "tapes" ON in the cockpit. It's easy to overlook, but it actually tells you to do this at fence-in in the briefing. The switches are located below the FUEL INDICATIONS. The comm's are a hint as to what you haven't done (turning on the tapes) rather than a command for something you should be doing. I had read it in the briefing and completely forgot to do it until I hit that comm's, then I had to look up where the switches were.

Likely is related, because if your Phantom is no longer authorized your anti-virus is probably blocking a file from it which is also breaking other related things.

Removing all your mods is a good starting point to troubleshoot. As the SU-30 causing the carrier not to appear issue shows, there can be weird interactions that cause problems. Once you've got it working you can start adding mods back until you find the one that's causing you issues. For mission you've created, did you set any of the aircraft as PLAYER or CLIENT? For downloaded, do you own and have installed any of the player flyable aircraft in it? Otherwise you won't have an aircraft to climb into.