Red Exclamation Error Badge on Loaded Inputs

[Dogman]

Hi Guys

For some time now I have noticed that when loading profiles onto different modules from saved input config files a red exclamation badge that I believe means that multiple inputs have been assigned to that command shows up on random commands. The screen shot attached shows what the issue looks like with the Weapons Fire command that after clearing a duplicate input command in Throttle Category only the one Joystick is input is now being applied but the badge persisting and the bind does not work. There is no rhyme or reason as to what commands will be affected in the different modules it is random. 

I would greatly appreciate some support solving this very annoying problem. I have done some research on the issue but can't find any satisfactory resolution apart from reloading the module and assigning each command individually which is a prospect that I can hardly imagine considering the number of modules that I have. 

Very much look forward to hearing from anyone who may have had this problem and has determined root cause and solution.

Thanks in advance...

[Flappie]

If you hover the mouse cursor over the red badge, you should get an indication.

Edited March 15, 2024 by Flappie

[bloomster]

I have the same issue with a brand new install of the module SA342. no idea how to fix it, I have no modifier on it as you can see, but it wont recognise the trim forward. Only happens with the SA342.

[bloomster]

Even cleared every assignment and reset control for the SA342 and the error is still there.

Error says Trim Hat Nose Down. Which is kind of what it is meant to be so odd.

[Flappie]

When it comes to the Gazelle, this is expected since there has been a recent change. Please read this (Input System Overhaul):

https://forum.dcs.world/topic/344001-sa-342-gazelle-february-2024-update/

[skypickle]

@bloomsterim having the same problem w trim forward. did you ever resolve the issue?

[sthompson]

On 3/15/2024 at 8:45 AM, Flappie said:

If you hover the mouse cursor over the red badge, you should get an indication.

 

A bunch of these red badges showed up in various modules recently after I installed 2.9.6 and bought the FC4 upgrade. While a few show the conflict when I hover, most do not. Is there any way to determine what is causing the issue? Some of the red badges appear in places where I apparently have no assignment at all.

[Flappie]

I helped a friend with the same issue a few days ago. Here's what solved the issue:

1. Remove all controls flagged with the red conflict indication icon.
2. Exit DCS.
3. Start DCS.
4. Re-bind controls.

[sthompson]

20 hours ago, Flappie said:

I helped a friend with the same issue a few days ago. Here's what solved the issue:

1. Remove all controls flagged with the red conflict indication icon.
2. Exit DCS.
3. Start DCS.
4. Re-bind controls.

Seriously? I have a lot of these conflicts, and I didn't change any key bindings. They just showed up. Fixing them all via that method is going to be very time consuming.

[Slippa]

This is how I fixed it too. Took me a while to do the lot. Props and jets I had to do throttles. Helis I had to redo the collectives.

Not a lot of fun. MP servers seem badly lagging, lots of complaints, hope for a fix soon but could’ve done without all the re-binding.

[speed-of-heat]

4 hours ago, sthompson said:

Seriously? I have a lot of these conflicts, and I didn't change any key bindings. They just showed up. Fixing them all via that method is going to be very time consuming.

I'm having a similar problem, but it also impacts Axis as well as buttons on multiple aircraft, it "seems"  that the "default" is "sometimes" selected for an axis/button , it doesn't seem to be consistent... across all aircraft for example the tomcat "both" axis is defaulted in addition to the left right axis which has been set in the particular profile, a number of default buttons seem to be set in the UI layer, across multiple devices for no apparent reason ... and so forth...

[Captain Orso]

Not sure if this thread's issue is the same issue that I had, but here is my experience.

I installed a new controller; a TEDAC for the Apache. There are two buttons on the grips which the real AH-64D doesn't use, but the controller has them wired up, so they are free for anything I want, so I assigned them as Modifier-Switches(momentary). 

So I'm setting up the AH-64D CP/G binds and I noticed a whole slew of the red exclamation marks on binds I had done nothing with.

Long story short, for the AH-64D Pilot binds I had a number of Modifier-Switches(momentary) for joystick and throttle which were not in the TEDAC controller. I also and the new Modifier-Switches(momentary) in the TEDAC controller which were ofc not in the AH-64D Pilot binds, and I noted that those bind slots in the AH-64D Pilot binds using Modifier-Switches(momentary) which were not configured for the AH-64D CP/G were the ones marked with the red exclamation marks.

So I harmonized 'c:\Users\me\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_CPG\modifiers.lua' with 'c:\Users\me\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_PLT\modifiers.lua' so that all Modifier-Switches(momentary) binds were in both files, started DCS and low-and-behold ALL the red exclamation marks were gone!

Further Tip, I used WinMerge to harmonize the two lua files. This utility has been a god-send in usefulness over the years. I can heartily recommend it, especially if you edit files--like DCS lua binds--regularly.

[alaindufour]

that means these button have mapped automatically themselves elsewhere. look at the general or UI tab if they are there. if so delete them

[Captain Orso]

Hi Alain!

I'm not sure what you mean. It's difficult to talk about this subject, because there is no normal terminology. I call all the lines you find under 'Options / Controls / Aircraft name and seat position' the 'bind sockets'. You bind your HW buttons, switches, etc (that is to say, the labels DirectX gives to them)  into these sockets. The controller names are in the columns.

In the AH-64D CP/G for example, all the KU (Keyboard Unit) sockets suddenly all had the red exclamation marks, with no tool-tip telling you what the issue was, which it should do, and does when you actually double-bind the same controller button to one of the universal pages (pages that are always active, regardless of which aircraft you are flying; EG UI Layer, Airdrome Free Camera, Command Menu, or General) to another universal page or an aircraft/seat page.

But this was not the case. The AH-64D CP/G page, category KU has under the keyboard column just the alphabet keys, a few of the special keys like ` , . - and the NUM-PAD keys, and none of theses are used per default in any of the universal pages without default modifiers like LAlt. I did have nearly all of them assigned in AH-64D Pilot page using the Modifier-Switches(momentary) set to TM Warthog Throttle JOY_BTN24 which I named KU_Switch.

As soon as I added TM Warthog Throttle JOY_BTN24 KU_Switch to 'c:\Users\me\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_AI_Menu\modifiers.lua' and restarted DCS, ALL the red exclamation marks in the AH-64D Pilot page KU category were gone.

None of the sockets on the AH-64D George AI Helper page have corresponding sockets on the AH-64D CP/G page, nor visa-versa.

The issue is, if you have 'Modifier-Switches(momentary)' defined, that DCS at times somehow muddles these up internally as if you had binded the same controller button in a universal page and an aircraft page, so that DCS doesn't know which socket it should asserted when the button is pressed. But this is in error, because there is no such actual case in the files.

The solution is, harmonize the 'Modifier-Switches(momentary)' definitions in the Modifiers of the complaining page and then the complaints stop.