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

No support for generic BT gamepad/joystick? #1039

Open
fade0ff opened this issue Jul 19, 2024 · 0 comments
Open

No support for generic BT gamepad/joystick? #1039

fade0ff opened this issue Jul 19, 2024 · 0 comments

Comments

@fade0ff
Copy link

fade0ff commented Jul 19, 2024

BlueRetro firmware version

24.04

BlueRetro firmware specification

HW1

BlueRetro firmware variant

System specific

BlueRetro hardware type

External adapter dongle (1 port only)

Manufacturer

Retroscaler

System used

SNK NeoGeo AES

Bluetooth controller brand & name

Roving Networks RN42

What is problem? (only list ONE problem per report)

The RN42 is a serially controlled BT device which can be configured as BT joystick, gamepad, keyboard or mouse. I used it in several joysticks, gamepads and the like and they work perfectly well under Windows or Android.
When I pair such a joystick with my BlueRetro, the pairing/connection seems to successful, but neither directions nor buttons do anything.
Since the HID descriptor and BT stack are handled by the RN42, all I can do (apart from selecting device type and name) is to fill the predefined control data:
Data sent

The arcade stick in question has 10 buttons, so I'm using 10 of the 16 bits for buttons. Still, not a single one is working.
I tried the joystick and gamepad mode of the RN42. Both behave identical under Windows (no problems) and the BlueRetro (obviously paired/connected, but nothing happens).
I tried to mess around with the web based configuration tool, but didn't achieve anything there. Actually, since there is no "generic gamepad/joystick" selection for the source side and no simple labels as "button 0,1,2,3,4,...", I didn't really know what to select there. I still configured everything somewhat plausible as one of the 6 buttons, but again, I couldn't get any button reaction.

What did you expect to happen?

I would have expected that generic BT joysticks/gamepads with X/Y direction and 1..16 buttons would be directly supported and that you could select something like "button0, button1" as source as this is how buttons are handled in a HID report. I.e. they just have number/position in a bit field.

Attach files like logs or Bluetooth traces here

No response

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

1 participant