Missing default key bindings after update

[funkyfranky]

Anyone else missing some default key bindings after the recent update 1.5.2?

E.g. PCA buttons in the armament panel used to work with 1,...,5 But these do not exist anymore for me. In DCS 2.0 they are still there.

[PiedDroit]

I had this too, I just remapped them.

Edit:

A better fix would be to update Mods/Aircraft/M-2000C/Input/keyboard/default.lua, to avoid filling the .diff.lua with unecessary bindings.

 

Here's what was changed (it's a sample):

 

old:

{combos = {{key = 'V'}}, down = iCommandPlaneModeVS, name = 'Close Air Combat Mode', category = 'HOTAS'},

{combos = {{key = 'D'}}, down = iCommandPlaneModeHelmet, name = 'Special Modes Deselect', category = 'HOTAS'},

{combos = {{key = 'O'}}, down = iCommandPlaneModeGrid, name = 'Ground Avoidance Mode', category = 'HOTAS'},

 

update:

{down = iCommandPlaneModeVS, name = _('Close Air Combat Mode'), category = _('HOTAS')},

{down = iCommandPlaneModeHelmet, name = _('Special Modes Deselect'), category = _('HOTAS')},

{down = iCommandPlaneModeGrid, name = _('Ground Avoidance Mode'), category = _('HOTAS')},

 

The default key was removed, what has to be done is to add it back:

 

fix:

{combos = {{key = 'V'}}, down = iCommandPlaneModeVS, name = _('Close Air Combat Mode'), category = _('HOTAS')},

{combos = {{key = 'D'}}, down = iCommandPlaneModeHelmet, name = _('Special Modes Deselect'), category = _('HOTAS')},

{combos = {{key = 'O'}}, down = iCommandPlaneModeGrid, name = _('Ground Avoidance Mode'), category = _('HOTAS')},

Edited January 24, 2016 by PiedDroit

[Rlaxoxo]

Yea, I've removed the default mappings on some keybinds to remove Unusable binds when they become RED like that.

 

Now I've done that for some others cus I prefer it like that, I made it for my self I didn't expect that would get into the fix so I didn't really bother

 

but sedenion made a his own version with custom default binds and stuff which is really neat

 

http://forums.eagle.ru/showpost.php?p=2647298&postcount=21

 

I could have remapped the custom binds but I honestly didn't bother cus like I said I just prefer it like that

 

I change all my default binds in the first place cus I'm more a less of a bind freak I have almost every bind mapped in every module

[PiedDroit]

I wasn't necessary because those compatibility problems were mostly comming from the inclusion of base_keyboard_binding.lua instead of common_keyboard_binding.lua.

 

Fixed file attached, I tested it with an empty .diff.lua, everything worked. 'K' worked as radar piper down, I suppose you still need to change it or remap "show kneeboard" to have the kneeboard.

 

Mods/Aircraft/M-2000C/Input/keyboard/default.lua

 

P.S.: I added the patch file, you don't need to copy it anywhere, I provide it only to indicate the changes between the current file and the modified one.

 

EDIT2: a better file is available a few post after this one, adding flight controls and other missing default mappings for 1.5.2

default.lua

default.lua.patch.txt

Edited January 24, 2016 by PiedDroit
better file below

[Redglyph]

Yes, canopy open/close was unmapped for me for M-2000C, in 1.5.2.49392.141 (not in 2.0.0.49135.73). Not in the P-51 though. Weird.

Maybe other keys, didn't check them all.

[PiedDroit]

Yes, canopy open/close was unmapped for me for M-2000C, in 1.5.2.49392.141 (not in 2.0.0.49135.73). Not in the P-51 though. Weird.

Maybe other keys, didn't check them all.

Actually, canopy open/close was one of the default keybinding coming from base...lua (that is not anymore included).

 

They added it in M-2000C/default.lua but there is no default mapping for it:

 

{down = iCommandPlaneFonar, name = _('Canopy Open/Close'), category = _('Systems')},

 

