Red Exclamation mark

[dresoccer4]

Just reinstalled DCS on a new PC and fired her up and noticed this red explamation mark next to one of my favorite key bindings, transpose camera. 

I tried clearing the mapping but its still there. No other exclamation mark appears and I can't get it to go away. Anyone know what to do?

Trying to bind to mouse button 2

nullnull

[SharpeXB]

I think it means you need to reassign a modifier that’s missing. That’s what it’s meant when I’ve seen it. 

Edited February 27, 2024 by SharpeXB

[dresoccer4]

Just now, SharpeXB said:

I think it means you need to reassign a modifier that’s missing. 

what does that mean? 

in the screenshot you can see there are no keys binded to that action at all. i tried resetting it and re-binding it, but the red exclamation won't go away and it essentially renders that command useless. which is a shame since i rely on transpose quite a bit

[Trigati]

There might be a ‘modified’ binding but if the modifier is no longer defined/available it doesn’t show the binding so looks blank like your screenshot.

Check your modifiers maybe.


Sent from my iPhone using Tapatalk

[SharpeXB]

13 minutes ago, dresoccer4 said:

what does that mean?

It must mean it’s looking for a button that’s no longer available. In my case it was a modifier which needed to be reassigned. 

[Chops]

It means that you have duplicate key mappings.  Check the UI Settings and Modules.

[sthompson]

16 hours ago, SharpeXB said:

It must mean it’s looking for a button that’s no longer available. In my case it was a modifier which needed to be reassigned. 

That was my experience when I moved to a new PC. Apparently DCS will not display a mapping that uses a modifier that no longer exists and instead shows the red exclamation with no useful tooltip to indicate what is going on. The solution is to recreate the missing modifier.

[dresoccer4]

1 hour ago, sthompson said:

That was my experience when I moved to a new PC. Apparently DCS will not display a mapping that uses a modifier that no longer exists and instead shows the red exclamation with no useful tooltip to indicate what is going on. The solution is to recreate the missing modifier.

how do you "recreate the missing modifier"? currently there is no key command or modifier mapped to the Transpose function. if I go in and add a mapping (right mouse button 2), the red exclamation mark is still there. not sure what else to do with this.

 

9 hours ago, Chops said:

It means that you have duplicate key mappings.  Check the UI Settings and Modules.

how can you see all of your duplicate mappings? if you look at my screenshot the Transpose command has nothing mapped to it at all, so how can there be duplicate? 

[Trigati]

To find missing modifier, go to the saved games folder and find the modifiers.lua file

In there it should list all the ones setup/expected…work out the missing one and re-create it (any mod as long as it has the same name as the missing one)

You should be able to see the binding then, and delete it

Not sure this will work but best suggestion I can make


Sent from my iPhone using Tapatalk

[sthompson]

4 hours ago, dresoccer4 said:

how do you "recreate the missing modifier"? currently there is no key command or modifier mapped to the Transpose function. if I go in and add a mapping (right mouse button 2), the red exclamation mark is still there. not sure what else to do with this.

As nearly as I can tell the red exclamation means there is an invalid or conflicting mapping. If it's a conflicting mapping then hovering over the exclamation will display more information about the conflict. In your case, the problem most likely is not a duplicate mapping but rather the entry is invalid for some reason, usually because it references a modifier that DCS can't find. Unfortunately, unlike the case of duplicate mappings, hovering on the exclamation gives no information about the problem, and since it won't display the invalid mapping there is no way to see what the problem is from within DCS itself.

Here is how to fix the problem. Go into Saved Games, then your DCS folder then config\input then your module then "joystick." You should see a *.diff.lua file for the binding in question. Open that lua file in a text editor and find the entry for the problem binding where you see the exclamation. It should be somewhere in the section with header ["keyDiffs"]. I don't have the F1 module so can't find the exact string you pointed out, but here is an example from one of my modules:

["d10077pnilunilcdnilvd0vpnilvunil"] = {
            ["added"] = {
                [1] = {
                    ["key"] = "JOY_BTN15",
                    ["reformers"] = {
                        [1] = "MOD",
                    },
                },
            },
            ["name"] = "Radar Range Switch - SHORT",
        },

Note that even though no keybinding is being displayed within DCS, there should be such a keybinding in the file. The name of key binding comes at the end of the entry. Note the [1]="MOD" entry. That indicates that this keybinding uses a modifier named "MOD." This is the modifier definition you need to recreate. Until you do that, DCS will not display the existing binding that is causing the problem.

