rob10

Thanks for coming back with your solution!

I'm sure I dropped them in training mission a bit ago, but now I can't get bombs to come off the plane no matter what I do. Rockets do release (same button) so it's not a binding issue but I've tried different binding too. Changeover set to ON, bombs selected, bomb door open (warning light lit), bombs fused, reticle on. Track attached. Mosquito on the Caucasus map. SOLVED: missed the extra binding "TRIGGER BUTTON (release bomb/guncam on)" that drops bombs. It doesn't show up when filtering for WEAPONS and I guess I missed it when I went through the full list several times.

Since the official C-130 module was only announced 2.5 years ago and considering they were actively updating the mod version almost up to that point, I'd say you're wrong on that. I'm just as happy if they spend their time coding it and not wasting time creating videos (which to do right don't happen in an hour or likely even 3 hours). They have shown some pic's, and as Max said, it's been included in ED videos. Too bad you don't believe it coming, but I'm really looking forward to it.

And what makes you think that? They've indicated either end of last year or sometime in Jan that it is planned to be out this year. My money is before summer, but that's purely speculation on my part.

In this particular case it's probably not your antivirus. You likely need to reauthorize your modules with Steam. It seems to happen occasionally with people that have transferred from Steam to standalone.

That usually indicates (as the description suggests) that you now have two (or more) identically named commands in your dif.lua's . It's something that has happened in past for no reason, but since you're using Quaggles I'd start looking there and see if it has something messed up in your settings or if something has changed in the controls lua's that means it's now duplicating. If you go into the the lua's you should be able to delete the duplicates and get things back to normal.

In your case, start by increasing your min and max pagefile to 32GB. Currently you're 32 GB RAM and 5954 MB pagefile. You're almost guaranteed to be running out of memory with that combo: System RAM: 32683 MB, Pagefile: 5954 MB

Couple of things (that apply to all 3 of your posts): Please use a more descriptive title. "Bug report" is going to make it really difficult to find the correct one again. Please give more detail. I'm guessing which aircraft in most cases and in the 2nd one I think you mean the new "save state" functionality, but that's not really clear. Please add a track file for where you're having issues. You can save it when you get to the mission debrief screen. Keep it as short as possible and ED does prefer it to be on Caucusus map if possible.

Just in case you weren't aware, you can put your TDC cursor over other F-18 or F-16 (and likely at least some others but not sure which ones) and press the MEMBR button on the bottom left to add them to your group. 1st one will show up as A, 2nd as B etc.

Well, you said it started "some updates ago". This thread is related to an issue that's only been a problem since the last update. Either way, without at a minimum a log file, all you're going to get are blind guesses what your issue is.

This thread is specific to an issue with exported MFD's. Unless that's specifically your problem (which almost for sure would be fixed by not running DCS as admin) then please create your own thread and more importantly include your dcs.log (may be just dcs if you have extension names turned off). From your description it's impossible to know what's going on or provide you any help.

Remove your mods (especially plane mods). Very common issue after the last patch and has nothing to the do with the campaign. If you search around the forum you'll find which ones are the problem, but some of the SU-xx and at least one VSN are causing issues.

The dcs.exe in both folders should be identical at this point. ED has indicated they plan to clean things up and get rid of one of them at some point but have left it currently just so people can run from either shortcut without issue.

Probably related to this:

Interesting. I DO NOT have it running as admin (and no problems). Will be interesting to see other responses.

You're much more likely to get meaningful answers if you post your DCS log file. Do you have ANY mods installed? There are a number of them causing issues after the last update.

I'm running a newly built system as of middle of Feburary, with fresh install of everything except DCS (copied), so for those without problems it's not due to old drivers not having an issue. Drivers for GPU would be new and I downloaded DisplayLink fresh.

I get where you're coming from, but unless that specific ratio or size is the problem it shouldn't be related to that. Mine with WW screens is 5376 x 2163 (so bigger both ways) and I'm not seeing any issues. Are you on Win 10 or 11? I'm on 11. Maybe there's a difference there

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.