We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.9.1
HW1
Universal
External adapter with multiple hardwired cord
BlueRetro (AliExpress)
Nintendo GameCube
HORI Wireless HORIPAD Pro Controller for Nintendo Switch
Controller is recognized as "Lic Pro Controller" so primary action button mapping is rotated.
Expected to be able to map buttons using web ui tool with actual face value for buttons.
In Debug was able to track it down to:
/BlueRetro/main/bluetooth/hidp/hidp.c
{"Lic Pro Controller", BT_SW, BT_SW_POWERA, BIT(BT_QUIRK_FACE_BTNS_ROTATE_RIGHT)},
Made adjustment to be:
{"Lic Pro Controller", BT_SW, BT_SW_POWERA, 0},
Recompiled and flashed firmware to board. This fixed the issue I was experiencing.
The text was updated successfully, but these errors were encountered:
Folowing.
Sorry, something went wrong.
No branches or pull requests
BlueRetro firmware version
1.9.1
BlueRetro firmware specification
HW1
BlueRetro firmware variant
Universal
BlueRetro hardware type
External adapter with multiple hardwired cord
Manufacturer
BlueRetro (AliExpress)
System used
Nintendo GameCube
Bluetooth controller brand & name
HORI Wireless HORIPAD Pro Controller for Nintendo Switch
What is problem? (only list ONE problem per report)
Controller is recognized as "Lic Pro Controller" so primary action button mapping is rotated.
What did you expect to happen?
Expected to be able to map buttons using web ui tool with actual face value for buttons.
Attach files like logs or Bluetooth traces here
In Debug was able to track it down to:
/BlueRetro/main/bluetooth/hidp/hidp.c
Made adjustment to be:
Recompiled and flashed firmware to board. This fixed the issue I was experiencing.
The text was updated successfully, but these errors were encountered: