malibu43

Anyone know if the campaign fixes have been incorporated yet into the beta or stable release yet? It is a hassle to remember to use OVGME to disable these mods before each patch *just in case* ED has decided to finally update them and not mentioned it in the patch notes. Some of these are game-breaking issues (I know for sure the A-10A campaign is unplayable without these mods) and ED has had plenty of time to get them fixed.

@ED - I would like to know the answer to this before purchasing. If I have to go back into existing stock hornet missions or any campaigns/missions I downloaded or purchased and manually add this in, I will probably not buy. Likewise I want to make sure future "official" missions or campaigns that I buy will make use of it without me having to modify everything. It would eventually be a mess to keep track of...

Nineline - Maybe this is info you cant share, but will fidelity be similar to FC3? Or even "lighter"?

We had FC3 and all the other modules when they announced MAC. So why would those things being in existence change whether or not MAC happens? MAC builds on FC3 by including content from other modules... I think it's still happening. Just no updates in a while...

It would be nice to add the same afterburner detent keypress option that we have in the FA-18 to the FC3 aircraft as well (at least the ones with after burners). This is a very helpful feature for throttles that don't have built in detents.

Any updates on MAC? I was looking forward to some FC3 level versions of modules I never bought due to time to learn them.

Thanks for the responses. @Griffin - I read that early on, but didn't see any "power management" options, so I couldn't get it to work. I was over Win10 last night and decided I would go back to Win8. I knew there was an option under recovery to do so, and it was supposed to stay active for 30 days. So I went to switch back to 8.1 and WINDOWS TELLS ME I CAN'T BECAUSE IT REMOVED THE FILES NEEDED TO SO!!!! WTF!!!! AAAHHHHGGGGGG!!! I guess when I allowed Win10 to apply updates (thinking they may be needed to get my software to work), it decided that meant I liked it and could delete the recovery files. I was seriously bummed. I could not get CH hardware or software to work in Win10. Decided I would bite the bullet and do a factory reset back to Win8.1. A lengthy process, but at least I knew it would work. I try that option and it asks for my original Windows installation disk, which my laptop didn't come with. So that's not an option. I was at the point where I figured I may have to quit flight simming for while. Then I started playing around with vJoy and Joystick Gremmlin. After some fumbling around I sort of got it to work and could see my joysticks in games. But, when I was in there, I also noticed that my Stick, Throttle, and Pedals were showing up as input choices by name (instead of vJoy devices). So I deleted vJoy and Joystick Gremmlin and my input devices were still there! At this point I went into Device Manager and found the devices as well as the power management options!!! Went through the steps recommended by Eclipse 4349, and then tried using CH Control Manager. Everything worked! I can open CH Control Manager at any time, activate/deactivate profiles, unplug the hardware then plug it back it in, and everything seems to work! What I think finally fixed it was that I completely uninstalled CH Control Manager, then also uninstalled the hardware and deleted the drivers from Device Manager. Then reattached the hardware, let windows recognize it, then reinstalled the CH Software. I think somewhere in there there was another update and restart from Win10. It wasn't until some point in that sequence that the power management option showed up, and it took me a while to go back in and see that it was there. TLDR: Win10 migration is dangerous, but I fixed my issues by completely uninstalling hardware and drivers and doing a fresh install, and then following the link from Griffin.

I knew a while back there were issues with CH Control Manager and Windows 10, but I recently did a quick google search and thought I saw that they were fixed. So I went ahead and upgraded from Win8.1 to Win10. However, in my initial test, I was having the issue with CH Control Manager where I could not select Mapped or Direct Mode, and even without using CH Control Manager, games were not detecting my hardware. I did some more thorough googling this time and realized the issues seem to have come and gone over the last couple of years, but I couldn't tell what the "current" status is... I found that my fresh Win10 install had a backlog of updates, so those are downloading and installing now. Hopefully that fixes the issue. However, I wanted to ask here and find out if CH performance in Win10 has reached a stable point (if it's working at all) or if it's still a crap shoot, in which case I guess I have no choice but to roll back to Win8.1 while it's still allowed (30 days). Input appreciated.

Would it be possible to get a link to all of MadDog-IC's campaign fixes stickied in this forum? It is essential that they be downloaded and used for FC3. Otherwise some campaigns are currently unplayable.

Go to the DCS home page, hover over "Downloads" then select user files. Then, under "Uploaded By" enter "MadDog-IC". He has made corrections to the FC3 campaigns for v2.5 and uploaded them there. It is frustrating that some of the campaigns are broken and unplayable as included with the game. It would be nice if ED incorporated these fixes at some point so we don't have to add them ourselves, but for the time being MadDog has us covered! :thumbup:

When I run DCS its starts to install a new updater, but then crashes. Can someone help me figure out what's going on? 00000.000 === Log opened UTC 2018-06-29 13:07:43 00000.006 INFO : DCS_Updater/2.9.2.69 (Windows NT 6.3.9600; Win64; en-US) 00000.006 INFO : cmdline: "C:\Users\GREGG_~1\AppData\Local\Temp\DCS\DCS_updater.exe" --apply selfupdate "D:\Games\Eagle Dynamics\DCS World\bin\DCS_updater.exe" 00000.009 STATUS: Initializing... 00001.083 INFO : basedir: D:\Games\Eagle Dynamics\DCS World\ 00001.083 INFO : DCS/2.5.2.18736.400 (x86_64; EN; WORLD,FC3,FA-18C) 00001.083 INFO : branch: openbeta 00001.083 INFO : Copying C:\Users\GREGG_~1\AppData\Local\Temp\DCS\DCS_updater.exe to D:\Games\Eagle Dynamics\DCS World\bin\DCS_updater.exe 00025.872 STATUS: Got CANCEL when asked to retry: Can't copy C:\Users\GREGG_~1\AppData\Local\Temp\DCS\DCS_updater.exe to D:\Games\Eagle Dynamics\DCS World\bin\DCS_updater.exe: (32) The process cannot access the file because it is being used by another process. 00025.945 ERROR: Can't copy C:\Users\GREGG_~1\AppData\Local\Temp\DCS\DCS_updater.exe to D:\Games\Eagle Dynamics\DCS World\bin\DCS_updater.exe: (32) The process cannot access the file because it is being used by another process. 00026.265 ERROR: Can't copy C:\Users\GREGG_~1\AppData\Local\Temp\DCS\DCS_updater.exe to D:\Games\Eagle Dynamics\DCS World\bin\DCS_updater.exe: (32) The process cannot access the file because it is being used by another process. 00029.353 === Log closed.

I can confirm the VFR overhead training mission stops instructing on the down wind. Confusing...

Here is my profile, set to mimic the F/A-18 HOTAS as closely as I could. You could easily turn the External Lights toggle into a shift, and add more commands. DCS F-18 CH Maps.zip

LOL. If this is really the case, then I guess I'll probably take that off my HOTAS layout! I assumed it was something for setting Mark Points (or whatever they're called in the F-18 ).

Here's my stab at a CH HOTAS layout. No SHIFT commands as I still have some open buttons, but can always change that later after once I learn how things are working.