Red exclamation mark in bindings on A-10C II only

[imacken]

I have this issue. Red exclamation marks in the A-10C II for the View Left (and Right) Slow only.

The same binding exists in all other modules with no issue, and it is not a conflict AFAICS, as if I remove all bindings for keyboard and other devices, the exclamation marks still are there, only for that View Left (and Right) Slow, and only in the A-10C II.

I've attached the A-10C equivalent as well.

Any ideas?

Edited April 18, 2021 by imacken

[rob10]

I had something similar yesterday.  I was playing with adding a modifier to a binding to allow me to use a rotary to change DDI brightness along with radio presets.  After I assigned one modifier I decided I was going to use a different one.  Went into the modifiers options and deleted the modifier I had added and when I came back out to the bindings I had the same red exclamation marks.  Note that I still had the modifier (now deleted) assigned when I came back out.  I cleared those boxes (with the clear function) and exclamation marks disappeared and then I bound it to the new modifier and all was good.  Doesn't look like you have modifiers assigned, but hopefully this might help point you in the right direction.

[Flappie]

@imackenIf you hover your cursor above a red mark, a message will inform you about what is conflicting.

[imacken]

8 minutes ago, Flappie said:

@imackenIf you hover your cursor above a red mark, a message will inform you about what is conflicting.

Normally, it would, but weirdly, in this case it doesn't.  I also tried the modifier thing suggested by rob10, and that made no difference.

 

As I said, this bind is common to all modules, but only the A-10C II has this issue.  There is no conflict at all that I can see.

[Flappie]

Look into "C:\Users\username\Saved Games\DCS.openbeta\Config\Input\A-10C II\keyboard". Is there a file in here? If so, it might contain "Num4" and "Num6" modifications. If you don't want any of the modifications the file contains, juste rename the file and retstart the game to see if something changes.

[imacken]

No keyboard file. Even if I delete the keyboard (and other device) binds for these 2 commands, the red exclamation mark is still there.

[Flappie]

Weird. This would mean the red marks come from the main DCS folder input files...

 

Try this:

1. remove "D:\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\keyboard\default.lua"
2. run a fast repair

[imacken]

Neither a fast or deep repair put the keyboard default.lua file back in.  

Still, with an emply folder keyboard folder, I loaded a free flight mission for the A-10C II, went to Controls, and the num 4 and num 6 were still red marked.

[Flappie]

Well, I have no clue about what's happening to you.

Here, take my "\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\keyboard\default.lua" file.

default.lua

[imacken]

Sorry, I was running the wrong version of DCS in Skate's utility! Duh!  So, ignore the last couple of comments. Let me try again and I'll report back in a couple of mins.

[imacken]

Hmm, so #i think this issue is do to with the profiler I use for my bindings. Probably nothing to do with DCS, but I'll investigate further later.

[Frederf]

This happens when two lua have different contents for exact same command name. For example if keyboard/default.lua gives Do X "Command A" and joystick/default.lua gives Do Y "Command A" then in control list there will by a ( ! ) on the line labeled "Command A" because the actions in different columns on that row are different. If you look at all your .lua for the ( ! )'d lines you'll see one is different than another.

[imacken]

The thing is, I can have no bindings at all for this as you can see from the image on my 3rd post, and still there is a red exclamation mark.

[Frederf]

The action slot is still there even if the default key isn't. The view up down left right aren't usually defined in the module explicitly but imported from a generic file that gets applied to many modules.

 

I'm guessing either the generic file has the error or the a10 file is also defining that command with !.

[imacken]

Well, if I copy the A-10C diff.lua for the device in question to the A-10C II folder, the red mark goes away. Same binds. 

[Flappie]

