Yes, when I am done with testing I plan to provide a whole image as download. I see this idea as an experiment that might give the RetroPie project another impulse.ti84 wrote:petrockblog
I just check your blog...are you going the include the whole distribution image?
Raspbian and the RetroPie setup script with all its components takes more than two gigabytes. I would opt at least for 8gb, but would prefer 16gb. Especially PSX roms are usually a few hundred MBs large ...Uplift wrote:What is the best sized SD card for the RetroPie setup? (Raspbian, RetroPie, lots of roms)
I have a 4GB SD lying around but think it would quickly fill up i'm not sure how much space raspian and retropie will use, not leaving much for roms?
Should i opt for 8gb or 16gb?
Will want to use PSX, NES, SNES, genesis etc..
You need to use retroarch-joystick and put its output into ~/RetroPie/configs/all/retroarch.cfgMrMarco74 wrote:I tried to find the solution for it, but after 60 minutes I gave up...
First, you did an extremely great work!
But... I can control the front end, using my Logitech Cordless Rumblepad 2, but as soon as I launch a game in the snes emulator, the controller is not more accepted. I've used a Competition Pro (USB) and it has the same behavior.
It seems, that the snes emulator is just ignoring the settings from the front end. What is exactly wrong and how can I fix this issue?
I suppose, that I have to add something to the retroarch.cfg file under RetroPie/configs/snes.
But what? I have no ******* clue
Btw... is there a FAQ somewhere on your homepage? I couldn't find some and if you don't have such a thing, I recommend setting up some.
Thank you for your kindness and help!
I believe RetroPie will always do the actions in the same order as long as they're selected (with Space). So it doesn't matter what order you select things in.jonez wrote:Is there a suggested order for new installs?
A fix was pushed for this recently, it shouldn't be necessary any more I think (you might want to run "git pull" in the RetroPie-Setup directory to make sure you have the latest version of the script).jonez wrote:Do I still need to use the missing file fix from here?
I have no idea how the autostart stuff works, so I can't really help you here, sorry.jonez wrote:Previously when I tried to use the auto-start, it would fail because I installed it under the raspbian user and not root. I enabled auto-login using the steps from here, and when it booted it would login and then when it tried to start emulationstation it would error out saying failed to initialize SDL. After it dropped me to the prompt if I typed sudo emulationstation it would start. For auto-start to work do I need to install under the root user? I tried that today and it didn't seem to put the files in the same place as before. Previously when I logged in as raspbian and typed cd, I'd see both RetroPie and RetroPie-Setup in the same directory. Today when I installed, logged in as root and typed cd, I'd only see RetroPie-Setup and the RetroPie folder was under /home/root? I'm not sure if that's part of my problem? When I launched the RetroPie script I followed the steps from here, login then type cd, followed by the git commands etc.
Shouldn't need to do this anymore.jonez wrote:Previously I had to use this command to get sound working:
echo 'snd-bcm2835' >> /etc/modules
Should I still do that or is it not necessary anymore?
Simplest way to remove it is to remove the Duke3D entry in ~/.emulationstation/es_systems.cfg (should be 4 or 5 lines, just remove them).jonez wrote:The binary method doesn't seem to give me a choice as to what to install? If it installs everything is there a way to remove what I don't want? If I remember correctly from when I tried using that option before (when it was still on GitHub) it will only show emulators that have games, but it also showed Duke3D which I don't want in the menu.
The full image is around 2.6 GB large. To be on the safe side I would recommend an SD card with at least 8 GB, but a 4 GB card would also do as long as you do not want to put PSX or large NeoGeo ROMs on the card.ti84 wrote:How large is the full "image"? Is it over 2.0 GB?
Good idea - I have just posted this as a new thread.kevkaos wrote:cheers for the .img
maybe start a new tread for your img so more folks here about it?
Do you mean this happens when you copy the image to your SD card?ti84 wrote:If it is only 2.6GB...how come when I try to download it...it goes over 3.5GB and then is interruped and stops? What am I doing wrong?
Actually, the downloadable file is a compressed image and has only a size of 1.6 GB. I just tested the download myself (again) and I cannot reproduce this.ti84 wrote:no...this is when I try to download it to my computer...windows...after I download it to my computer, I am going to transfer it to the sd card
The interruption after 3,6GB might be filesystem related. Are you using Fat32? Fat32 does not allow files larger that 4GB, if I am not mistaken.If it is only 2.6GB...how come when I try to download it...it goes over 3.5GB and then is interruped and stops? What am I doing wrong?
Could the entire problem, therefore, be filesystem related, too?!Actually, the downloadable file is a compressed image and has only a size of 1.6 GB. I just tested the download myself (again) and I cannot reproduce this.
Does anybody else have an idea?
These cores are all installed.adwhitenc wrote:I haven't taken a detailed look into the image, but are the following platforms currently installed?
I believe I saw SNES and NES but not sure about the gameboys. If they are not installed, is there a way to get them working?