Ungh… What the heck? I just can’t get it to work. Sonic is mocking me!!!

I:
cd RetroPie-Setup
sudo ./retropie_setup.sh
Update setup script
Reboot

then run the setup script again after reset. The first time when I ran it after the update, I got pages and pages of code before it opened. Every time after that when I update, it just starts. So I figure that means there are no updates and I have the latest?

Then I go to install individual emulators. I pick the GenPlus-GX one. I choose “binary”, some code flashes for half a second and I am back in the install emulators screen. I choose “cancel” to get back out, then I choose “reboot”.

After reboot, I try to play a Genesis game, I press “x”, a screen asks what resolution I want (I don’t know what to pick so I just pick randomly) and I get spit out to a black screen with an error that says “runcommand line 283 command not found” Then “Powering on HDMI with preferred settings” then I am spit back to emulationstation.

No mention of an error report and my /tmp/ directory is empty aside from 2 folders that are also empty. (This is the /tmp directory from the root.)

One thing I always forget- did you update the setup script first?

cd RetroPie-Setup
sudo ./retropie_setup.sh
Update setup script
Reboot

Then proceed to do an individual emulator binary install.

edit! You need to do a full binary install not individual emulator install

Hey guys. I can not find GenPlus-GX. I’m assuming you wanted me to choose “5. install individual emulators from binary or source”? But there is only one Genesis option in there—Pico.

I chose “Source based installation” when I set this up (like a week ago) and I think that just installs EVERYTHING? I don’t remember it giving options. (I didn’t want to hit it because I am afraid it will just run the whole thing again)

Also, my command was sudo ./retropie_setup.sh if that changes anything?
Thanks.

scroll further down in the set up script for installing individual emulators- it is titled:
lr-snes9x-next.

This video goes step by step if there is any doubt.

Hi,

I would suggest you update to the latest binaries first as I detailed in this thread:

Where is the PocketSNES PPU.CPP file?!

The emulator-specific rom folders will be deprecated soon because it is now possible to choose the emulator used per system (and rom) for that matter. After doing a binary install (which is actually an update in your case) you could try to update the mupen64plus libretro core from source as an individual emulator from the setup script.

There’s a lot of instructions between the github wiki page as well as this forum. You’ll need to also look at the configuration documentation for the individual emulator you’re using. A little google and searching the forums and you’ll get the commands for exiting an emulator.

Another followup to avoid confusion:

When you do this, the new default emulator for SNES is lr-snes9x-next. Is there a reason you would like to use PocketSNES? If it isn’t installed per default anymore follow the individual install route as explained before and access the emulator selection menu by pressing “x” or “m” shortly after starting a rom from Emulationstation.

Yes, to make it a little clearer with less text ;)

I would suggest you use the RetroPie Setup script which you can start as explained and then:

– Update the script itself using the appropriate menu item
– Reboot (not needed, just to be safe)
– Execute a binary installation to get the latest binaries and the updated runcommand to select emulators
– Reboot

This may already solve your problem. If not:

– Update the PocketSNES emulator by using the command to update individual emulators and choosing “From Source”

If this doesn’t solve your problem please report back and I will help you compile a version yourself.

REMEMBER TO BACKUP :) (since these operations will potentially overwrite changes you made)

To follow up on this I just checked the PocketSNES repository and it seems this was fixed, so updating the PocketSNES libretro core from source as described should be all you need to do. No editing of source files necessary…

That being said, if you are using the SD image 2.6 updating individual emulators will break your installation because a new mechanism was added for choosing emulators per system and rom. To update to this system you will first have to choose “Binary installation” after updating the setup script as described in the above post. This might already give you an up to date PocketSNES.

In any case BACKUP ANY RELEVANT DATA before doing any of this.

OK, sorry, I wasn’t sure about your level of knowledge in terms of the structure behind the project and such. Let me try another approach.

RetroPie is basically a collection of scripts (automation) to setup a the Raspbian OS on your Pi so that it runs EmulationStation and a couple of emulators (plus a couple of handy enhancements).

The setup script either installs the emulators via binary distribution (someone else already compiled the source code and you just get the resulting “program”) or source distribution (the script downloads the source code, compiles it, copies the “program” to a folder and deletes the source from your Pi). Either way as a user you actually never “see” the source-code on your Pi because it either never made it there or was deleted after generating the emulator from it.

What you would have to do is manually getting the source-code you would like to edit (like the setup script does), change it and then compile it. What I was suggesting was mimicking what the setup script does (this is on your Pi in /home/pi/RetroPie-Setup), if you have never had any contact with bash scripts before this might be too much of a hurdle though.

Is the change you would like to have implemented already don by the authors of PocketSNES? If so it would suffice to just let the setup script compile a new version for you.

What you would need to do for this, is first update the setup script:

cd
cd RetroPie-Setup
sudo ./retropie_setup.sh
<Update Script>
<Reboot>

Then update the PocketSNES emulator from source by executing the setup script like before and choosing to update “individual emulators” and then “from source”.

Hope this made some sense…

You’re most welcome!

What sort of problems are you having with Street Fighter? With the new kernel update from Feederchain (custom_kernel_1.20150317-1.tar.gz) it should make the Pi see both joys as individual and get around the 10-button limit.

