DubDub

I had done this many times and even done the same thing by trying to edit the files themselves. The key was the restart immediately after just as @speed-of-heat also suggested. Thanks guys!

I've had the AH-64D since release. Took a couple years off for some coding projects and came back to an unusable Apache due to this binding conflict. After testing my joystick and throttle config files in the Config\Inputs\AH-64D_BLK_II_PLT folder, I removed them from the folder to hopefully force reconstruction of the files and restarted the program. - The files were not reconstructed but the conflict remained although the configuration came from an unknown source. I've completely erased the settings within the program countless times and they only come right back. The settings in the photo are not mine but some settings DCS began bringing in after I blew away all traces of my own bindings config files. I can't even find this combination in the default folder or the default.lau scripts in the primary execution folder tree. I've hovered over all of the exclamation marks but they simply show a label containing the name of the box the exclamation is on. (i.e. a "Collective" label appears for the red mark on collective, a "JOY_Z" label appears on the red mark for JOY_Z, etc) I began searching for and modifying all joystick config sources I could locate (After backing them up of course). Config\Inputs\Default, \InputUserProfiles, I even went through the input config files on the main program folders which were set to Read-Only, reset them to editable and modified them to no effect. I had just bought the OH-58D which worked fine so I began comparing its input config as well as all of my other Helos and discovered that most call collective "Flight Control Collective" but the AH-64D just called it "Collective". I also noticed at that time that the Mi-24P bindings where damaged in exactly the same way as the AH-64D but the Mi-24P did call its collective "Flight Control Collective" while the AH-64D binding was only called "Collective". I decided to try writing a brand new and distinctively named Throttle file for the AH-64D and the Mi-24P to look for differences in how it might name the settings within the file and found to my surprise that while the Mi-24P did call its collective "Flight Control Collective" it wrote the setting to the bindings file as "Throttle (Collective)". Naturally I tried renaming the entry in the bindings file from "Throttle (Collective)" to "Flight Control Collective" but it made no difference. I have completely deleted the AH-64D and reinstalled it again. no difference and I've restarted DCS from scratch after every test. I'm stumped. It feels like the program is expecting a name I don't and can't know in those files. Any ideas besides the Nuke everything surrender?

The Job of marketing is to play with messaging so as to make any corporate decision palatable and profitable DESPITE REALITY. The problem is that for most marketing people, it can be very hard to keep track of all the "SPIN" the corporate chiefs have forced them to spew. This creates conflicts in the spin. 1 - "the most authentic and realistic simulation of military aircraft, tanks, ground vehicles and ships possible." - - - If you have to pay corporate resources to correct and update product you already sold then the product that was previously sold was unfinished product and couldn't have been accurate and authentic. Why would you have to change a COMPLETE, ACCURATE & AUTHENTIC product? What does this say about all of your claims of complete, accurate and authentic other products? 2 -In the past, you bought a sim and it came with ALL of the finished aircraft. In DCS we're forced to pay-per-plane. I had a tough time with this in the beginning but warmed up to it because of the quality of what was being produced for the money I paid. The question of pay-to-update is a serious one. What are the boundaries for Pay-for-update? Where does it end? If your starting Pay-for-update then the natural progression is the selling of empty planes with bad graphics. Then users pay for missile systems, cockpit systems, improved graphic, etc all in the effort to achieve "the most authentic and realistic simulation of military aircraft, tanks, ground vehicles and ships possible." You're charging to update a previously incomplete product. What does this suggest about the kinds of decisions DCS is willing to make for increased profits. You talk about the monies that need to be paid to create these updates. Those monies were paid. THAT is the ethical contract you made with your community when you took their money for digital aircraft. That they were paying for complete, accurate and authentic aircraft. Now your asking them to pay for exactly the same thing, a complete, accurate and authentic aircraft for the one they paid for and never got the last time. DCS has spent years building a community of dedicated players and its those dedicated players who have kept it alive. The software itself is actually very boring. There's a very limited collection of maps and play with the automated mission generators gets stale quickly. In fact, for the first two years of ownership I had been avoiding online play and couldn't figure out where people where finding all of the missions and features they were showing on the internet. Its the player community who make the mission maps, host the multiplayer servers and run the squadrons that make the game great and interesting and form the bonds that keeps people coming back. They don't get paid and will quickly tire of your bills. Be very careful how you abuse that which you have worked so hard to build. It won't go unnoticed despite the spin and every player you loose is another brick from your foundation. You don't have to loose them all for it to crumble.

I'm assuming I'm missing something simple or there'd be complaints about this mission everywhere. - I set my ADF to 430 - Flew to Batumi and pick up the passenger - Orbited the port as directed until I was told to they had enough material - Set my FM radio to 40.00 Mhz as directed - Flew over the fleet until told to return to the Argo - Landed on the rear of the Argo. (The ship with the big "46" on the front) And there I sat on the landing pad of the Argo with the engines at idle for a half hour with no next step and no mission notification. What am I missing? Thanks