Once you know the name of the missing modifier you can recreate it. Go into the controls page for your module and click on the link at the bottom to add a modifier. Now define a new modifier and make sure it has exactly the name of the missing modifier. The invalid entries should now be valid and should reappear.

If you use the same modifiers in other modules you can copy the modifiers.lua file from one module to the others in order to fix the problems in those modules without having to recreate the modifiers again for each one separately.

[dresoccer4]

1 hour ago, sthompson said:

As nearly as I can tell the red exclamation means there is an invalid or conflicting mapping. If it's a conflicting mapping then hovering over the exclamation will display more information about the conflict. In your case, the problem most likely is not a duplicate mapping but rather the entry is invalid for some reason, usually because it references a modifier that DCS can't find. Unfortunately, unlike the case of duplicate mappings, hovering on the exclamation gives no information about the problem, and since it won't display the invalid mapping there is no way to see what the problem is from within DCS itself.

Here is how to fix the problem. Go into Saved Games, then your DCS folder then config\input then your module then "joystick." You should see a *.diff.lua file for the binding in question. Open that lua file in a text editor and find the entry for the problem binding where you see the exclamation. It should be somewhere in the section with header ["keyDiffs"]. I don't have the F1 module so can't find the exact string you pointed out, but here is an example from one of my modules:

["d10077pnilunilcdnilvd0vpnilvunil"] = {
            ["added"] = {
                [1] = {
                    ["key"] = "JOY_BTN15",
                    ["reformers"] = {
                        [1] = "MOD",
                    },
                },
            },
            ["name"] = "Radar Range Switch - SHORT",
        },

Note that even though no keybinding is being displayed within DCS, there should be such a keybinding in the file. The name of key binding comes at the end of the entry. Note the [1]="MOD" entry. That indicates that this keybinding uses a modifier named "MOD." This is the modifier definition you need to recreate. Until you do that, DCS will not display the existing binding that is causing the problem.

Once you know the name of the missing modifier you can recreate it. Go into the controls page for your module and click on the link at the bottom to add a modifier. Now define a new modifier and make sure it has exactly the name of the missing modifier. The invalid entries should now be valid and should reappear.

If you use the same modifiers in other modules you can copy the modifiers.lua file from one module to the others in order to fix the problems in those modules without having to recreate the modifiers again for each one separately.

thanks for the detailed explanation. so i went to the place you described and opened up my mouse.diff.lua and this is what I see. i don't see a MOD segment. what happens if i just deleted the whole "transpose" segment and load the sim again. i'll try it now

local diff = {
    ["keyDiffs"] = {
        ["d1593pnilu1594cdnilvdnilvpnilvunil"] = {
            ["added"] = {
                [1] = {
                    ["key"] = "MOUSE_BTN2",
                },
            },
            ["name"] = "Camera transpose mode (press and hold)",
        },
        ["d363pnilunilcdnilvdnilvpnilvunil"] = {
            ["added"] = {
                [1] = {
                    ["key"] = "MOUSE_BTN3",
                },
            },
            ["name"] = "Force cursor to show, toggle",
        },
    },
}
return diff

[dresoccer4]

update: well i finally fixed it but i had to go nuclear and delete the entire input folder. i backed up the keys so will go in and re-load plane by plane and hopefully it stays fixed

[sthompson]

40 minutes ago, dresoccer4 said:

thanks for the detailed explanation. so i went to the place you described and opened up my mouse.diff.lua and this is what I see. i don't see a MOD segment. what happens if i just deleted the whole "transpose" segment and load the sim again. i'll try it nowloc

"MOD" was an example from my setup. Yours would be different.  For example, if your modifier was called JOY20 then you would see a line in the "Camera Transpose Mode" segment that read [1]="JOY20". Your approach of deleting the "Camera Transpose Mode" segment will probably work, but would have to be done for every potential reference to a modifier that is no longer valid.

Also, it's possible that the issue is in one of your other *.diff.lua files for the module.

 

1 minute ago, dresoccer4 said:

update: well i finally fixed it but i had to go nuclear and delete the entire input folder. i backed up the keys so will go in and re-load plane by plane and hopefully it stays fixed

Glad you got it fixed but it's going to be painful to recreate mappings for every DCS module!