This repository was archived by the owner on Dec 14, 2025. It is now read-only.
Replies: 2 comments 2 replies
-
|
If you use the default label in the mapping config it's RT is called "GP: RT; KB: L Shift" leave the source to that but change the destination to the button you want it to be. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Both of your debug trace are empty. Can you try again and make sure you follow every step in the doc: |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment





Uh oh!
There was an error while loading. Please reload this page.
-
Hello Everyone:
I've got a "universal" arcade stick, which can connect to Android, PC and Switch without issues, all buttons work; but for some reason, with BlueRetro i can't map a particular button.
let me elaborate:
I decided to create a blueretro dongle for my PSone ( as a start point), got Firmware 25.1 HW1 for PSX / PS2, it connects to the console through the pins in the controller ports.
This seem to work, as i can control both players, with the buttons i've managed to map, except for the button that i'm mising.
While looking at github and forum messages, i noticed similar issue messages where it was mentioned that there is the V1.3 BlueRetro_pad_test.bin, and i have used it to know what buttons are seen on Blueretro when pressed on the arcade stick.
Below I'm trying to represent the buttons as detected by BlueRetro_pad_test.bin firmware
The button, I'm dealing with is show as "RT" which highlights in green when pressed
see screenshot
DL O DR BL BD LT LT "register" (when pressed it shows 7FFF)
DD O O O O
Note, there is other similar named button (RT), which i called "register" above as it seems they are detected as trigger or stick, and it is showing an hexadecimal value when pressed, on the RT column in the left (refer to screenshot).
Now; the problem is that i couldn't find how to Map RT button in 25.1 Firmware, i tested Most (if not all) available labels from source, all GP and KB labels, and failed to find it.
I'm also sharing the 25.1 Firmware, Debug trace, which has my latest mapping, that detects all buttons (and gets them mapped to PSX buttons), except for this problematic one, while it is being pressed.
br_debug_trace (4).zip
Any insights would be appreciated.
Thanks for this awesome project.
Beta Was this translation helpful? Give feedback.
All reactions