Duplicated lines in Options/Controls: Now mostly fixed

[TAW_Impalor]

For me the issue is that SOMETIMES my custom blinds for kneeboard next and previous page get replaced by default [ and ], creating conflict with other binds. Restarting DCS usually fixes that. Only in Mirage module. Deleting the folder and assigning the buttons again did not help.

[LeCuvier]

In which folder/file do you create your "custom blinds for kneeboard next and previous page"?

The original commands are in "...\DCS World OpenBeta\Config\Input\Aircrafts\Common\keyboard\default.lua":

{combos = {{key = ']'}}                           ,             down = 3001, cockpit_device_id  = 100, value_down = 1.0, name = _('Kneeboard Next Page')  , category = _('Kneeboard')},
{combos = {{key = '['}}                           ,             down = 3002, cockpit_device_id  = 100, value_down = 1.0, name = _('Kneeboard Previous Page'), category = _('Kneeboard')},

And for what purpose do you create custom binds for these commands?

[TAW_Impalor]

9 hours ago, LeCuvier said:

In which folder/file do you create your "custom blinds for kneeboard next and previous page"?

The original commands are in "...\DCS World OpenBeta\Config\Input\Aircrafts\Common\keyboard\default.lua":

{combos = {{key = ']'}}                           ,             down = 3001, cockpit_device_id  = 100, value_down = 1.0, name = _('Kneeboard Next Page')  , category = _('Kneeboard')},
{combos = {{key = '['}}                           ,             down = 3002, cockpit_device_id  = 100, value_down = 1.0, name = _('Kneeboard Previous Page'), category = _('Kneeboard')},

And for what purpose do you create custom binds for these commands?

 

I don't touch any .lua. I assign key combinations in DCS Options - Controls menu. All my keystrokes are generated by Warthog TARGET, with single profile for all modules. To fit more commands I have two modifier buttons on my HOTAS. This all is beyond the point. I should be able to define my own keyboard bindings and they should work reliably.

[MAXsenna]

 
I don't touch any .lua. I assign key combinations in DCS Options - Controls menu. All my keystrokes are generated by Warthog TARGET, with single profile for all modules. To fit more commands I have two modifier buttons on my HOTAS. This all is beyond the point. I should be able to define my own keyboard bindings and they should work reliably.

He's just trying the help, and as this is his thread, and it's mainly about manually editing Lua files to temporarily fix it, I'd say his questions are spot on. But I can see the confusion.
If I were you, since you're already using T.A.R.G.E.T, I'd try out Homefries DX profile. It gives you 128 or so DX buttons to use, so can forget about keybinds altogether.
Now that I think of it. Why would you use keybinds anyway? You're obviously using buttons on you're HOTAS anyway, so you could literally use a button on you're HOTAS that's already. But now I think of it again. You're using the same profile for all modules.
Well, one problem is that ED should FORCE all 3rd parties to use the same keybinds for every similar function. That'd be awesome for VoiceAttack etc. but I work around that as I have VAICOMPRO and since VAICOM knows what module I'm in, I can say the same command (gear up), and it will execute the correct keybind depending on the module I'm using.
Sorry for getting of track.
Cheers!

Sent from my MAR-LX1A using Tapatalk

[TAW_Impalor]

22 hours ago, MAXsenna said:

Why would you use keybinds anyway?

 

Short answer: because I am lazy! I like to program a sequence of keystrokes into single button press or flip of a switch. I think it started with Mig21 and its incomplete autostart routine. A screenshot below explains what I mean. Then I adopted the same keystrokes to make F18, F16 etc battle ready. Or be able to turn the radar on and lock a bandit in JHMCS/boresight with one button, on any airframe. In my squad we may fly different planes in the same mission, so I must rely on muscle memory. I like the flexibility of TARGET for that. Some of my physical buttons generate both virtual keyboard keystrokes and virtual joystick button presses. I have VAICOM Pro as well, but only use it to talk to AI "people": Jester, Chief, Flight, Tanker, ATC...

 

[MAXsenna]

 
Short answer: because I am lazy! I like to program a sequence of keystrokes into single button press or flip of a switch. I think it started with Mig21 and its incomplete autostart routine. A screenshot below explains what I mean. Then I adopted the same keystrokes to make F18, F16 etc battle ready. Or be able to turn the radar on and lock a bandit in JHMCS/boresight with one button, on any airframe. In my squad we may fly different planes in the same mission, so I must rely on muscle memory. I like the flexibility of TARGET for that. Some of my physical buttons generate both virtual keyboard keystrokes and virtual joystick button presses. I have VAICOM Pro as well, but only use it to talk to AI "people": Jester, Chief, Flight, Tanker, ATC...
 

I meant why d'you use keybinds for the kneeboard, but I see.
VAICOM doesn't do commands, but that you probably know. That's what VoiceAttack's for. Can do some pretty cool macros (and other stuff) that one too.

Sent from my MAR-LX1A using Tapatalk

[LeCuvier]

I spent several hours today going through most of my modules in OB. The duplications have mostly disappeared.

There are still a few pairs of orange lines, but these are "legitimate" as they indicate an inconsistency. In all cases I found today, there are inconsistencies between lines of code with identical names, but different code between either

a) the "default.lua" under "\joystick" and the one under "\keyboard" or,

b) any of the "default.lua" and the "Throttle - HOTAS Warthog.lua"

I reported one of these cases for the FW-190D in this post:

https://forums.eagle.ru/topic/279245-optionscontrols-duplicated-orange-lines-for-ez42/?tab=comments#elControls_4746215_menu

 

However, the massive occurrence of duplicated orange lines for no good reason has obviously disappeared at least in Open Beta.