AH-64D - Exclamation mark on Collective binding (Mi-24P as well)

[DubDub]

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?

 

[speed-of-heat]

try going over all (even the blank ones) and clearing the bindings for each "!" and then try re-assigning just one, you can try adding more later, i have had some strange behaviours with the defaults, but i am never quite sure if is just me (for me it was on the Tomcat) ... forgot the close DCS step below from @Esac_mirmidon, but he is correct!

 

Edited November 19, 2024 by speed-of-heat

[Esac_mirmidon]

Just do this

Clear all boxes with red alerts

Ok and close DCS

Restart DCS

Bind again those boxes 

[sirrah]

32 minutes ago, Esac_mirmidon said:

Just do this

Clear all boxes with red alerts

Ok and close DCS

Restart DCS

Bind again those boxes 

Check the UI-layer controls for double bindings
 

[Jef Costello]

Hello DubDub!

I had this exact problem! I solved it by renaming it like this

                    ["key"] = "JOY_RZ",
                },
            },
            ["name"] = "Collective",

[scommander2]

Another reference with the similar issue:

 

[DubDub]

7 hours ago, Esac_mirmidon said:

Just do this

Clear all boxes with red alerts

Ok and close DCS

Restart DCS

Bind again those boxes 

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!

[Esac_mirmidon]

Glad to help guys 

[ShuRugal]

the red X indicates that DCS sees a binding assigned for a button which does not exist.

When i see it, it's usually because i had a modifier defined, and used in a binding, referencing a device which is not plugged in.  Did you recently replace an input device?