-
Search Results
-
Topic: Auto Scraper v0.6
This is an auto-scraper that runs from a command line that supports:
NES, SNES, N64, GB, GBC, GBA, MD, SMS, 32X, GG, PCE, A2600, LNX, MAME(see below) ROMsIt works by crawling a directory of ROM files looking for known extensions. When it finds a file it hashes the ROM data minus any headers or special file formatting with the goal of hashing only the data pulled from the original game. It compares this hash to a DB and downloads the metadata and builds the gamelist.xml file.
You can find the source on github:
https://github.com/sselph/scraperAnd for trusting people who don’t want to bother compiling I cross compiled for several platforms, even the rpi:
https://github.com/sselph/scraper/releasesBasic Instructions:
Download/Build the scraper executable for the system of choice.
Copy it into your ROM folder.
Make sure it is executable on linux/mac(chmod +x scraper)
Run it (./scraper -thumb_only)
You will see it processing the roms and it will write a gamelist.xml file in the ROM folder.
If you are not running this on the RPI then copy everything(roms, image folder, gamelist.xml) to the retropi.If you want to run directly on a rpi or rpi2 you can follow these instructions:
https://github.com/sselph/scraper#install-from-my-binariesMAME has a slightly different and is based on names. You need to start the script with the -mame flag:
./scraper -mameIf these instructions are unclear you can checkout floob’s videos:
I physically have roms for the SNES , Nes , and N64 in the right folders on the USB drive i have plugged in, which has working GBA roms on it
i have tried to copy the SNES roms over to the SNES folder on the SD card but it literally said “copying failed” even if sudo and such
i only have Gameboy advance, IBM, PC and Apple 2 on my emulators screen. Can anyone help me out? :)I really admire the attempt to organize emulator management through the Retropie setup script, but the lack of good and current documentation and how fragile the Retropie seems at the moment is a bit frustrating.
I wanted to bring up 2 specific problems I’m experiencing with the RetroPie setup script because I have been unable to find documentation or discussion that’s helped point in the right direction.
1) Initially I started from a RetroPie 2.3 image. When I ran the setup script initially, I installed binaries to save time. When I experienced a few performance issues in a couple emulators (SNES, in particular) I wanted to try compiling from source. I re-ran the RetroPie Setup script and installed from sources with the default items selection to compile. This took a long time, as expected, but when finished, I found that most of the emulators were broken. I tried rebooting, but SNES, NES, TG16 and a few others would start to launch a ROM from Emulation Station, but would just return to the ROM list with no indicator of any error. The only way I was able to resolve the issues was a re-run of the RetroPie setup script to install binaries again, and everything worked. I guess what I’m asking here is, has anyone else has had the same issue with source based installs? Is this capability broken? Is there a plans to implement nightly binaries, and opt into Stable vs Nightly binary downloads? I’m a bit confused at the decision to do source based installs anyway since the RPi is such a slow platform and any PC or server could do it once for everyone once a day, instead of everyone downloading all sources and taking the 15-24+ hours it requires on a single-core pi. This seems very inefficient, and is the reason binary packages are far more common in common linux distros. Not everyone needs to tweak sources, right?
2) I know the N64 emulator support is in a poor state at the moment. I’ve read that it currently doesn’t run from Emulation Station. But I can find no way to debug it, and finding documentation that says what command needs to be run to launch it from the command line is virtually impossible. I wanted to try compiling from sources, but the N64 emulator doesn’t appear in the list of modules that sources are available for in the source modules list in the RetroPie Setup script. Do I have to modify a file to enable it in the modules list? Or does the fact it doesn’t show up mean that support for it is being pulled because of it’s non-functionality?
Anyway, just wanted to pass along a little feedback and ask a few questions. Sorry if it’s been covered, but I’m having a lot of trouble finding the “signal through the noise” with all the out of date, incomplete, and irrelevant documentation.
Hi
Im new to this project, i have just installed the PI with the RetroPie Project SD-card Image V2.3 image, everything went great, and installed 2 games “the pagemaster” and “Zelda link to the past” but after that everything went wrong. I tried to install Mario All-stars, Donkey Kong Country 1, 2, 3. When i started these games, the screen just flickered with green and yellow color. my games that worked are sfc files, and i tried with smc files and i got these error, then i thought, maybe its the file that dont work, so i found a sfc file, but that didnt helped either.
I also tried to play a GBA game pokemon firered, but that didnt work because it cant find the bios. I found a bios on google (dont know if it works) but now it dont say the bios error, now i just try to load the game, and then i jumps out again.
I also tried to play zelda on N64 and mario, linux is loading, and then i jumps out to the menu again. I have tried many other games, many other console, but same mistakes. The only one who works is SNES and only 2 games :(
Anyone who knows what i’m doing wrong? Is it only some games that works?
Topic: Problem with n64 emulator
Hello!
I have a slight problem with the mupen64plus emulator. When I boot up a rom, it just shows a really low resolution terminal. I couldn’t make any of it out because of the low rez, so i ran a rom from putty on another computer.
What i THINK is being displayed is:
Video: Mupen64plus opengl video plugin by rice v2.0.0 – 63.200 VI/S
So basically that keeps popping up on a new line in the terminal, and i think the last value changes each time.
I think my problem is that the video is not being initialized properly, or for some reason the full-screen, low rez terminal windows is appearing on top of the emulator.
Another thing, when i launch a rom from ssh, i get no video (obviously) but i do get sound, and many, MANY audio buffer under run warnings. However when i launch a rom from the emulationstation menus, I get no sound and no buffer under runs.
Any odeas of how I can get the video working so I can start troubleshooint the million other problems I am bound to have?
I love the idea of this system and I can’t wait to get it working.
Thanks!
Topic: Mupen64 input workarounds
First off I’d like to say how awesome this project is and how much fun I’ve had just getting it set up and configured.
Like most people I’ve had some issues with the n64 emulator, after using the workaround posted in this thread I got mupen64 to run.
A few tweaks later (1GHz OC, force VGA mode, 128mb split, etc) and mario kart runs relatively well sparing the occasional audio glitch.
The only issue I have now is that I don’t have a way to reliably exit the emulator. It seems like the only working way to exit the emulator in it’s current implementation is to hit the esc key on a keyboard – but my keyboard input does not seem to be registered by mupen (but it is working on some level as good old alt+printscrn+REISUB still works).
Any suggestions?
