0x7B:0xB3 used to work, now it doesn't. no clue why.

[lemero]

The line I run at every start-up is:
uncap 0x79:0xAF **0x7B:0xB3** 0x78:0xAE 0x14:0x14
F9 vol up, F12 play/pause, F10 vol down, capslock to capslock
All the other mappings work just fine.

[susam]

Are you using version 0.3.0 of Uncap?

Can you download version 0.2.2 of Uncap from https://github.com/susam/uncap/releases/tag/0.2.2 and see if the issue disappears?

[lemero]

Are you using version 0.3.0 of Uncap?

Can you download version 0.2.2 of Uncap from https://github.com/susam/uncap/releases/tag/0.2.2 and see if the issue disappears?

Hi, thanks, that didn’t help. Still behaved the same. I’m not sure which one I have so I disabled it then ran the one you linked.
I tried re-mapping using the Insert key instead of F12, 0x2D:0xB3 but it also doesn't work. Could be some issue with the media key map?

[susam]

All previous releases of Uncap are available here: https://github.com/susam/uncap/releases/.

If a previous version of Uncap worked for you, one of the versions available here should still work for you. The changelog for each version can be found here: https://github.com/susam/uncap/blob/master/CHANGES.md.

If you can find out which version of Uncap works fine for you, that would help me to narrow down the cause of the issue. It is very likely that version 0.2.2 works fine because version 0.3.0 is the only one that introduces a major change in the way key-strokes are handled.

To find out exactly which version works fine, you have to choose a version, install that, kill any other instances of Uncap (uncap -k), ensure no Uncap is running via Task Manager, then run the chosen version of Uncap, and see if it works for you.