Can you run the following commands and post the output here in the topic ? If xpad is not recognizing the gamepad, we can try and force the driver to load is we know the device's Vendor and Product Ids

lsusb cat /proc/bus/input/devices

@BOne72 I am happy that you have fixed your previous problem...

I am not sure with the audio as I usually connect audio from my monitor as you know audio is also transmitted with video through HDMI cable.

I think you must do some changes in your settings...

Try checking Retopi-setup or raspberrypi-setup....

Decided to try Recalbox and it was so much easier to setup. Controller worked straight away, didn't have to program anything. Super Mario All Stars works flawlessly with no delay. I'm very happy now :)

@mitu

No luck. Bought two cables. Same thing : /

p.s. I think the full update broke something because now I can't play a game with the controller wired haha. It says xbox controller not configured, a message in the lower left screen. But I can use it in the emulator carousel GUI. Everywhere except a game.

As much as I want to play wireless, it's more my curiosity and desire to want to fix a bug and understand why the pi zero is fussy about this and not the pi 4.

If it has a dongle, then it's not a Bluetooth contrller. If it's not working with a PC, then the dongle/controller may be fake or defective. Complain to the vendor and ask for a replacement/RMA.

@mitu thanks, I'll try it!

@abj Will look thru these again, thank you

@dandaman Hm, I wonder if you haven't activated something like Turbo mode in RetroArch for P2.

@Melchior said in Pi5 - SNES - 8bitdo SNES30 - Down & Diagonals triggering State Selection and Resetting Game:

Any idea where I might have gone wrong? 😅

Did you delete any configuration file(s) hoping you'll 'reset' the mapping ?

Sounds like you've deleted es_input.cfg from EmulationStation's configuration folder, in which case follow the steps in the docs to reset your inputs and re-configure your gamepad once again.

@barleyguy
For some reason, it works now!
It must've been something I did before that fixed it, and i didn't test it correctly.
Thanks for the help y'all!!

Do you have any input remapping set-up ? Does it happen only on GBA games ?
Please provide the rest of the info asked in https://retropie.org.uk/forum/topic/3/read-this-first (emulator, image used for installation, etc.)

Do you have 2 dongles - one for each controller - or are you trying to get both controllers working with the same USB dongle ? I don't think the latter may be supported.

@jernserval said in More 8BitDo Pro 2 Controller Weirdness:

It appears there's some kind of naming conflict or problem when the 8BitDo tries to "spoof" as an XBox One controller?

No, I don't think so - conflicting with what ?

Xpadneo refers to configuration in it's docs, but there was no configuration after RetroPie-Setup install?

Configuration is optional, RetroPie doesn't add any, but you can add it if you'd like.

hid_xpadneo: loading out-of-tree module taints kernel. - Does this mean I need to install the headers referenced in the xpadneo documentation? Was it not autoinstalled by RetroPie-Setup?

No, that means what it says - it's an out-of-tree module, external to the Linux kernel. Kernel headers are already installed, otherwise the module wouldn't have compiled.

Now in retroarch its saying "8BitDo Controller not configured" why would it say explicitly "not configured"?

Because it's not configured ? This means there was not configuration profile found for the controller.

What is the way forward to get the most reliable experience with X-Input across retroarch and other emulators?

You haven't mentioned the issues you have with other emulators, but for RetroArch it's enough to configure the controller in EmulationStation in order to generate the configuration for it.

@ExarKunIv I attempted this unsuccessfully but will give it another shot.

The configs in openbor are not user readable / not in any way like a retroarch.cfg.

And like I referenced above, my openbor saves are for some reason saving to: /opt/retropie/configs/all/emulationstation/Saves

@mitu I see, so use a USB extension cable for the dongle.... I was hoping to keep this as aesthetically pleasing as possible. Are theere any good dongles that have better range?

@mitu Whew. It's getting weird now.

I just built the latest version of SDL2 from github.

cmake sees SDL2 as 2.29.0 now instead of the previous 2.0.10.

So then I rebuilt Emulation Station.

The preinstalled Emulation Station was v2.11.2rp. The one I've built identifies as 2.12.0rp-dev.

The good news:

Emulation Station now recognizes my L2/R2 triggers!

The weird news:

When I launch retroarch emulators, they do not recognize my L2/R2 trigger presses. While the bluetooth dialog still reports my controller name as "8Bitdo SN30 Pro" when I pair and connect it, this newly-built version of Emulation Station reports it as "Xbox 360 Controller".

@qstyler said in Cannot setup 8bitdo bluetooth adapter on Pi 4:

Hi! I'm trying to set up an 8BitDo BlueTooth adapter but it doesn't seem to work for some reason.

First of all, I disabled Bluetooth in the config.txt file by adding dtoverlay=disable-bt

Then I plug my dongle and try to do bluetoothctl, but it hangs forever.

To fix the issue I tried to run the following:

$ sudo systemctl enable bluetooth Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable bluetooth $ sudo systemctl start bluetooth

This command gives no output...

And this is a status of the bluetooth:

$ sudo systemctl status bluetooth * bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8) Apr 09 11:24:42 retropie systemd[1]: Condition check resulted in Bluetooth service being skipped.

If I try to get a list of USB devices, I can see my dongle, but without a name (device 004):

$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2dc8:3107 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here's the full dmesg output, maybe this will help.
https://pastecode.io/s/ejohjh6u

I'm using Raspberry Pi 4 Model B Rev 1.2

There are no other USB devices connected to my Raspberry.

And I'm using a default usb-c power adapter that came in a box.

The 8bitdo bluetooth adapter is not actually a bluetooth adapter in the traditional sense. When you plug it in, it is treated as a USB controller, not a bluetooth radio. To connect a controller to the receiver, press the pairing button on the adapter, then press the pairing button on your controller. When both lights are solid, the connection is made. It also means you can only have one controller paired to the adapter at a time, and need multiple adapters if you want to pair multiple controllers. Changing bluetooth settings in the OS will have no effect on the adapter.

@trecuu said in 8bitdo Ultimate Bluetooth Controller Compatibility:

@mitu
Managed to fix it by downloading a beta firmware for the receiver to be able to change to D-Input.
It does not work while on X-Input, only on D-Input.

Thx for the help.

Hi @trecuu I’m in the same situation as you but I’m not able to find the beta firmware you mentioned. 8bitdo Support informed me that it was no longer available. What version number is the beta? Any chance you still have a copy of the beta firmware? The latest controller firmware is V1.03 and V1.02 for the usb dongle receiver. I appreciate your time and your help,
Best Regards