Page MenuHomeFeedback Tracker

Keybinding Display Issue
Feedback, NormalPublic

Description

I use a Corsair Scimitar RGB Pro mouse and it has 12 extra buttons on the side. In the Corsair Software I've mapped these buttons to Function 13 through 24. Now, no actual keyboard has physical Function keys above 12 but they do exist and can be mapped.

All of these keys are able to be bound in ArmA III and work just fine. The issue is that they all display as "UNEXPECTED_KEY_ID" in the controls menu making it impossible to tell what key is what.

The text just needs update to read as F13 through F24 for their respective keys. See the screenshot below for an example. All three of the actions are bound to different keys but they all display the same.

Details

Severity
Tweak
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
Version 1703 (OS Build 15063.296)
Category
Controls
Steps To Reproduce

Bind any control to a function key in the F13-F24 range.

Additional Information

Event Timeline

So not even a response?

This is kind of a really special situation maybe there are some other things todo. Such tickets get sometimes resolved some days before the update.

F13, F14, and F15 now work, F16~F24 still work as keybinds, but display as "UNEXPECTED_KEY_ID"
Found that this is almost certainly related to missing DIK keycodes
These I believe are the missing DIK code and scancode lines, from "\a3\ui_f\hpp\definedikcodes.inc"
Reference I found for DIK codes: https://community.bistudio.com/wiki/DIK_KeyCodes

#define DIK_F16 0x67
#define DIK_F17 0x68
#define DIK_F18 0x69
#define DIK_F19 0x6a
#define DIK_F20 0x6b
#define DIK_F21 0x6c
#define DIK_F22 0x6d
#define DIK_F23 0x6e
#define DIK_F24 0x76

dedmen changed the task status from New to Feedback.Nov 19 2024, 4:04 PM
dedmen added a subscriber: dedmen.

Fixed 2.20