Weird. Can you please attach the two files? (if you've kept the bugged .diff.lua) I'd like to compare them.

[imacken]

Sure. Which 2 do you mean? The problem diff.lua and what other one?

[Flappie]

The one that was causing the error and the one you replaced it with.

[imacken]

OK, here you go.

Working VPC Throttle MT-50CM3 {3AD8D3C0-7082-11EB-8002-444553540000}.diff.lua Non-working VPC Throttle MT-50CM3 {3AD8D3C0-7082-11EB-8002-444553540000}.diff.lua

[Frederf]

The only difference between the two files is the section lines 236-267 where it is specified to remove from default the POV directions from trim up/down/left/right.

I recommend using the working version of that file (or delete the lines 236-267 from other file) and simply bind/verify your four trim controls.

 

The .diff.lua is saying "this is how I want to alter the original .lua file". But default.lua doesn't have a key to remove (older version of default.lua probably did). And so your non-working diff is saying to unbind POV from trim and original lua is saying hey there's nothing to remove. That would cause the warning.

[imacken]

Ok, thanks you for that. I’ll look into what you say. However, I don’t understand why trim is involved. I’m not rebinding them at all. They are default. 

[Flappie]

@imacken.diff.lua for keyboards are supposed to be called "Keyboard.diff.lua", not "VPC Throttle..." or any other joystick name.

 

Are you sure you've sent us the .diff.lua contained in "Saved Games\DCS.openbeta\Config\Input\A-10C II\keyboard" ?

[imacken]

No, I sent the 2 you asked for, i.e. the throttle one that everything works with, and the one that doesn’t. Keyboard files not involved as far as I know. 

[Flappie]

The first picture in the OP made me think it was an issue with the keyboard (see, the red marks are repeated in the keyboard column).

 

Here his is the A-10C II joystick default.lua file (DCS reference for all joysticks):

{pressed = iCommandPlaneTrimUp, up = iCommandPlaneTrimStop,    name = _('Trim: Nose Down'),	     category = _('HOTAS')},
{pressed = iCommandPlaneTrimDown, up = iCommandPlaneTrimStop,  name = _('Trim: Nose Up'),			 category = _('HOTAS')},
{pressed = iCommandPlaneTrimLeft, up = iCommandPlaneTrimStop,  name = _('Trim: Left Wing Down'),   category = _('HOTAS')},
{pressed = iCommandPlaneTrimRight, up = iCommandPlaneTrimStop, name = _('Trim: Right Wing Down'),  category = _('HOTAS')},

 

This is the A-10C II VPCWarBRD + MT50.diff.lua file next to default.lua (another DCS reference, this time for VPC joysticks only):

["dnilp93u215cdnilvdnilvpnilvunil"] = {	["added"] = {	[1] = {	["key"] = "JOY_BTN12",	},},		    ["name"] = "Trim: Left Wing Down",},
["dnilp94u215cdnilvdnilvpnilvunil"] = {	["added"] = {	[1] = {	["key"] = "JOY_BTN10",	},},			["name"] = "Trim: Right Wing Down",},
["dnilp95u215cdnilvdnilvpnilvunil"] = {	["added"] = {	[1] = {	["key"] = "JOY_BTN9",	},},			["name"] = "Trim: Nose Down",},
["dnilp96u215cdnilvdnilvpnilvunil"] = {	["added"] = {	[1] = {	["key"] = "JOY_BTN11",	},},			["name"] = "Trim: Nose Up",},	

 

And this is your faulty custom .diff.lua:

["dnilp93u215cdnilvdnilvpnilvunil"] = { ["name"] = "Trim: Left Wing Down",["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_L",}, },},
["dnilp94u215cdnilvdnilvpnilvunil"] = { ["name"] = "Trim: Right Wing Down",["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_R", 	}, },	},
["dnilp95u215cdnilvdnilvpnilvunil"] = { ["name"] = "Trim: Nose Down",["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_U", 	}, },	},
["dnilp96u215cdnilvdnilvpnilvunil"] = { ["name"] = "Trim: Nose Up",["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_D", 	}, },	},

 

Red marks appear when your .diff.lua asks to remove "JOY_BTN_POV1_L / R / U / D" where it should be "JOY_BTN12 / 10 / 9 / 11".

 

But since both the code and name of the command are specified in it, I don't understand why a .diff.lua has to specify keys it wants to remove from default controls. This may be the reason for all the .diff.lua issues we see here from time to time. You know, the usual "this update broke all my controls!" kind of post.

 

Thanks to both of you @imacken and @Frederf. I understand all these .diff.lua things better now.

[imacken]

Well, now I am totally confused.  What does the default WarBRD+MT50 lua file have to do with this?  I have a WarBRD+Alpha and the trim hat buttons are 14.15.16 and 17, not 9-12?