1. There are two different folders for N64 ROMs. Each folder will utilise a different emulator. Note that the non-standard N64 emulator doesn’t use the standard button mappings and often has to be tweaked separately.
2. You can either edit it via ftp or locally(or SSH) using Nano. If you do it via FTP in Windows, I recommend using Notepad++ to edit the files as Notepad does not lay out the file nicely.

To edit the file locally:

sudo nano /opt/retropie/configs/all/retroarch.cfg

This edits the primary config file and affects all Retroarch Emulators (which is almost all of them).

Each emulator has its own folder for individual configuration. EG:

sudo nano /opt/retropie/configs/psx/retroarch.cfg

The above lets you specify extra config just for the PSX.

Thanks for that vulga. Yes using Xin Mo 2 player.

Everything appeared to be working when I had it connected to my laptop over USB I used a visualiser to test everything on OSX and it appeared to be good all over.

I have not successfully had it working on retropie as the first issue I had was the turbo fire which made the ui navigation in emulationstation pretty much impossible. I did a clean install with latest to no avail and next step was to install the custom firmware which worked really well except the diagonals.

I will run another vanilla install without the kernel update and see if it still plays up and re-wire it to match your setup and see how I get on.

It’s an odd one because I know each switch works individually and I can definitely hear both go down.

I haven’t done anything to the Xin other than connect everything, have you updated your firmware?

you need to upgrade runcommand also – and all the other megadrive emulators. probably easiest to do a full install.

There wasn’t really a way of adding the new functionality but keeping the “individual install” option working.

[quote=92013]I know that, but it is possibe to get to the regular raspbian and still have RetroPie on it?[/quote]

RetroPie has regular Raspbian, just with a few packages uninstalled (that you’re free to re-install and maybe don’t need anyways). It would help if you actually said why you want to dual boot.

But yeah there’s plenty of info on dual booting a pi, and from your first comment it sounds like you’ve already done it in the past:
https://www.google.com/search?q=dual+boot+raspberry+pi&btnG=–%3E&gws_rd=ssl

Looks like a “standard” bluetooth gamepad (xbox360 is not bluetooth, sixaxis is not standard). If there is a module in kernel for it (i suppose you could check that by seeing if it is recognized as a gamepad when plugged by usb), following a tutorial for ds4 bluetooth on linux should help : https://wiki.gentoo.org/wiki/Sony_DualShock

As stated above RetroPie is already running on top of Raspbian.

If you’re looking to have a dual purpose retro gaming setup and media center there are existing solutions that you may want to consider:

http://www.raspberrypi.org/forums/viewtopic.php?f=78&t=59590
http://www.recalbox.com/

There are also ways to modify RetroPie to support launching into XBMC but it would take some work.

You can’t use openeelec with retropie per se. What you can do is a dualboot setup. Either use Noobs with a Rasbian/OpenElec installation or use Berryboot with the same (i think there’s a Retropie 2.6 squashfs (needed for Berryboot) floating around in these forums). Beware that Noobs will default to splitting your sd card “in half”, every os-partition will be the same size.
Alternatively you can just install Kodi on a Retropie Installation.

I think because retropie has yet to have an official logo they’ve left it pretty generic/ up to individuals. I’m partial to the mushberry but some may feel that is too nintendo-centric. a few svg files should do the trick though.

sixpair won’t work with ds4 (sixpair = sixaxis pair, ds4 is not a sixaxis), but you actually don’t need sixpair to pair your ds4 with your pi, the following guide should work on any distro with blueZ >= 5.14 and kernel >= 3.15 :
https://wiki.gentoo.org/wiki/Sony_DualShock

For others with the same problem – I found a workaround – but not ideal – solution. No idea if this was introduced in 2.6 or not.

For some reason, those retroarch.cfg files in individual system’s folders don’t seem to be pulling in any additional input lines. All of the other lines seemed to be working fine.

I was able to get the secondary configs working by calling them with the –appendconfig command line switch.

You have to change the command line in order to do this. For GB it was in the es_systems.cfg file; and for NES it was in the emulators.cfg file I believe. I also had to remove the #include line at the beginning of these individual config files.

For example:
OLD:
/opt/retropie/supplementary/runcommand/runcommand.sh 0 “/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/neslibretro/fceumm_libretro.so –config /opt/retropie/configs/nes/retroarch.cfg %ROM%”

NEW:
/opt/retropie/supplementary/runcommand/runcommand.sh 0 “/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/neslibretro/fceumm_libretro.so –config /opt/retropie/configs/all/retroarch.cfg –appendconfig /opt/retropie/configs/nes/retroarch.cfg %ROM%”

I just did this today:

UPDATE SETUP SCRIPT:

cd RetroPie-Setup
sudo ./retropie_setup.sh
update setup script
reboot

INSTALL INDIVIDUAL EMULATOR:

cd RetroPie-Setup
sudo ./retropie_setup.sh
Choose option 5: Install individual Emulators
Select the emulator you wish to install
Then either choose binary or source (binary is really fast to install, source takes longer but is more up to date) 
then reboot

see this video: