DCSW misreading keyboard

[doveman]

I've got a Sidewinder X4 which has six macro keys, which I can assign keystrokes to. If I assign End to one of them, it registers as End as far as everything is concerned except for DCSW, which decides it's Num1!

 

I've even checked with a program called Keycode and that shows it's sending End (Keycode=35) just the same as if I press the actual End key, or one of my joystick buttons mapped to End with Xpadder or one of my mouse buttons mapped to End with AutoHotKey (both of which DCSW sees correctly).

 

I already ran into the bug where I couldn't open the radio because DCSW doesn't see my \ key properly but as OEM102, so I had to add that in the Control settings and this seems to be yet another keyboard bug, so I hope there's a fix in the works.

[doveman]

Hmm, seems it's not DCSW's fault this time as it's doing the same in Arma and sending Num1, despite being set to End and Keycode seeing it as End outside of games.

 

I note Num1 also has End written on it and it sends End (code 35) when Numlock is off, so maybe that's a clue but I don't understand it.

[agrasyuk]

this is indeed the case sometimes - DCS does see the original key and the macro you send. that makes utilities such as HIDMacros unusable. crude workaround - use only DX keys for macros and try try to get 15-50msec delay between the [modifyer key dow] and [actual key down] events. DCS is sencitive about that as far as i can tell.

[doveman]

Yeah, in this case I've just been using MS Intellitype which allows me to assign Keystrokes or Macros and for this key I just assigned Keystroke "End", which as I say is seen just the same as the actual End key by "Key Scan Codes v3.0" http://www.delphiforfun.org/programs/utilities/KeyCodes.htm

 

The only difference is when holding the real End key, it sends repeating Keydown events and a single Keyup on release, whereas with the hotkeys it only sends a single Keydown event and a single Keyup when on release, so although the key is held it doesn't autorepeat. Keys I setup with AHK are seen exactly the same though and still work and are seen as held keys by programs/games.

 

So why DCS and Arma see the hotkey as Num1 when I've mapped it to End I have no idea. If I can work out how to use the HID codes sent by the keyboard, I'll try mapping the hotkeys with AHK instead of Intellitype to see if that's any better.

[doveman]

I seem to have fixed this now by uninstalling Intellitype and installing Microsoft Mouse and Keyboard Centre. I've only tested in Arma so far but that sees End, not Num1, now so I'm fairly sure DCSW will as well.

 

EDIT: Yes, it does :)