Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backtick/tilde key does not register on US QWERTY layout #216

Closed
b02860de585071a2 opened this issue Dec 12, 2021 · 6 comments
Closed

Backtick/tilde key does not register on US QWERTY layout #216

b02860de585071a2 opened this issue Dec 12, 2021 · 6 comments

Comments

@b02860de585071a2
Copy link

Describe the bug
Backtick/tilde (Windows virtual key 0xC0, keycode 0x0029, VC_BACKQUOTE in libuiohook) does not register when using the overlay. It does show and function properly in io-cct, although the keycode will appear as "0x0". Once the .json config is exported, the correct keycode is listed in the .json file, however input-overlay does not recognize the input (will not illuminate/react, key remains blank in OBS when pressed).

To Reproduce
Steps to reproduce the behavior:

  1. Open config/texture file in io-cct
  2. Add keyboard element, assign texture and keycode
  3. Save/export JSON file
  4. Launch OBS and confirm plugin is active
  5. Press "`" key
  6. Confirm it does not activate

Expected behavior
Backtick\tilde key illuminates on OBS when key is pressed

Screenshots

Current JSON file showing correct keycode:
ioscreenshot1

OBS input with all top-left keys pressed:
ioscreenshot2

Additional information:

Additional context
As mentioned, the correct keycode is being written to the JSON file that is exported from io-cct. I'm not sure if this is an issue with how libuiohook is integrated to recognize those codes, or something else. io-cct DOES recognize the key, which to me seems that whatever fix was pushed to io-cct did not make it to the actual end program. Every other key on my board (tenkeyless) provides the correct inputs.

@univrsal
Copy link
Owner

Can you download the nightly build from here, unpack demo_hook.exe from x86_64-win32-msvc/bin as well as uiohook.dll from x86_64-win32-msvc/lib somewhere and confirm the keycode you get when pressing that button?

@b02860de585071a2
Copy link
Author

b02860de585071a2 commented Dec 13, 2021

Can you download the nightly build from here, unpack demo_hook.exe from x86_64-win32-msvc/bin as well as uiohook.dll from x86_64-win32-msvc/lib somewhere and confirm the keycode you get when pressing that button?

Attached is a screenshot of the cmd output. It gives a keycode of "0x29", as well as a rawcode of "0xC0", which is the Windows virtual key code for my region (US standard keyboard).

io_output_backtick_nightlybuild

Hope this helps.

@Gn9sis
Copy link

Gn9sis commented Apr 18, 2022

For me, I have found that the key display set to code 41 lights up when I press ' (40) instead of ` (41).

The key display set to code 40 lights up when I press \ (43) instead of ' (40).

Unfortunately pressing ` does not light up any key display at all (or if it does, I have absolutely no idea what key code it would correspond to).

Is there somewhere with a list of key code numbers for reference?

Edit: Fixed by running demo_hook.exe and checking the hexadecimal keycode for `, which for me turned out to be 125 for some reason. Swapped all the keycodes in the .json config file and it all works now.

@b02860de585071a2
Copy link
Author

For me, I have found that the key display set to code 41 lights up when I press ' (40) instead of ` (41).

Interesting, I never got any behavior like that even when testing everything I could.

Edit: Fixed by running demo_hook.exe and checking the hexadecimal keycode for `, which for me turned out to be 125 for some reason. Swapped all the keycodes in the .json config file and it all works now.

That's so bizarre, I tried the same thing and got no results out of it. Are you on US QWERTY layout?

@Gn9sis
Copy link

Gn9sis commented May 3, 2022

Yes, I'm on the US keyboard layout. I originally thought we had the same issue, but we probably had separate issues.

I asked around and it's not very common of an issue/symptom. In my case, it was easy enough to fix but I have no clue what your issue might be.

I would try a different keyboard and see if that changes anything.

@univrsal
Copy link
Owner

univrsal commented Dec 6, 2022

See #298 for further tracking

@univrsal univrsal closed this as completed Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants