rob10

TL/DR translation of OP's 2nd post: SA page worked fine in default, is currently broken in the F-18 mod he's using.

Ahh, yes, I'm using a single viewport with the MFD displays off to the right of my main screen as part of it displaying on the WW MFD's. My apologies, I missed that detail if you're using multiple so my use case isn't the same.

Not sure that's completely the issue. Mine is set for 5376 x 2163 and I'm having no issues.

This is a MOD issue rather than an ED issue, so logs aren't really required. The mod makers need to update things, not ED. Not really unusual that the mod makers need to update things due to changes in DCS core by ED.

You need to remove the mod folder. You can just cut and paste it out if you want, but it needs to be out of all the DCS folders. My guess is a bunch of these mods will be updated over the weekend and you can put them back but currently they cause issues if installed (even if not used in the mission you're running).

I'm far from expert on that, but are you running Win 10 or Win 11? With 11 reports are you're better off in most cases removing Process Lasso and letting DCS handle it. Seems like it's doing a good job of it currently.

What aircraft are you flying? For some, like the F-18, you CAN'T use pitch trim unless gear are down (you can trim roll).

OK, that's just cruel of them to include that in the changelog when it doesn't fundamentally fix the fact that the missile can't fire. They should wait until it will fire before they bother to include it.

Double check that you properly excluded the DCS folders mentioned. Then RESTART your computer and run a DCS REPAIR.

Sorry, can't help you with a solution, but I have 3 WW MFD's and haven't had an issue so keep digging because there should be a solution. I have seen another post experiencing the same as you, not sure what the commonality is. As a random thought: go into your SimAppPro wwexport.lua (\SimAppPro\resources\app.asar.unpacked\Events\wwt\wwtExport.lua) and at line 19 change the winwing interval value from 0.03 to 0.3. Not sure it will help your scenario but that reduces how often SimAppPro polls DCS so it might. That's assuming you weren't having issues with USB export without SimAppPro running as well in which case that won't likely help.

SU-30 is also another common offending mod currently. And at least some of the FSN mods.

Please post a track. You can save a track from the debrief window when you close the mission. As a complete guess since we have no details from your post, double check that you have turned your datalink on (UFC, press D/L 2x (1st time only takes you to carrier landing datalink), press ON/OFF).

If you leave a window OPEN (not minimized) on your desktop ALT-TAB will work without disabling those. So you either need to do that or as Rudel_chw suggested or you won't be able to ALT-TAB in my experience.

You should make your own thread to report this (it will be missed in here) and post a track of this happening in it.

If Razbam and ED come to an agreement on their disagreement then maybe. If not, best case the F-15 is going to stay same as it is.

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.