@alareqi you were rude, hence my rebuttal. I stand by what I said.

It was easier than I expected, thanks @ferdnand

@obsidianspider
you may have some issues in connecting and configuring the buttons of your bluetooth controllers. But once it's done, it's really easy to switch between the available controllers in RetroArch.

Trying to ask your question "how does the system choose which controller to use?" (assuming system = RetroArch). Like I said in my first response, RetroArch define some indexes for the controllers. The default is player1 = index 0, player2 = index 1, and so on (I didn't make it clear in my first post). But you can change it in retroarch.cfg. What the RetroPie-Setup config editor and my joystick-selection tool do is just this: change these options in retroarch.cfg.

BTW: the options related to what we are talking about here are input_player1_joypad_index, input_player2_joypad_index, etc...

@edmaul69 it worked! Thanks!!!

Just arrived to RetroPie and still trying to configure my devices, after reading full topic here are my two cents:

unistalled PS3 Driver (clone) Paired Sony official PS3 bluetooth controller successfully Installed PS3 Driver (clone) Connect PS3 Clone Gamepad on USB then disconnect Push PS button to connect Gamepad. All done :)

At this point two devices works properly. I can change from retorpie to kodi and back again and all its fine. Just played some games on joypad, exit retropie onto kodi, navigate using keyboard.. all fine !

But... after reboot, bluetooth keyboard can't be paired again. I need to start over again from point 1.

the question is: It's possible on boot process, disable sixaxis while normal stack connects to bluetooth keyboard (or other devices) and after some time (maybe 1 minute) reenable sixaxis again?
How is started bluetooth device during boot? and where are the scripts?

Any advice are welcome if someone has tryed something like this.

Obocaman

@mattrixk
I have the C120 Pro remote, which might not have the same id numbers.

I found this post that helped solve the same issue as yours, where it would register as player 1 and the other controls were 2+.
From the post: "The following code deactivates the joystick part."
https://ubuntuforums.org/showthread.php?t=2283297

Use this to find the usb interface/vendor/model id numbers:

udevadm info -q all -n /dev/input/js0 | grep -Ei '(ID_USB_INTERFACE_NUM|ID_VENDOR_ID|ID_MODEL_ID)'

Create rule using:

sudo nano /etc/udev/rules.d/99-persistent-joystick.rules

and add the following in (replacing bInterfaceNumber, idVendor and idProduct with yours):

SUBSYSTEM=="usb", ATTR{bInterfaceNumber}=="03", ATTRS{idVendor}=="0c45", ATTRS{idProduct}=="3451", RUN+="/bin/sh -c '/bin/echo -n %k >/sys${DEVPATH}/driver/unbind'"

Reboot, and you should see that js0 is no longer shown by using

ls -l /dev/input/

and that controller 1 shows up as controller 1 when activated.

This may not be the proper way to do things, but the best I've found so far using it with PS3 controllers. If there's a better way, I'd be open to hearing it.

Hope this helps.

HI there

I am having exactly the same problems. I've trawled the internet with no luck... did you manage to fix your problem in the end? I'd love to know how if you did!

Thanks...

No experience with the GameStick unfortunately, but in relation to this:

@Dopy25 said in Gamestick (bluetooth) controller:

I also attempted to connect a PS3 controller, but after plugging it in to charge and running the setup for it, the original controller does not light up at all, I am hoping this is unrelated.

You cannot currently use the PS3 controller drivers and the normal bluetooth stack at the same time, so that may be why the GameStick no longer connects after trying the PS3 controller.

@BuZz said in Retropie 3.8 Bluetooth Configure Issue:

you cant use ps3controllers and the built in bluetooth stack at the same time currently. Known limitation of the ps3 pairing software.

I had the following error that occurs if you configure a PS3 controller before attempting to configure an 8bitdo gamepad:

Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/home/osmc/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 118, in pair_reply dev_connect(dev_path) File "/home/osmc/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 38, in dev_connect dev.Connect() File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in call return self._proxy_method(*args, **keywords) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in call **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.NotAvailable: Operation currently not available

The solution is to remove the PS3 controller driver via the retropie_setup.sh script ([Manage packages] -> [driver]->[ps3controller]->[uninstall/remove]).

Afterward, manually remove all packages/dependencies related to it. Basically any package mentioned in the PS3 controller setup guide:

https://github.com/retropie/retropie-setup/wiki/Setting-up-a-PS3-controller

sudo apt-get --purge remove sixad
sudo apt-get --purge remove sixpair
sudo apt-get --purge remove bluetooth
sudo apt-get --purge remove blueman
sudo apt-get --purge remove bluez-hcidump
sudo apt-get --purge remove checkinstall
sudo apt-get --purge remove libusb-dev
sudo apt-get --purge remove libbluetooth-dev
sudo apt-get --purge remove joystick
sudo apt-get --purge remove pkg-config
sudo apt-get --purge remove python-gobject
sudo apt-get --purge remove bluez-utils
sudo apt-get --purge remove pi-bluetooth

Then,

sudo apt-get install pi-bluetooth

Then follow the normal 8bitdo setup guide:
https://github.com/retropie/retropie-setup/wiki/Setting-up-an-8bitdo-Bluetooth-controller

@deadpool There's this section in the retroarch.cfg

# The maximum rate at which content will be run when using fast forward. (E.g. 5.0 for 60 fps content => 300 fps cap). # RetroArch will go to sleep to ensure that the maximum rate will not be exceeded. # Do not rely on this cap to be perfectly accurate. # If this is set at 0, then fastforward ratio is unlimited (no FPS cap) fastforward_ratio = 0

I don't know if this is a very healthy setting to be using, or how much it even effectively speeds things up. There doesn't seem to be a way to get the really zippy frameskipping fastforward that you find with a lot of pc emulators. At least, I haven't come across it yet.

@cdoss Start a new topic (and read this first https://retropie.org.uk/forum/topic/3/read-this-first)