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

Raise appears incompatible with PS4 / PS5 #159

Open
jordaaash opened this issue Jan 13, 2021 · 2 comments
Open

Raise appears incompatible with PS4 / PS5 #159

jordaaash opened this issue Jan 13, 2021 · 2 comments
Labels
bug Something isn't working FW For issues with the keyboard's behavior

Comments

@jordaaash
Copy link

Describe the bug
Raise doesn't work when plugged into a PS4, PS4 Pro, or PS5. This occurs with or without the use of a powered USB hub that has been tested using a desktop computer.

To Reproduce

  1. Plug the Raise into the front or back USB ports of a PS4, PS4 Pro, or PS5. The Raise is recognized as an external keyboard by the console. RBG for the Raise and Neuron function correctly. Only keys defined in Bazecor as layer swap, one shot layer, and some ctrl/alt/cmd keys cause responses.
  2. Enter the Messages screen and attempt to type a message using the letter and number keys. There will be no input or response from the console. The enter key does not respond. The capslock key doesn't change color when toggled.

Expected behavior
The keyboard works like a regular keyboard.

Desktop (please complete the following information):

  • OS: Mac OS 10.15.5
  • Bazecor Version: 0.2.6

Additional context
The problem appears to be related to lack of NKRO support on the console.

https://www.reddit.com/r/HyperX/comments/a4ggot/hyperx_alloy_fps_pro_not_working_with_ps4/ebipta6/

Corsair keyboards have a similar mechanism that is used to work on consoles:

https://help.corsair.com/hc/en-us/articles/360053198052-How-to-Use-a-CORSAIR-keyboard-to-enter-BIOS-mode

From #157, which may be related:

It's a 6KRO vs NKRO issue. Most KVM switches only recognize 6KRO, but do not do what the USB spec would require them to do: ask the keyboard to go 6KRO. They just assume it will be. There's no reliable way to automatically switch to 6KRO, unless the host (in this case, the KVM) asks us to do so.

With the next firmware update, there will be the 6KRO<->NKRO toggle, which will help with this issue. Press the combo, the keyboard goes 6KRO, KVM switch will recognize it, all's well!

Is there any way to configure the Raise to use 6KRO so I can test compatibility with the PS4? I can follow the instructions to build custom firmware if needed.

@jordaaash jordaaash added the bug Something isn't working label Jan 13, 2021
@jordaaash
Copy link
Author

Also found this thread: https://www.reddit.com/r/DygmaLab/comments/ifq87h/problems_with_your_raise_tell_us_here_and_well/g6yn0gm/

It seems like this is an understood issue, but if there's any workaround I'd love to know. I just got my Raise and I love using it with my computer, but a major reason I got it is for gaming and I do most of that on console.

@GazHank
Copy link

GazHank commented May 29, 2021

I believe this is tied to the same root cause as #157 (a fix for that one should fix this too)

@alexpargon alexpargon added the FW For issues with the keyboard's behavior label Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working FW For issues with the keyboard's behavior
Projects
None yet
Development

No branches or pull requests

3 participants