@Zentrifuge

Found solution for everything - Batocera - Works like a charm out of the box - Even with my N30 Pro + Bluetooth from internal device.

Thank you

@mitu Hi, and thanks for your reply.

Apologies for having not provided feedback sooner, not normally my habit to be ill-mannered. I had to purchase a SATA to USB adapter so I could boot from my SSD with the pi removed from the case, then we had a family wedding ...

Anyway, you're absolutely right. With the case taken out of the equation, and the SN30 Pro connected directly to a USB port on the pi, ReDream launches fine. So, as you said, must be an issue with the USB port on the NESPi4 case.

As I say, I do have a different controller, also from 8BitDo, which doesn't experience the same issue. Possibly because that model has upgradeable firmware? So I'll most likely buy another one of those, one which colour matches the NESPi4.

Anyway, thanks again for the solution.

Ok, thank you for letting me know. May be difficult to acquire another cm4, but I will check rpilocater daily from now on for a wireless version.

@MetalGamerFil
Please supply the information requested in
https://retropie.org.uk/forum/topic/3/read-this-first

In which mode are you using the controller?

I had some trouble configuring mine with a couple of buttons when it was in X-input mode (X + Start when turning on the controller). Some of buttons were showing up as analog axes instead of button presses. I solved it by changing the mode to either Switch mode (Y + Start) or D-input (B + Start) and re-configuring the controller.

I think part of the problem is EmulationStation doesn't want you to use an Axis when configuring certain buttons. Not sure if this could be fixed in the auto configuration. I believe you could manually edit the controller config to get around that though.

I have one and it's working fine with the latest RetroPie version.
What's the issue exactly ?

@AlphaBetaPie this is a common problem. there was a user who did find a way to do something about it

LINK

i have not tryed this, so i cant say if this still works or any more, but its something

Thanks for the info all. With a combination of core remapping and removing some lines I didn't realize 8BitDo stuck into the autoconfig by default, I have removed access to 99% of these menus. Still having some issues closing off Mame's menus, but that will be another thread for another day. Thanks as always!

Glad you got it sorted out and thanks for adding the solution to the topic.

Hold SELECT + DPAD DOWN = Switch the positions of the A-B and X-Y keys

It would be nice if 8BitDo would include this info in the Modkit manual, they are mentioning _ SELECT + DPAD DOWN_ as a way to send the Home button only when the modkit is paired in Switch mode.

I'll mark this topic as solved.

@bradbradbrad hmmm, I will have to procure that UB400 and experiment! Thanks for the tip!

@mitu thanks for the reply, there does not seems to have any firmware update for the tg16 controller yet...

The dongle seems to shutdown (let blink) like the dongle for my Arcade stick. I will try to see if I can see connect/disconnect in the Linux log for both and see if there is a difference.

@x_wav This means the button is not registering, so it can't be used.

@digriz Thanks for the tip! You're right, the instructions were slightly vague for the different pairing options. My nephew is super patient so I know it's not really going to bother him. For me, I KNOW it could be better! LOL

@mfraz74 Looks like Debian doesn't package the 8bitdo-tool or it's included in a plugin, but I haven't used fwupd so far, so I can't offer more details. Try using the macOS updater to install the latest (4.20 I think) version of the firmware.

Please add more details about your setup, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Have you tried starting the controllers after the Pi is started (in case you're not doing that already) ?

@mitu and to any future readers - I fixed it!

After much searching, I found this link https://github.com/goodtft/LCD-show/issues/278 for an issue with an LCD display I tried to use years ago. Apparently, it updated my /boot/cmdline.txt file to put ttyAMA0 in my console, instead of the default serial0. Swapping it back to console=serial0,115200 and rebooting, and now bluetooth works again!

Here is a potential solution

From emulationstation, enter RetroPie configuration Then RetroArch In the Main Menu of RetroArch, select Settings -> Input

From there, go down to Port 1 Controls and update the following

Set Device Type to RetroPad with Analog Set Device index to 8BitDo SN30 Pro+

I was able to get two controller working with this work around.

Versions

Program Version / Hash emulationstation 2.9.6RP retroarch-setup.sh b3acb001fcf6276a2ef5c5b4caca135b399797f8 retroarch 8373ac6

In hindsight having a keyboard plugged in may have been problematic in regards to it defaulting to the primary controller.

@barbudreadmon , thanks for the heads up. Will keep that suggestion in mind in case of any issues.

@benmclean

The Raspberry PI 4B with 8 GB of RAM. The performance gain is small for gaming because RAM is usually not the bottleneck

Eh? The performance gain past 2GB is zero. Retropie uses around 1GB with swap and all. The extra ram might help with installing emulators from source or if you want to use it as a desktop someday.

You need a compatible power adapter and lots of companies make them.

I only recommend the official psu due to reliability. They are $8US so there shouldn't be a reason to get a 3rd party psu that no one knows how reliable they are.

If you're going with a plain pi4, for a case, I recommend the argon one v2 if you don't want that nespi. It has a fan and converts the microhdmi ports into normal sized ones.