P.S: full patch of the 1.5.2.49392.141 update attached, so yo ucan see what was added and removed.

default.lua.patch-of-1.5.2.49392.141-update.txt

[Redglyph]

Sorry, must be tired, I misread your previous post :)

[PiedDroit]

Sorry, must be tired, I misread your previous post :)

No, you were right, canopy open/close default keyboard mapping was added in 2.0 update but not in 1.5.2 update.

 

I have attached another modified file that adds the default keyboard mappings that were included in 2.0 but not in 1.5.2:

- open/close caopny

- engine and flight controls

- lights and hud brightness

- fire and jettison weapons switch

default.lua

default.lua.2.patch.txt

Edited January 24, 2016 by PiedDroit

[funkyfranky]

Thanks mate, this is very useful!

[wdrago]

Also notice default mapping vanish for "next waypoint" and "previous waypoint".

(on that subject haven't found how to select waypoint on INS panel ?).

 

Other think, more belong to ED i supposed, the ability to map some action with mouse.

I usually map "clikcable cockpit" to my mouse and for that I have to edit lua...

 

Dev should know that today most of player mouse have more than 2 bouttons /joke :music_whistling:

[yeepee]

Just give us default key bindings !

 

For 2 keys in conflict, you just delete all keys ?! WTH ! We (I) don't want joystick mapping, 1st of all we need keyboard mapping.

 

Having some keys to edit in our profile is not a major issue but having to do all the biding is it.

[PiedDroit]

Also notice default mapping vanish for "next waypoint" and "previous waypoint".

(on that subject haven't found how to select waypoint on INS panel ?).

 

Other think, more belong to ED i supposed, the ability to map some action with mouse.

I usually map "clikcable cockpit" to my mouse and for that I have to edit lua...

 

Dev should know that today most of player mouse have more than 2 bouttons /joke :music_whistling:

I don't know about those mappings, probably they were from the base.lua file and were not put in the new default.lua.

 

To switch waypoint, use the DEST button (big yellow square button) on the INS panel.

The INS is very basic at the moment, once it is fully implemented we should get a bunch of shortcut that control it.

[Rlaxoxo]

Just give us default key bindings !

 

For 2 keys in conflict, you just delete all keys ?! WTH ! We (I) don't want joystick mapping, 1st of all we need keyboard mapping.

 

Having some keys to edit in our profile is not a major issue but having to do all the biding is it.

 

Well, sorry lol I didn't know they were gonna implement it like that

 

Like I said this is my style of playing

 

If you don't like them use sedenion rework

 

http://forums.eagle.ru/showpost.php?p=2647298&postcount=21

[yeepee]

Well, sorry lol I didn't know they were gonna implement it like that

 

Like I said this is my style of playing

 

If you don't like them use sedenion rework

 

http://forums.eagle.ru/showpost.php?p=2647298&postcount=21

 

Don't take it for you, it's not your fault, I know it. ;-)

 

I just don't know why devs have done something like this. I mean not everybody has a warthog or a X52, but everybody has a keyboard, so deleting lot of keyboard shorcut is just amazing...

 

I have take default key from my 2.0 install, but for some reason not all my keys works as it should like in my 2.0 and it drives me crazy when I join a server...

[Rlaxoxo]

Don't take it for you, it's not your fault, I know it. ;-)

 

I just don't know why devs have done something like this. I mean not everybody has a warthog or a X52, but everybody has a keyboard, so deleting lot of keyboard shorcut is just amazing...

 

I have take default key from my 2.0 install, but for some reason not all my keys works as it should like in my 2.0 and it drives me crazy when I join a server...

 

For the keys that don't work just remove the default binding from the keyboard.lua file

 

And they should work just fine

 

Just remember to rebind them afterwards

[yeepee]

For the keys that don't work just remove the default binding from the keyboard.lua file

 

And they should work just fine

 

Just remember to rebind them afterwards

 

Yep, I know, I make my own keyboard/default.lua with commonly used keys for DTC like , / . ; for example.