@mitu I need you to unlock that recent post of mine about the splashscreen. I reposted on that topic because nobody was able to help me with my previous post and the one that you locked had more detail and pictures that might be able to be diagnosed by someone who actually knows how to fix my issue.

Perhaps this?

https://www.8bitdo.com/micro/

Can you switch the stick into XInput mode, instead of PS3 mode ?

Thanks. I'll try that when I can save up some money.

Also some other details. When I try to connect it to other devices like my phone or laptop, it also turns off by it's own, and what's more is that Windows 11 says that its a "Driver Error" when reconnecting to the controller.
Also when reconnecting with Android, there is also a pin requirement of "0000".
(Maybe my controller is just the Issue)

Also, Is there a way to run:

Bluetoothctl

and try to re-pair and connect when retropie Starts, Restarts, or Boot up?
Because this might solve my Issue.

@mitu My apologies for not reading through that read first post. Nevertheless the problem was exactly what you said. I made sure that everything on the back of those little controller boards was plugged in exactly the same on both sides now the only problem is the joystick orientation has to be flipped around because it is reading backwards should be good. Thank you for your help I appreciate it.

@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.

@lovemehate said in No matter what image i use on RP3+ controllers wont get detected:

is this the same one that comes with Raspberry pi imager ?

Yes, Raspberry Pi Imager downloads the same images.

Just to close the loop on this. I was unable to try the above solution as the controller had paired, but no security settings or configuration was allowed. When I tried to unpair the controller I couldn't. I assume I had messed up the settings trying fixes for this. I uninstalled retropie and reinstalled and it worked fine. Thanks for the help.

@standarsh14 said in RetroArch won't distinguish between two controllers:

It seems like either controller will work with one registered bluetooth connection - which confuses me because I thought that with separate Serials, only the one registered would work.

That's unexpected, the controllers should have different MAC addresses (they appear in the pairing dialog) so the OS would be able to tell them apart and some pairing info to be also stored on the device itself. Deleting the device from the list of paired Bluetooth devices in RetroPie should force the gamepad to be re-configured.

With both devices connected, can you run

cat /proc/bus/input/devices

and post the output ?

You can also test with jstest if the controllers are acting separately. Run:

jstest /dev/input/js0

and press the buttons on 1st, then on the 2nd controller. Only one controller should yield any events/output on the test.

@mitu Ummmmmm.... maybe! Hahahahaa. Skimming through, looks like what I need, I'll have to try it tomorrow.

THANKS!

I'll update this post as needed. I'm certain it will be needed... lol.

@mitu

I read this as they are looking to run the desktop over an SSH tunnel from a (headless) remote linux fileserver, hence my concern about latency. If this is the case, they would need to start the X environment manually, or maybe you could setup some checks to examine ${SSH_ENV} within .profile to try an autostart.

@t-men

Another check is to ensure the user running ES, is in the correct group to access js events. Usually input

crw-rw-r--+ 1 root input 13, 0 Oct 3 19:05 /dev/input/js0

@iandaemon said in Do 3rd party joy cons work with Retropie ?:

They're just bluetooth controllers, right?

Yes.
If the wireless signal is exactly the same as the official Joy Cons,
then it should work, I suppose.
But no way to know for sure, unless someone has tried it before.

@ericsnis said in Remapping buttons for runcommand.sh:

Is there a way to remap the buttons used for runcommand without messing up the mapping for games?

runcommand will use the RetroArch configuration file of the gamepad. If you didn't generate one - it's automatically done when you configure the input in EmulationStation - it doesn't which buttons are A/B to enable them in the launch menu.
Since you copied the ES configuration for input, and didn't run the input mapping dialogue, the RetroArch configuration file hasn't been generated - hence the missing mapping in the launch menu of Runcommand.

@mitu Thanks that worked perfectly!

@mitu Good call! I'm not sure how much power it's pulling, but setting over_voltage to 2 definitely makes it last longer, though not completely staying on all the time. Trying with setting it to 3 right now and that seems to be going strong!

@mitu Ha ha, hard to believe we are in April and I'm still trying to connect the XB1S controller and get games working in Retropie!

I installed xpadneo and have managed to pair the controller, but 2 issues remain.

Cannot select the Xbox home button when configuring the controller. I wanted to select it as the 'hotkey'. Even if I choose 'Yes' at the end of the setup when asked if you want 'select' as the hotkey, Start and Select wont exit out of the games.

After starting a game in retropie you are taken to a blue menu screen with various options (choose emulator, launch ect.) Left stick on the controller is the only way to navigate and to move down I have to kind of move it left and down (SW on the compass as an example) and pressing A does nothing unless I keep pressing it over and over.
Two more things - The cursor underneath the 'OK' in the blue menu screen is flashing really fast (it stops if I turn off the controller and if I plug in a wired controller it behaves normally) + if I am in a blue menu screen that has 'OK' and 'Cancel' down the bottom it continuously swaps between them.
So the controller has a mind of it's own. I can also confirm that the controller 100% works, I have tried it on the PC and Xbox.

Maybe I should erase the SD card and start from scratch? Although I'm not sure how much more time and effort I can invest in getting this working......

@mitu So sorry for the delay...busy week and didn't have much time to play. Just tried my ps3 controller and yep, you're right it's simply the controller itself.

@louiehummv Thank you so much for this. Still works today! Was having the same issue with my 8bitdo SNES30 controller. Interesting considering said controller does not have any analog sticks…