I’m still learning how this kb stuff works down at the board level so I apologize if this is obvious to the old heads.
I’ve used the TEX Shinobi online configurator to remap my CAPS_LOCK as Left Control. This has been a lot more reliable than doing the remapping in the OS with, say, Input Remapper. However it means that Left Control actual no longer works. As in I see nothing from it when activating Screenkey nor with xev.
Ideally I would like to have CAPS_LOCK and Left Control actual both result in a Left Control key event.
I don’t have a ton to offer, but you might try manually mapping LCtrl to both keys, even if the configurator shows it already correct. Sometimes explicitly telling them to do something can help, especially if some stray logic is messing up the default. An escalation of that idea would be to flash it with something “wrong” on the LCtrl key, then reflash with it fixed. Beyond that, you could also try mapping the LCtrl key or the CapsLock to be a RCtrl and see if that works out or if it causes trouble with the real RCtrl.
Barring all that, you could ask Tex, but, yeah, asking vendors can be a chore even when they want to be helpful.
I was able to resolve this by changing the chosen profile. The Shinobi has a series of 6 dip switches which, according to the docs, do slightly different things depending on whether you have uploaded a configuration to the keyboard. When using Profile 1 you set dip switch #1 to on. That seems to have the dual purpose of activating Profile 1 and doing a Fn ↔ Left Control swap.
I set the desired configuration in the web configurator for Profile 3, uploaded, and then selected Profile 3/deselected Profile 1 and it is now working as desired. That being:
