rob10

At a minimum uploading your DCS log file is going to at least give people a fighting chance to help you.

Yes, the SU-30 has been reported by a lot of people as causing issues. As Max said I'm guessing you updated since you ran with no problems. And also as Max said, mods can cause unexpected issues. The SU-30 causes carriers to NOT spawn so people spawning on a carrier in a SP mission with it installed currently are blowing up (the F-18 spawns 50 ft in the air and drops to it's immediate death on spawn. Not what you'd expect from a plane mod.

You have a crap load of mods installed. I'd start by cutting and pasting them somewhere else and seeing if things work then add them one by one. I see the VSN 104 mod. Several of the other VSN mods are causing issues currently so I'd start there if you don't want to remove them all.

Currently that's not true. If you have SC and use Stennis you will get ZERO deck crew. Not the new full deck crew or even the older SC deck crew. You have to do the old school line up on your own and hook up the cat with manual binding. That will flip back at some point, but currently ED are working on making zero crew and full new deck crew both work on the Stennis (which they haven't yet).

And for anyone that ends up in this post, the SU-30 is another offender currently.

That's unacceptable how?????? You added extra unsanctioned, untested by ED mods to your build and you're holding ED responsible? No way that ED is going to try and test all (or any, since that would set an expectation they were going to it for all) mods. If it's unacceptable you should be screaming at the developers (who for free mind you) provide you with mod and didn't jump on this immediately yesterday to check and fix them (cause, you know, you paid big money for the mods -- oh wait - see the earlier part of this sentence).

There was no need to cross post this in multiple threads. And as you've probably read in the others, remove your mods they are causing this issue with current patch.

I think Steam downloads go to a separate folder while being downloaded before being installed. It seems to be getting caught in that part of the process so excluding DCS doesn't help because it never gets there. I believe some have had success in disabling AV while doing the update then reenabling it or else figuring out where that Steam download folder is and excluding it. I don't use Steam so that's all the help I can give on that.

Sorry, but ED and 3rd parties can't rewrite their software every time the antivirus companies decide to add something else to their "suspicious" list. That file didn't change and probably hasn't changed in literal years. The antivirus programs are not only looking for "viruses" and "malware" but are also checking for things that look "suspicious" -- so the same as the unmarked van that an Amazon delivery guys pulls up to your house in could cause a security company to be concerned because it looks like what a robbery crew might drive even though it's completely safe in this case. It might be the same van that's pulled in 10 times in the last 6 months, but by coincidence a robbery crew happened to use the same colour/make of van 3 streets over to rob someone so suddenly it's an issue. Not Amazons fault. Do you want them to change from white Ford vans to red Toyota vans every time this happens?

With 16 GB of RAM you need a bigger pagefile than 16 GB. Sure maybe it ran fine before the update, but you were likely on the edge of issues but hadn't quite gone over. New stuff was added that pushed you over the edge and now it's not working. FROM YOUR LOG: 2025-03-17 19:13:52.539 ERROR BACKENDCOMMON (6944): Can't load image './Mods/aircraft/Mi-24P/Cockpit/Scripts/../IndicationTextures/ASP17_flex_sight.tga'. Reason: Not enough memory resources are available to complete this operation. 2025-03-17 19:13:55.540 ERROR EDCORE (14144): More out of memory in ed_malloc for 1229984 bytes.

Thanks. I wondered if it was a "normal" Viggen thing. Flagged it since it was repeating at the end of the log so seemed like it might have been an issue. Glad to have a real answer on it!

More knowledgeable people than me may spot something that I didn't, but no big red flags I saw. I'd start with temporarily removing your Mig-21 and A-4 mods. Mods have been known to cause issues that wouldn't seem like they should be related (i.e. supercarrier wouldn't spawn after one update with a particular plane mod installed). There is also this repeating at the end of the log which I can't recall seeing before: 2025-03-19 23:04:06.916 INFO VIGGEN (19436): Custom cartridge file found! C 2025-03-19 23:04:06.916 INFO VIGGEN (19436): FOLDERID_SavedGames: C

Your anti-virus is deleting files. Look around the forums and you'll find lots of reports/solutions.

Nothing obvious from that description, but I recall someone else having a similar issue recently. You're better to post a small mission example for people to look at.

Post your log file. You'll find your most recent one in your DCS Saved games/logs folder. If you have file extensions hidden it will be dcs, but likely it will be dcs.log For the record, DCS has only had multi-thread option for some time now (single thread was depreciated), so that's not going to factor into the issue.

There is a little box in the top right corner of this thread with "search" in it. Type "authorization" and hit enter. There have been probably 20 new threads started about this (or what is virtually the same) issue in the last 2 weeks. Short answer is It's your antivirus causing issues.

Thanks @BIGNEWY, never thought to try resaving, but that seemed to update things and it worked fine after I did that.

Mission was built before chocks were available (it mentions that fact) but since they are now available they are applied. And you CAN NOT call the ground crew (tried bound button and default keybind, menu won't come up) to remove them (and no keybind to remove them) so you can't do the taxi part of the mission.

Your anti-virus is blocking the F-14 files. Very common issue currently. Check the forums and there are all kinds of post explaining how to fix.

They are telling you that the unit is beyond limits side to side (6 degrees rather than max 5 degrees) but within limits front to back (1 degree vs max 5 degrees). So you need to place it on leveller ground for it to be able to be functional.

No apparent reason for it, but NordVPN seems to be coming up as a problem with number of people in the last week or so. Likely something that would need to be tweaked or fixed on their end.

It's your anti-virus. There are lots of threads about this issue and how to fix it if you search around even a little bit.

From your other post, you're flying the F-18 as a RED COALITION member. Unless you have Unrestricted SATNAV selected you're going to have a degraded GPS so no wonder it's not hitting accurately. This is a prime example of why we ask for a track file when trying to help people. It's usually the little details that they don't think to mention because it doesn't seem important to them that are the root of the problem.

See this reply from further up the page: And add a track if you want to get actual answers about your specific case.

Do you have them plugged into a USB hub? Is it powered? My 1st thought would be not enough power. Try swapping the bezel that not showing for one of the ones that is and see if it's working. That should rule out hardware (cable or physical device).