Highrez

But at no avail. What I am doing wrong? Im afraid to say, probably nothing. I suspect the game uses RAW/DIRECT Input, which operates below the level XMBC operates, and thus simply can not be manipulated by XMBC. Many games work this way - and therefore XMBC is pretty useless in those games, but it ...

Great, glad that worked. I fixed the typo above (thanks for pointing that out )

You could try...
Middle button -> Simulated Keystrokes
In the main input, enter: {LOCKY}
Set Method to 3 (During)
Un-tick the box: Block original message
Give the a go, let me know if it works or not!

EDIT: Fixed the typo mentioned below!

No, as I said above, the default profile uses the Windows setting... Subsequent profiles can alter this, but its not sensible for the default profile to alter the default windows setting (if that makes sense). It is still a really bad idea to use XMBC to swap the buttons as you have done, not least ...

Yes generally (at least in C++) HEX numbers are prefixed by 0x to indicate it is HEX. IF XMBC works with hex in these tags (I cant remember for sure) then it will be using the same convention (if it does not it probably should!!).

Glad to hear it - good research!
I *think* XMBC will accept it in HEX so long as it is prefixed with 0x so 0xF0 (but I'm not 100% sure).

Indeed if I do the same button swap, I do see the problem (it should work, even if its inefficient, so I will have a look at it, but I highly suggest your use the windows mouse control panel setting if you can!!!)

I've just noticed the button swap thing - thats a primary difference with my setup I guess.... But why are you doing it that way - there is a way to swap buttons natively in Windows using the mouse control panel (which does not require XMBC at all)... Untitled.png XMBC can control that setting also ...

Debug logging might help, but in this case, I doubt it, because all that will show me is the button presses etc. which your words above have pretty accurately described. I will have to see if I can reproduce it here (although i would have thought I would have noticed this myself if it was a generic ...

probably, but that's no excuse for me really is it

Can you possibly try the latest beta? there were some fixes for OneNote in there (although I don't think related to this problem) but I have (and use) onenote, both the Win10 one and the full Office 2021 Professional install (on both Win10 and 11) and haven't seen such issues. If it still happens on...

The log is correct. {M} is not a valid tag.
All tags are listed in the simkey setup screen window/help text (with examples too!)
Normal keys do NOT need { } around them!

You should be using {CTRL}M
Does that work?

Oh OK it must be something specific to the Japanese keyboard layout then - that's going to be tricky to figure out. XMBC sends the scancode for CAPSLOCK (which I guess is in your case meaning shift+capslock, I'm not sure how I can make that any different right now! I will have to try and setup a Jap...

But I don't understand shift+capslock .... On my keyboard, pressing capslock and shift+capslock makes no difference. And {CAPSLOCK} is XMBC should not be pressing SHIFT at the same time. More to the point, using a keyboard tester (like https://en.key-test.ru/ ) shows that XMBC {CAPSLOCK} is not send...

SHIFT+CAPSLOCK and CAPSLOCK (without shift) are identical on my keyboard...
What's the difference between the two on yours? Must be a language/layout specific thing?