Cool project! I started something like it a few years ago, but didn’t have a raspberry pi at the time.

For the sake of portability (and because I haven’t mucked around with the GPIO pins on the pi yet), I would wire it up to another controller with a USB on it. Something like this, though I can’t confirm its compatibility with the pi: http://www.diyarcade.com/usb-arcade-control-encoder

That way, if you get frustrated or bored with using the raspberry pi, you can just plug the USB into another machine without having to completely rewire. From there it would just be a matter of plugging it in and configuring your emulators to recognise the buttons.

I ended up wiring my arcade buttons up to the PCB of an old wired Xbox 360 controller as an obsession with street fighter 4 took hold. This is a pain in the arse, and I would not wish it upon anyone.

There may have been some changes in the file structure from when those videos were made. What version of Raspberry Pi are you using? B+ or Model 2? Did you install from source or are you using the 2.5 SD image? Which USB controller are you using (SNES ibuffalo… n64?) Specifying the details of your hardware and software can help identify the issue.

Ok I can confirm that you can get both controller working MANUALLY by doing this:

press PS button on the first controller and wait until its assigned P1.

run:

sudo sixad –stop
sudo sixad –start

and when it tells you to press the PS button press the PS button on controller 2, I had this working but by no means is this a solution.

I imaged my SD card with the image I had that had the controllers working. They act the same way, which leads me to believe when we ran raspi-update it updated some firmware which is persistent no matter what version of RetroPie is used.

I am using a asus USB-BT211 dongle

thanks!

That audio noise is typical for the pi. A lot of places suggest replacing the built in analogue out with a cheapo usb sound card off ebay for around $2-5.

Through some searching, I found the updated information for the wireless ps3 controller setup in this site. The new 2.4+ directions specifically state you can use the script within the retropie_setup.sh script to install the driver… they will fail, but you can run a couple things manually and voila.

for me, this does not survive a reboot. no matter what. sixpair only hammers up a js device when usb connected. There’s no ps3 controller vibration when linked, and the one time it did work, there was only one controller allowed. as soon as i connected the second one, the first went off the air.

The issue I am having now is that since the new script was built, new auto-configs have been added and I need to basically send those packing and go back to the 2.3 way of doing it, with downloading source, patching running and pairing etc etc.. I can go through all this work, but the problem lies in that the exit buttons are not taking either when i manually setup the controllers with my own 2.3 version predefined configs..

i had this running sweet as honey on 2.3 but went to the beta as the RPI2 showed up and it seems this version is the necessary one for RPI2.

Which are the predefined config files, and can I move/remove them and have the emulators go back to the previous configs?

Hi everyone.

I’ve done something really wrong, I’m completely new to this so go easy one me and please forgive me if I’ve posted in the wrong section.

I’ll run through what I did yesterday and if someone would be kind enough to tell me what I did wrong I would be very grateful.

So I bought a 32GB Micro SD card along with one of those USB adapters so I could use it in my Mac. I downloaded the RetroPie image, extracted it and used the RPI-sd card builder software to write the image to my SD card. All good so far.

I put the SD card in my Raspberry Pi and followed a tutorial to get it up and running. I ended up doing something wrong and messing it up so I thought I would format my SD Card, write the image again and start over.

I put the SD card back in my mac and go to disk utility. I notice on the left hand side it says ‘2.2 TB USB2.0 CARD-READER Media’ but didn’t think anything of it and went ahead and clicked the ‘erase’ tab (formatting it as MS DOS FAT). It got half way through and then it just froze. I quit disk utility and went to try again but when I put my SD card in now it says ‘The disk you inserted was not readable by this computer.’ It still shows up on disk utility though. I tried it in my phone as well and it’s not recognising it.

Is my SD card broke? Did I do something wrong?

Any help would be greatly appreciated. Thanks.

And don’t forget to change the path for save state and save files to another path (on retroarch.cfg). My USB card was read only (maybe yours is not) so i had to put these Save settings back to the original /home/pi/retropie/xxx.

In the ROMS folder there should be a folder called mame. You put your ROMs in there. If the mame folder is in _unused then move it back into the ROMs folder, add your ROMs to the recently moved mame folder and restart emulationstation and mame will show up as an option. Once in a game you’ll use tab on the keyboard to configure your controllers since mame is different than retroarch configs. (https://www.petrockblock.com/forums/topic/configuring-usb-controller-with-mame/) You’ll also need to make sure your mame ROMs are from the 037b5 set (https://code.google.com/p/imame4all/wiki/GameList) otherwise they may not work.

Thanks. the emulator runs really well on the new rpi

My only issue is with controller mapping. I have two generic N64 USB controllers. Unfortunately the mapping of the keys is wrong. A and B map to the right hand down and left. and A&B map to the shoulder buttons. I cant quite figure out where this info is stored, and i’ve tried to set it up using retroarch but assume that mupen doesnt use retroarch because the mapping has no effect.

Can anyone help me with this??

Kinda the same way that you update the usbromservice. I apologise if this isn’t exact I’m going off the top of my head as I don’t have access to my pi right now.
cd RetroPie
sudo ./retropie_setup.sh

Select update script
Reboot

Then update usbromservice like you did before

get this image

https://drive.google.com/open?id=0B_knGioK16E6TlVpa3hmRi1PRHc&authuser=0

or do as herbfargus suggested, update the script, and then re-run the usbromservice. There was a bug with this in the 2.4.2beta image that has since been corrected.

The only thing I can think of that I made a mistake with was not updating the retropie setup script first. When I fixed it I updated the script first, rebooted, and then went back into the setup script and installed the usbromservice

Hi there, I started playing around with Retro Pie yesterday and since I didn’t have a USB controller available, I tried using the Fire TV gamecontroller via bluetooth. I followed instructions for connecting a PS3 controller (https://dhoium3009.wordpress.com/raspberry-pi-connecting-multiple-ps3-controllers-via-bluetooth/), but got stuck when it came to pairing the controller to the Pi.

Did someone already succeed in connecting the Fire TV controller? Any hints are really appreciated.

I am a newbie to retropie but I guess I am lucky enough to have SMB and SMK working without doing anything special.

However at first it did not work as mention in this post. I could navigate in the menu of SMB but when the controller froze once in the game (in the map land). This only happens if I have only one controller connected.

My configuration is a B+ with 2 identical USB gamepads connected to the Pie.

First I run the calibration from retropie-setup with only one controller connected. It created a new configuration file called “GreenAsiaInc.USBJoystick.cfg”, here is the content :

input_device = “GreenAsia Inc. USB Joystick ”
input_driver = “udev”
input_b_btn = “2”
input_y_btn = “3”
input_select_btn = “9”
input_start_btn = “8”
input_up_btn = “h0up”
input_down_btn = “h0down”
input_left_btn = “h0left”
input_right_btn = “h0right”
input_a_btn = “1”
input_x_btn = “0”
input_l_btn = “4”
input_r_btn = “5”
input_l2_btn = “6”
input_r2_btn = “7”
input_l_x_plus_axis = “+0”
input_l_x_minus_axis = “-0”
input_l_y_plus_axis = “+1”
input_l_y_minus_axis = “-1”
input_r_x_plus_axis = “+2”
input_r_x_minus_axis = “-2”
input_r_y_plus_axis = “+3”
input_r_y_minus_axis = “-3”

Then I connect the second controller and it worked, I have verified with 1 player and 2 players and it worked. Then I have tried SMK 1/2 players and it also worked. Maybe the key is to have two identical controllers connected?