Keyboard input handler: compatibility problem with Stream Deck Hotkeys? Timing issue?

[xray-sierra]

I have have a new Stream Deck with a Hotkey mapped as a "Num/" button to zoom out the camera. Unfortunately that key isn't properly recognized by DCS. I'm currently running OpenBeta 2.5.6.55690. Meanwhile, the equivalent Stream Deck Hotkeys for "Num*" and "NumEnter" works just fine to zoom in and reset zoom.

 

Under adjust controls the Stream Deck "Num/" Hotkey jumps straight to "Keyboard /", whereas the Stream Deck Hotkeys for "Num*" and "NumEnter" jump to their proper keyboard mappings.

 

When I probe the keycodes with a javascript keyboard tool found at https://unixpapa.com/js/testkey.html, it shows the Stream Deck output for "Num/" as being indistinguishable from my the "Num/" key behaviour of my keyboard, so I suspect that there is a subtle timing issue within the DCS keyboard input handling routines. How to get ED to take a look at this problem?

 

Keyboard input "/" key results produces:

keydown keyCode=191 which=191 charCode=0

keypress keyCode=47 (/) which=47 (/) charCode=47 (/)

 

Keyboard input "Num/" key produces:

keydown keyCode=111 (o) which=111 (o) charCode=0

keypress keyCode=47 (/) which=47 (/) charCode=47 (/)

 

Stream Deck Hotkey set to "Num/" key produces:

keydown keyCode=111 (o) which=111 (o) charCode=0

keypress keyCode=47 (/) which=47 (/) charCode=47 (/)

 

[shagrat]

 

 

I have have a new Stream Deck with a Hotkey mapped as a "Num/" button to zoom out the camera. Unfortunately that key isn't properly recognized by DCS. I'm currently running OpenBeta 2.5.6.55690. Meanwhile, the equivalent Stream Deck Hotkeys for "Num*" and "NumEnter" works just fine to zoom in and reset zoom.

 

Under adjust controls the Stream Deck "Num/" Hotkey jumps straight to "Keyboard /", whereas the Stream Deck Hotkeys for "Num*" and "NumEnter" jump to their proper keyboard mappings.

 

When I probe the keycodes with a javascript keyboard tool found at https://unixpapa.com/js/testkey.html, it shows the Stream Deck output for "Num/" as being indistinguishable from my the "Num/" key behaviour of my keyboard, so I suspect that there is a subtle timing issue within the DCS keyboard input handling routines. How to get ED to take a look at this problem?

 

Keyboard input "/" key results produces:

keydown keyCode=191 which=191 charCode=0

keypress keyCode=47 (/) which=47 (/) charCode=47 (/)

 

Keyboard input "Num/" key produces:

keydown keyCode=111 (o) which=111 (o) charCode=0

keypress keyCode=47 (/) which=47 (/) charCode=47 (/)

 

Stream Deck Hotkey set to "Num/" key produces:

keydown keyCode=111 (o) which=111 (o) charCode=0

keypress keyCode=47 (/) which=47 (/) charCode=47 (/)

 

This is an issue in StreamDeck. For these NumLock buttons (similar problems for the num keys doubling as up/down/left/right etc.) you need to select the respective "key" from the drop-down menu in the StreamDeck Software, so it sends the correct Keyboard output.

There is also hidden the option to have StreamDeck distinguish between LCTRL and RCTRL and LSHFT and RSHFT.

Another issue with StreamDeck is the RALT key, the Left and Right ALT keys are recognized by their Keyboard related "messages"(?) instead of the keyCode so Right ALT (ALT GR) sends ALT+CTRL and thus it can't be used as RALT in DCS combos.

 

Edited November 1, 2020 by shagrat