rob10

You have at least a couple of issues. The INS DEGD advisory in the bottom left says your INS in not fully aligned. Although the JDAM itself seems to be aligning (the ALN QUAL 01 GOOD in the middle of the screen -- it starts at 10 min but only actually takes about 2:30 to get aligned well enough for a good drop) Above that you haven't set the EFUZ so you're going to drop a blob of metal that's not going to explode. The fact that your J-83 is X-ed out at the top can be caused by one or multiple of: MASTER ARM not armed, A-G MODE not selected, TARGET not designated (which in this case it doesn't appear to be), and INS not in IFA or NAV modes.

Not sure WinWing software is the culprit. There really aren't other reports other than this one (little or nothing in the WinWing subforum here which should have a bunch of reports) and others (like myself) are running it with no issues. What someone is looking into is how you have your MFD's positioned and whether having a "taller" setup (MFD's below the main screen rather than beside) is maybe part of the issue. That's purely speculative too at this point. In a quick look at your log I'd try getting rid of Process Lasso. It seems to be causing rather than helping issues currently (DCS is doing a better job of managing cores).

Start by removing your mods (especially the aircraft ones). There are currently a number of mods causing issues including some of the VSN mods.

That's pretty easy to answer: 100%. If things go that badly south Razbam likely isn't going to make a deal with them on any of it and since it's Razbam's IP then ED can't use any of it. All they could do would be try and keep it alive from the outside by feeding it the info it wanted/needed. And as was said elsewhere that's not a forever solution realistically. If they did make a deal for some access to it they'd probably be better off to start from scratch rather than try and learn what was there anyway. So need to hope it gets resolved "positively" in the end.

Interesting, thanks. Since it's one value I assumed it was one viewport. Shows what I know . Glad my comment may have twigged someone on the actual issue then. I wonder if this is a multi-cause issue because there are people reporting updating their Helios fixed it.

In fairness your system (while it may have worked before) is on the bottom end and may finally have tipped over to the point where it just isn't enough to run DCS anymore.

Do you have the option to plug the hotas into a powered hub? There is a chance that the laptop (especially when it's running hard trying to keep DCS going) doesn't have enough power supply to go around and power to that USB is dipping.

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.