-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
BlueRetro Dreamcast - 8bitdo Ultimate 2C Problem #1135
Comments
Same thing here. I understand the controller does not support x-input over bluetooth so the analog triggers aren't going to work anyway, but I'm a little confused why blueretro seems to be receiving all kinds of phantom inputs when nothing is pressed. I'm using the LaserBear BlueRetro GC V3 and the Ultimate 2C Wireless controller in bluetooth mode. |
Is it better in v25.01? |
Unfortunately no, same behavior of seemingly random rapid-fire button presses. Attaching a debug file where I start the console and connect the controller in question (I had to change the extension to .txt for Github to allow the upload, please change the extension back to .bin). |
@brettinman your trace is invalid, did you follow the instruction and enable debug mode? |
Ah sorry, I somehow missed that part. Try this one: |
@brettinman (you need to be logged into github for it to work) If it doesn't work take another debug trace with it. Thanks! |
Thank for the help debugging. Interestingly, on this test firmware it seems to be injecting fewer random presses, but is still pressing them and (seemingly) not responding to actual inputs. |
Your trace show that you are still running v25.01 firmware and not the v25.04-beta |
Yeah I actually just realized that, the first firmware update apparently didn't "take". So good news - it works great! I haven't done a full test yet, but no random button presses and inputs seem to work. I'll do a more thorough test and update this thread soon. |
Ok GC Controller Test shows all buttons are good, including analog triggers. I can't get rumble to work but I think that's expected; from what I can find, the Ultimate 2C only supports Dinput mode when switched to Bluetooth, and Dinput doesn't support rumble. Output settings: Thanks again for the help here, I'm glad these can be supported since it's a nice controller and there have been some great sales on them recently. |
There is a rumble report I can see. Can you make a debug trace while trying to trigger the rumble (press -/select should do) |
Sure, let's try these: With Accessories set to Rumble: br_debug_trace_8bitdoUltimate2C_LaserBearGamecube_rumble1.txt With Accessories set to None: br_debug_trace_8bitdoUltimate2C_LaserBearGamecube_rumble2.txt |
Can you try this one and take a debug trace again: Thanks! |
Hmm I've tried updating to that firmware a few times now and always get a disconnection at about 7%.
|
When it fail just close your Chrome tab and try again in a new one. It will eventually work. |
I think your connection issue are due to having debug mode enable while updating firmware. Turn debug mode off Sorry I haven't though of that yesterday. |
Ah, that did the trick for the OTA FW update. Does it matter what the Accessories field is set to when grabbing these logs for rumble troubleshooting? Accessories set to "None": br_debug_trace_8bitdoUltimate2C_LaserBearGamecube_rumble3.txt Accessories set to "Rumble": br_debug_trace_8bitdoUltimate2C_LaserBearGamecube_rumble4.txt |
leave it at rumble, so I guess that means it didn't work? |
Nope, no dice when pressing "-" or triggering the rumble in the controller test program. |
Actually scratch that, I'm not sure debug mode was re-enabled. Here's another with debug mode and Rumble selected: |
Ok I made a mistake in previous one. Hopefully this one will do: |
Thanks! Unfortunately still no rumble, debug here: |
Ok too bad I guess it doesn't work over BT They report a rumble report with ID 5 in their HID descriptor. That report doesn't exist in their LE attribute but there was another output report with ID 1 in the LE attribute. However writing to that yield a "Error Code: Invalid Attribute Value Length (0x0d)" As a last ditch efford you could try to connect it on your PC with BT, and launch Steam controller test: There a button to trigger rumble. |
No button in the Steam controller test for rumble when doing the test with this controller connected via bluetooth. The button does appear when connecting over 2.4Ghz USB dongle. There are a number of threads out there of people not getting rumble in bluetooth mode, but it's unclear whether that's because it's impossible or just that none of the common libraries have figured out how to interface with it. Anyway, thank you so much for the help getting the controller working! |
100% 8bitdo software issue. It's all there but it's not hook up. Thank for testing and providing traces! This helped a lot! |
Here a more complete set of builds with this fix until next official release: |
BlueRetro firmware version
24.10
BlueRetro firmware specification
HW1
BlueRetro firmware variant
System specific
BlueRetro hardware type
External adapter dongle (1 port only)
Manufacturer
8bitmods
System used
SEGA Dreamcast
Bluetooth controller brand & name
8bitdo Ultimate 2C
What is problem? (only list ONE problem per report)
The Ultimate 2C controller connects but behaves erratically, rapidly firing commands I haven't pressed. I have had the same thing happen with two different 2C controllers. The 8Bitdo Arcade stick however behaves completely normally.
What did you expect to happen?
I expected the controller to not send button presses by itself.
Attach files like logs or Bluetooth traces here
No response
The text was updated successfully, but these errors were encountered: