Same here with ps3 controller over usb

First of all make a backup.
Windows: Run ‘USB Image Tool’ as admin and use device mode http://www.alexpage.de/usb-image-tool/
Linux/Mac: dd bs=1m if=/dev/”sdcard” of=/home/”userpath”/RetroPie.img

Disable overclocking:
# sudo raspi-config
# select Overclocking
# Select 700MHz
# Reboot

Update Raspbian:
# sudo apt-get update
# sudo apt-get upgrade
# sudo reboot

Update firmware:
# sudo rpi-update
# sudo reboot

Update RetroPie-Setup:
# cd RetroPie-Setup
# git pull

Install newest sources:
# cd RetroPie-Setup
# sudo ./retropie_setup.sh
# select “Source Based Installation”

Enable overclocking:
# sudo raspi-config
# select Overclocking
# Select 900MHz
# Reboot

I think you need to include these lines in es_systems.cfg since they are not included in the original setup

DESCNAME=Sega CD
NAME=segacd
PATH=/media/usb0/segacd
EXTENSION=.smd .SMD .bin .BIN .md .MD .zip .ZIP .iso .ISO
COMMAND=/home/pi/RetroPie/supplementary/runcommand/runcommand.sh 1 “/home/pi/RetroPie/emulators/RetroArch/installdir/bin/retroarch -L /home/pi/RetroPie/emulatorcores/picodrive/picodrive_libretro.so –config /home/pi/RetroPie/configs/sega32x/retroarch.cfg %ROM%”
#COMMAND=/home/pi/RetroPie/supplementary/runcommand/runcommand.sh 1 “/home/pi/RetroPie/emulators/dgen-sdl/dgen -f -r /home/pi/RetroPie/configs/all/dgenrc %ROM%”
#COMMAND=export LD_LIBRARY_PATH=”/home/pi/RetroPie/supplementary/dispmanx/SDL12-kms-dispmanx/build/.libs”; /home/pi/RetroPie/emulators/dgen-sdl/dgen %ROM%
PLATFORMID=21

DESCNAME=Sega 32X
NAME=sega32x
PATH=/home/pi/RetroPie/roms/sega32x
EXTENSION=.32x .32X .smd .SMD .bin .BIN .md .MD .zip .ZIP
COMMAND=/home/pi/RetroPie/supplementary/runcommand/runcommand.sh 1 “/home/pi/RetroPie/emulators/RetroArch/installdir/bin/retroarch -L /home/pi/RetroPie/emulatorcores/picodrive/picodrive_libretro.so –config /home/pi/RetroPie/configs/sega32x/retroarch.cfg %ROM%”
#COMMAND=/home/pi/RetroPie/supplementary/runcommand/runcommand.sh 1 “/home/pi/RetroPie/emulators/dgen-sdl/dgen -f -r /home/pi/RetroPie/configs/all/dgenrc %ROM%”
#COMMAND=export LD_LIBRARY_PATH=”/home/pi/RetroPie/supplementary/dispmanx/SDL12-kms-dispmanx/build/.libs”; /home/pi/RetroPie/emulators/dgen-sdl/dgen %ROM%
PLATFORMID=33

You can use the usb copy function of RetroPie to transfer roms, it’s enabled by default on the RetroPie image. See here for more details: https://github.com/retropie/RetroPie-Setup/wiki/How-to-get-ROMs-on-the-SD-card

Hi! First of all you must be careful with autocopy function. This searches on the folder “roms” of the usb for new roms (if that folder doesn’t exist it’s created), and if there are new roms, it will copy them to the sd. You can deactivate it, or you can leave this folder empty and create other folder with your roms (games for example).

Ok, you have the games in a folder, now you need to modify this file:

“home/pi/.emulationstation/es_systems.cfg”

How can you reach this file? you can use ssh or you can use an ftp (filezilla for example). I recommend you installing an ftp, it’s easy to manage files with it. If you have the usb plugged, you will see your folders in “/media/usb0/” if not, you have something wrong.

In this file you can disable emulators, and change the roms folder. You only need to change roms folder for each emulator like this:

“/Retropie/roms/mame/” change for “/media/usb0/games/mame/” for example.

If you scrapped the roms (It means that your games have picture and information), you need to modify gamelist.xml of each emulator. Change roms and image folders.

I think that I don’t forget anything, but feel free to ask.

But if you really want a controller, go for a SNES usb controller. I am currently working on my Retro Pie and Still waiting for parts. To have fun, you pretty much need Snes USB, power supply , USB hub if you want, and A custom case( My parents have a big 3d printer, that I can use if I pay) Then you would have a PiePhone 5s XD ! Joking but SNES USB is really the way to go. My idea would probably have some lag in it.

Hi, if you are using a usb gamepad this guide should help you: https://www.petrockblock.com/2013/12/02/retropie-autoconfig-functionality/

If you are using a wireless gamepad such as an Xbox 360 pad or a PS3 pad have a look at the RetroPie-Setup wiki: https://github.com/retropie/RetroPie-Setup/wiki

Regarding the Mega Drive emulator the roms need to be in .smd or .bin format and need to be placed in /home/pi/RetroPie/roms/megadrive

Hope this helps!

I’m using a PS3 wireless logitech remote for my 1st and the 2nd with a USB Logitech Gamepad.

So far, I haven’t had any problems with them. I’m probably going to figure out a second wireless device though because I don’t want somebody to pull my Pi off the table.

It would depend on what it presents itself to the operating system as, but I’ve had it working on both an official and un-official Xbox 360 Wireless USB receiver.

just to add, if you have the Xbox pad plugged into non-powered usb it won’t be able to draw enough power, try plugging it directly into one of the Pi’s usb ports

So you have to overclock the pi to play N64? What’s the safest way to go about doing that? You wouldn’t also know how to configure the N64 usb controller by any chance?

[quote=4250]
P.S. I started deleting Doom, duke3d, apple2, x86, and cavestory so that the gui loads only the emulators/roms the user has access to since I’m doing a usb controller only interface. This leaves the input config left, which someone could accidentally run and reset the game-exit. Does anyone know how to disable the input config screen? Thanks!
[/quote]

To get rid of the Input Config screen, do the following from either the command line (close down EmulationStation by pressing F4) or by SSH shell:

– sudo nano /home/pi/.emulationstation/es_systems.cfg
– go to the very bottom of the file and add comment hashes like this:

DESCNAME=Input Configuration
NAME=esconfig
PATH=/home/pi/RetroPie/roms/esconfig
EXTENSION=.sh .SH
COMMAND=/home/pi/RetroPie/roms/esconfig/Start.sh

to this:

#DESCNAME=Input Configuration
#NAME=esconfig
#PATH=/home/pi/RetroPie/roms/esconfig
#EXTENSION=.sh .SH
#COMMAND=/home/pi/RetroPie/roms/esconfig/Start.sh

– hit ctrl+x
– type ‘y’ then hit enter
– done!

This should kick you back out to the command line. You can always re-enable the input config by removing the hashtags.

From my own trials I have found the retroarch auto config to be hit and miss. If I start hot swapping controllers with retroarch open I tend to freeze the system.

If you run jstest with both controllers? jstest /dev/input/js0 then try js1

If you have enough USB ports, try having everything plugged in plus a keyboard. when you start up a rom press F1 to go into the gui and go into the inputs/controller section. See what controller driver is being loaded. (sorry I can’t remember the exact sub menu)

Are you using a wireless controller?

Sent from my GT-I9300 using Tapatalk

Yeah, make sure your keyboard is connected to the Pi and when a game starts press the tab button. That should bring up a menu and you can configure input for your USB pad.

Sent from my GT-I9300 using Tapatalk

Ah great, thanks for the diagram! Just one last question, I was planning to purchase one of these LED’s with a built in resistor: http://www.maplin.co.uk/p/5mm-red-led-ck46a for use as power indicator for the SNES case. Is it possible to plug this LED straight into a pair of female to female jumper leads and then into the 5v & ground pins on the Pi (making sure the long and short leg are connected correctly) Would this leave enough power for the usb ports? (running a flash drive and a usb pad)
Thankyou

Thanks for the feedback! After I posted this I figured out only about 75% auto scraped correctly, and sometimes it was the popular titles that didn’t make it. However, this is when they were all named incorrectly and filtered through goodtimes into new names. I’ve since found a rom download site that tends to have the roms already named correctly. In the end I will probably have to manually scrape and modify those unidentified roms a few times through until I have the base rom list easily identifiable. I might just manually scrape them in sections and weed out the crappy ones or rename them until the final product at which point I’ll of course have to do it manually from start to finish at this point.

Two questions I am wondering is whether the SD card write speed matters (ie 4 vs 10) or whether or not changing the the memory so that the pi has 256/512 vs 16/512.)

Another question: does anyone know what the file naming conventions are that are most easily identifiable by the ES-scraper? It seems like the most successful ones had a (U), a (!), and sometimes PRG. I’m guessing that (J) means japan and that (U) means US. Not sure what the exclamation point means. I started downloading the roms from http://www.romnation.net/srv/roms/ since they appear to be named well. I’ve been going for standard (U) without (!) if its available, ignoring the (hacks) (j) (Unl) and (0# B#) labels.

If I had the list that ES-scraper uses to identify roms I bet this could be a lot easier does anyone know how to access this?

Many thanks for all the input and help!

P.S. I started deleting Doom, duke3d, apple2, x86, and cavestory so that the gui loads only the emulators/roms the user has access to since I’m doing a usb controller only interface. This leaves the input config left, which someone could accidentally run and reset the game-exit. Does anyone know how to disable the input config screen? Thanks!

P.P.S. I discovered with the naming convention that (U) means US and (!) means verified good dump, so I’m going to test the difference between (!) roms and roms without the (!) label.