[SomeCoolName]

Very nice. I’ve added it to my build. Thanks for the great splash screen.

[SomeCoolName]

The likely issue is that your ROMs are in zip format. According to the github page, the accepted file extensions are .bin .a26 .rom.

https://github.com/retropie/retropie-setup/wiki/Atari-2600

If you want to use this system, you are going to drop in ROMs with a different file format.

[SomeCoolName]

OK. Have you chosen any systems to scrape? Are you clicking scrape all systems, or just scrape chosen systems? If you selected scrape chosen systems, did you tick any systems off?

[SomeCoolName]

The actual command to start up retropie setup from the command line is retropie_setup.sh
However, you can access retropie setup from the GUI, by going to the Retropie menu in Emulationstation and clicking Retropie-Setup.

[SomeCoolName]

The built in ES scraper is pretty unusable. I use the sselph scraper, and can easily scrape all my systems in a couple hours. That’s with complete sets of ROMs for each.

You can find the sselph scraper in the experimental menu of retropie setup. If you find that doesn’t work properly the manual method is pretty easy as well. Basically you put a copy of the scraper file in the directory for the system you are trying to scrape and set the permissions to 777 using winscp or another FTP client. Then you only have to browse to the system’s directory in the terminal, and run the following command:

sudo ./scraper -thumb_only

The scraper can be found here:

https://github.com/sselph/scraper

And there is tons of information on using it along with an excellent video by Floob, if you do a quick Google search.

[SomeCoolName]

As far as a I know, you select the video plugins for mupen64plus in the runcommand menu. Its been a while since I did it, so I don’t remember if there is a specific option for changing the video plugin for N64 or you use the default emulator setting. Either way, the options will be mupen64plus-rice, mupen64plus-glide64 etc.

https://github.com/retropie/retropie-setup/wiki/runcommand

[SomeCoolName]

I have the official Pi display, and wanted to do the same thing for my portable build. After a lot of digging around I could not find a way to accomplish this.

What I ended up doing was picking up a latching on/off button from Adafruit and a longer length of the PCB wire the display uses. I soldered the button in the middle of one of the wires, and used that for the wire attaching the 5V pins. Then if I wanted to power the display I only had to push the button down, and outputting to the display only took another button press to release. Note if you do it this way, the Pi will not change its video output mode while powered on so it will really only work if you press the button on or off before powering on the Pi.

The default for the Pi is to favor HDMI audio, so as long as HDMI is connected and powered on it will output to that and bypass the speakers automatically.

In case you needed it, this is the type of PCB wire I used:
https://www.adafruit.com/products/1951
And this is the style button:
https://www.adafruit.com/products/1476

I am only providing these for reference, you can use any you like.

[SomeCoolName]

For anyone else having this issue, I was able to solve it. It turns out that whenever the controller paired while emulation station was loaded it was moving my PS3 controller config to a cfg.bak file and generating a new config file. I was unable to do anything about this.

In the end, I used RGUI in the Retropie menu to set up the hotkeys for the controller in the actual retroarch.cfg. After saving the config file, I removed retroarch.cfg and renamed the file generated by RGUI to retroarch.cfg so that it became the config. Now when the new config file is generated for my controller, the hotkeys still function because they are hard coded into retroarch.

[Author]

Posts