Hi. Here’s a long, long shot, but worth to try the post.
Why do you want to make F13-F24 new keyboard keys on your secondary USB Numpad?
Answer: Quicker animation keybinds (and modifiers assigned by shortcuts), rigging presets and bone selections… there is a plethora of uses to speed up workflow with those new keys enabled.
Ok, so you know you can manipulate blender different editors depending on your shortcut keys.
In Windows 7, 8,10+ etc. you can configure extra keyboard keys that are not physically on your keyboard, such as F13 (which is produced by using Shift+F1), F14 (produced with Shift+F2), F15 (produced with Shift+F3), F16, F17, F18, F19, F20, F21, F22, F23 and F24.
Someone in the community ran a quick python listen code, and this is what Blender returned for F13:
He mentioned that Blender says that the key is “unnasigned” and there for it’s “unknown”.
Here’s where it gets complicated;
I wanted to assign a second USB Numpad key keyboard (key #1) to F13 to “FRAME FORWARD”
But the (1) Key on the second Numpad key, behaves exactly as (1) in my original typing keyboard.
You may say: Easy solve: Use a program like the old HIDMacros test the key press on your second numpad (key 1) and reassign it using this code to F13:
but the HIDMacros doesn’t respond as F13, it still responds as Numpad1 (identifying the HID device as device 2 on Windows…) So Windows knows it’s got a secondary USB Numpad assigned. The next step is have HIDMacros detect we want to re route that keypress to F13.
The final step will actually be pushing the “shortcut key assignment in Blender” with the new rerouted Numpad 1 (F13) to make the frame go forward.
But it seems I can’t get scenario 1 working right (reassigning the numpad to F13) and scenario 2 (Blender needs to figure what key is F13) can’t be detected either.
I know accomplishing this is possible, I am just not getting the configurations correctly.
Has anyone ventured into looking how to extend HIDMacros for Blender?
Update, I remapped the secondary USB Numpad key (1) with HIDmacros like this:
Now F13, is correctly recognized in OBS.
F13 is not recognized as F13 in Blender. It’s still showing 01 Numpad. And if I press 01 on my main numpad I get the exact same behavior (in this post thread example: to go forward 1 frame).