@mitu said in Joystick order and Bluetooth gamepad:

@pscotto1234 said in Joystick order and Bluetooth gamepad:

When I start a game with this configuration, DS4 is the first joystick and it's ok. The weird thing is that if I disconnect DS4,...

Are you disconnecting the controller during game play or you're starting the game after disconnecting the controller ?

I disconnect Joystick only when not in game. I tried to restart as well but had the same behaviour.

@nunna78 hi there. I must complète this Thread:

XpadNeo: Xbox-One Controller does not fully works on SteamLink. X and R1 Button are not recognized

Xboxdrv: Xbox-One Controller work perfectly on SteamLink.

So if you want to play SteamLink i'll recommand Xboxdrv instead of Xpadneo

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.

While waiting I installed Recall box to try if it works. It's same there.

However... I found old Saitek Pad (PS2700) and it works like a charm. I decided to try xBox Controller via USB and it works like a charm.

Trying to connect via Bluetooth does not work at all. Will try to ssh and play with BT then, maybe console will tell me something.
Since I can't pair my headphones also, I think it might not be pad problem, but bluetooth.

About SteamController. There is problem with mapping of d-pad. It recognizes only swipe in one or 2 directions. Like Analog Left and Analog Up. So its more like Analogue for emulator than D-Pad.
But I think i can pass on stemController if XBox and Saitek works. I'm a fan of D-Pad. Touchpad as D-Pad is not good on SteamController.

EmulationStation does not know (nor care) how the controller is connected, so there's nothing to configure there.

You can however pause the RA software during gameplay and resume it afterwards using the onstart/onend scripts for runcommand - see here.

Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Did you disable BT in the bootloader configuration file (config.txt) ? What 'lines of code' (commands) are you executing ?

@fretman yeah anything will do just to get the bluetooth ones sorted. These are all things you'll learn as progress as a Raspberry Pier

@yarongo said in Pi3B, Xbox Wireless Controller not connecting:

A few questions to @mitu :

Should I uninstall xpad driver first?

No, it's not needed.

Should I install xpadneo directly from Github and not via the menu?

You can try, but the menu installation pulls the latest release tag from the xpadneo Github repository anyway, so I don't think it will make a difference.

@erickwilson thank you for the advice. I am currently playing with a temporary keypad. Waiting for some of the retro keypads to come back in stock. Seems like there's a shortage on them right now.

This issue has been fixed with an RPI OS update for the Bluetooth packages, so the workaround is no longer necessary - an update of the packages/OS is enough.

You can update the packages as part of RetroPie's update menu or manually with

sudo apt update sudo apt upgrade

The bluez package version that fixes the issue - 5.50-1.2~deb10u2+rpt1.

@jhny0 I know that this topic is quite old, and at this point, I am doing necromancy, but what model dongle did you buy? I fought one, which thechnically works with linux machines, but the range... Well lets just say a short wired controller has better range.

The PS4 Dualshock controller should work without any additional driver installation - the ds4drv is an old and un-maintained driver and it shouldn't be used.
If you configured your controller in EmulationStation, you don't need to do any configuration in RetroArch. The configuration for RetroArch is automatically generated from EmulationStation - see https://retropie.org.uk/docs/Controller-Configuration/. You can check if your auto-configuration for RetroArch has been generated by looking into the \\retropie\configs\all\retroarch-joypads folder (over file shares). Do you have a .cfg file for your controller there ?

Aside, you should be using a proper power source for your Pi, a mobile phone charger is not enough for most cases, especially on a 3b+. Do you get the low voltage sign when you start a game ?

Try updating RetroPie and the OS/packages to the latest version and re-try the pairing via Bluetooth.

@mitu I updated when I saw your message here, 5 minutes before I posted my reply here. It took a while updating, but my controller doesn't work neither in my PC or raspberry :/

Try installing the xpadneo driver from RetroPie-Setup (see here on how to install things in RetroPie) and try re-pairing the controller again via Bluetooth.