How did it go?

I have an xbox360 wireless controller with the Windows USB WiFi lead, so I can use this in Retropie or is it better to use one with the USB lead attached?

You can probably skip step 2. Shutdown stops the service as well. But yeah, the built in PS3 pairing system doesn’t really seem to work.

It appears as if the service doesn’t get added to the boot process automatically unless the PS3 pairing script finishes successfully (which I’ve never gotten it to do). So once you install the PS3 drivers, then plug in the controller and run..

sudo /opt/retropie/supplementary/ps3controller/sixpair

and get the two MAC addresses to match, confirming the top MAC address (the controller) matches the bottom MAC address (your Bluetooth Dongle), you can then go ahead and add the sixad daemon to the startup sequence.

sudo sixad --boot-yes

Unplug the USB cable, give the Pi a reboot, and it should sync up after it boots up when you hit the PS button.

[quote=96295]Tried everything from the thread. Nothing helps. Uses Floobs retroarch.cfg, USBGamepad.cfg.

I used than my old controller and it’s working fine with it. MegaWorldUSBGameControllers.cfg is used fine in every emulator and every button is working as intended.

Help?
[/quote]

Can you confirm you have deleted all files from the retroarch config path?
(Keep this one MegaWorldUSBGameControllers.cfg)

Tried everything from the thread. Nothing helps. Uses Floobs retroarch.cfg, USBGamepad.cfg.

I used than my old controller and it’s working fine with it. MegaWorldUSBGameControllers.cfg is used fine in every emulator and every button is working as intended.

Help?

Its really personal preference. If you have your pi overclocked and leave it running all the time it may decrease its lifetime, you can also look into extra hardware like the mausberry switch or the control block and incorporate an on and off button which will preserve the life of your microusb port from being handled so often. Sometimes I’ll leave it on for a few days other times I’ll unplug it. I have 3 or 4 raspberry pi’s I use semi frequently and I’ve had them for about 6 months and have never had any issue with any of them.

I used a clean USB…. as it needs to be formated correctly.
This is a good guide..
http://electricgardener.net/2014/04/03/retropie-moving-games-usb-stick/

I have a Pi 2 running retropie 2.6. I have limited space on my sd card so I was attempting to put everything on a separate USB drive. As I put the roms onto my usb drive, I tried to copy the folder tree on the pi so changing es_systems.cfg would be easy.
Once I inserted the USB and went to change the config file, it instead copied 1/3 of the files from the USB to the sd card. Any idea how to disable that feature?

Where you got your ROMs is your prerogative – links just can’t be posted here to preserve the integrity of the retropie project. The issue you are having is most likely with the rom transfer rather than the ROMs. If you are using retropie 3.0 you’ll first need to create a folder on your USB drive called retropie plug it into your pi, wait til it finishes blinking and then pull it back out, place your ROMs in their respective folders that were created, and then plug it back into your pi, wait for it to finish blinking then reboot your pi or restart emulationstation. If that isn’t working you can try re-enabling the usbromservice from the setup script and then try again. See here for methods on transferring ROMs: https://github.com/retropie/RetroPie-Setup/wiki/How-to-get-ROMs-on-the-SD-card the wiki also shows which file types are accepted for each emulator.

If you have your ROMs transferred and they show up in emulationstation and still aren’t working either you’re lacking a bios or have a bad source of ROMs.

@ feederchain Once again you are a hero. You fixed that damn mess of a USB interface! Indebted to you mate!

Will give this Kernal a shot. I’ll also try justest. I used evtest earlier, is that the same thing? How to you tell what model Xin-Mo you have. Mine has no markings on it and it wasn’t identified as a Xin-Mo in the evtest detection. Was listed as something like USB Controller Adaptor…

I’ve tried RecalBox lately. The PS3 controller works like a charm with it. It’s a very nice approach, but the system is kind of close, you can’t modify much like in the retropie distro, so I came back to it.
When you connect a PS3 controller with RecalBox you only have to wait about 5secs and disconnect the usb cable. After that you are able to connect the controller with ease every time.

I have the same problem with the same controller.
I have tried deleting USBGamepad.cfg and doing the retropie_setup.sh script. It does work in other emulators, but not on SNES games..

USBGamepad.cfg:
input_device = “USB Gamepad ”
input_driver = “udev”
input_b_btn = “2”
input_y_btn = “3”
input_select_btn = “8”
input_start_btn = “9”
input_up_axis = “-1”
input_down_axis = “+1”
input_left_axis = “-0”
input_right_axis = “+0”
input_a_btn = “1”
input_x_btn = “0”
input_l_btn = “4”
input_r_btn = “5”
input_enable_hotkey_btn = “8”
input_exit_emulator_btn = “9”
input_menu_toggle_btn = “0”
input_load_state_btn = “4”
input_save_state_btn = “5”
input_reset_btn = “2”
input_state_slot_increase_axis = “+0”
input_state_slot_decrease_axis = “-0”

The auto configs work by matching the “iProduct” value to the autoconfig file (I think!)

You can see it by typing “sudo lsusb -v”
Mine is
iProduct 2 USB,2-axis 8-button gamepad

This maps to:
input_device = “USB,2-axis 8-button gamepad ”

in my file:
/opt/retropie/emulators/retroarch/configs/USB_2-axis_8-button_gamepad.cfg

As you say, you would want to avoid editing retroarch.cfg for controller info if you can help it.

Which version of retropie are you using? You’ll need to run the controller that doesn’t work through retroarch-joyconfig (if youre using retropie 3.0 it is an option in the retropie menu) and it will create an autoconfig file that should work with retroarch emulators. There will be some separate configurations that might need to be done manually for some emulators but retroarch covers for most of them.
See this page:
https://github.com/retropie/RetroPie-Setup/wiki/RetroArch-Configuration

And this video:

You can type lsusb and it will give you a hexadecimal code for the product Id and vendor Id http://www.linuxnix.com/2013/05/find-usb-device-details-in-linuxunix-using-lsusb-command.html

Retroarch creates a configuration file based off of the lsusb identification. Some people have added their configuration files to the retroarch source code here:
https://github.com/libretro/retroarch-joypad-autoconfig/tree/master/udev

When you run retroarch joyconfig it will create a gamepad.cfg file in
opt/retropie/emulators/retroarch/configs/yourgamepad.cfg and as you’ll see all the aforementioned configs are there plus your newly created gamepad.cfg file. I’m sure there is a setting somewhere related to autoenable that remembers your gamepad.cfg, otherwise you can override those associations by manually editing the retroarch.cfg files for each or all emulators in /opt/retropie/configs I don’t know everything but hopefully that will give you an idea.