[Floob]

Do you get the error if you:
– Create clean 2.6.0 image
– Run it and quit ES
– Manually edit gamelist. Save it
– Restart ES? (By typing “emulationstation” at the command prompt.)

I’ve done that approach and its always been fine.

[Floob]

Check the video for the paths.
The only place I had to put my kick13.rom was /home/pi/RetroPie/BIOS/

The only place I had to put the game was /home/pi/RetroPie/roms/amiga/

This is from a clean 2.6.0 image downloaded from this site (I havent separately tried updating the binaries).

[Floob]

Longshot, but the ES gamelists will complain *a lot* if you make ANY change at all whilst ES is running. Make sure all changes are done without ES running.

[Floob]

Sure, I use an iBuffalo USB joypad:
http://ecx.images-amazon.com/images/I/51AoJp5lcQL._SL1000_.jpg

[Floob]

Exactly which folder have you copied it to and which game are you trying to run?
Can you run other games?

[Floob]

UAE4ALL worked fine out of the box for me (using clean 2.6.0) image.
My setup is here:

[Floob]

The setup script is in
/home/pi/RetroPie-Setup/

This playlist will give you a good overview of how controller configs work

http://www.dailymotion.com/playlist/x3nvkw_smartretro_retropie-usb-controllers/1#video=x2hudlt

[Floob]

I’d be tempted not to use the internal scraper and use sselphs instead – its very efficient.

[Floob]

I am saying that anything in here would override other settings – so its often best left blank for simplicity
/opt/retropie/configs/snes/retroarch.cfg

Ideally your controller settings should be in the auto controller detection file of:
/opt/retropie/emulators/retroarch/configs/{controllername}

The filename here will be more like “USBGamepad.cfg” it wont be retroarch.cfg

You can update your retroarch controller file by using the retropi-setup script and registering a retroarch controller.

[Floob]

The emulator used defines if you can save games, for example, any emulation using RetroArch will allow saving using F2. It all depends on the emulator used.

The Game Boy Advance requires a BIOS file, I dont have an exhaustive list, but ask if you have a system in mind. Most dont need a BIOS.

[Floob]

In the 2.6.0 image you put the roms (named kick13.rom, kick31rom etc..) in /home/pi/RetroPie/BIOS/ they are symlinked from the app directory.

The UAE4all GUI will quite happily run the roms then.

[Floob]

Do a clean install of 2.6.0, put one SNES rom in
/home/pi/RetroPie/roms/snes/

You can confirm the files that are parsed to run this by reading the
/etc/emulationstation/es_systems.cfg

It will read first
/opt/retropie/configs/all/retroarch.cfg
This in turn will check this directory to manage your controller
/opt/retropie/emulators/retroarch/configs

Then anything specified in this file will override what has been read so far
/opt/retropie/configs/snes/retroarch.cfg

You shouldn’t need to run “sudo rpi-update”, just run
sudo apt-get update
sudo apt-get upgrade

Although to be honest that isnt needed really, the straight image should be fine.
I dont think running rpi-update should have damaged anything though.

[Floob]

Part of the issue is you have auto select controller set to true, but then you specify your controller setup in the main retroarch.cfg. I’d do one or the other.

input_autodetect_enable = true

or just set this false:
input_autodetect_enable = false

If I was you I would set a button (joypad) to enable hotkeys rather than trying to get them to work on their own. The video above runs through a full example.

[Floob]

Can you post your /opt/retropie/configs/all/retroarch.cfg as an attachment?
You might simply need to change
input_enable_hotkey = nul
to
input_enable_hotkey = alt

[Floob]

Thats weird, the EVO is working well on mine.

Here is one way to backup:
http://smartretro.co.uk/forums/viewtopic.php?f=3&t=58

Did you say it is a 2A PSU, previous Pis didnt need as much and used a 1 or 1.2A typically. It should say on the plug.

[Floob]

You could post up your controller file and perhaps we can see the issue.

This may help:

http://www.dailymotion.com/playlist/x3nvkw_smartretro_retropie-usb-controllers/1#video=x2hudlt

[Floob]

You can set a per system control setup if you edit
/opt/retropie/configs/{systemname}/retroarch.cfg

[Floob]

This should help you with scraping

[Floob]

You dont mention if you have included this line?

input_enable_hotkey_btn = “”

Remember hotkeys will only work if the enable is pressed, so you have to hold select and then press M for example to scroll through the shaders. Same for RGUI with F1, you must hold your enable hotkey button.

[Floob]

You’ve got quite a mixture of quotes in that example, some are ” , ″, “, ”

Are the all exactly the same type when you edit the file with nano?

[Floob]

Check the file in
/home/pi/.dosbox/

[Floob]

You could try using these retroarch.cfg file instead, and keep the line blank in your main one.

/opt/retropie/configs/{systemname}/retroarch.cfg

Then you specify your full path:
/home/pi/RetroPie/savefile/snes/

[Floob]

This is where all the controller files generated by retroarch joyconfig tool are kept, they are effectively the auto files and can be used on a hot swap basis:
/opt/retropie/emulators/retroarch/configs/

This file is always used by retroarch emulation regardless of your controller, so settings in here would be effectivly hard coded and always run.
/opt/retropie/configs/all/retroarch.cfg

There is no significance of the fact that some of the controller files are set to be executable.

This should help more:
http://www.dailymotion.com/playlist/x3nvkw_smartretro_retropie-usb-controllers/1#video=x2hudlt

[Floob]

This should help you work out which button is what:

You can find the files produced by retroarch here:
/opt/retropie/emulators/retroarch/configs

[Floob]

Does that game not work under /home/pi/RetroPie/roms/nes/?

[Floob]

Did you paste that error message or type it?

This filename isnt right: retrorch.cfg

Did you use the 2.6.0 image to create this setup?

[Floob]

It sounds like your hotkeys are set to on all the time.
Try changing this in your /opt/retropie/configs/all/retroarch.cfg file

input_enable_hotkey = nul
to
input_enable_hotkey = alt

Here is a hotkey guide

[Floob]

Try here:

/home/pi/.dosbox/dosbox-SVN.conf

[Floob]

I think it may be the SD card – do you have another?
Is this the v2 image of RetroPie, and your PSU has 2A rating?

[Floob]

Attached is the file from
/opt/retroarch/configs/all/retroarch.cfg

This is from 2.6.0 image

[Floob]

It would be best to start with a clean retroarch.cfg, then check out this video to confirm where you can set your hotkeys.

[Floob]

Im always interested in a new theme.
The default one is very smart and clean, but choice is great.

[Floob]

Change this
# input_enable_hotkey = nul

to this
input_enable_hotkey = alt

But also, is there a reason you want to hardcode your controllers and hoteys in retroarch.cfg and not use the auto detect method instead.

[Floob]

I had a dodgy HDMI cable once – could you try another.
Ideally try another TV as well just on the off chance.

[Floob]

Have you tried blacklisting xpad?

XBox 360 wireless controller – blinking lights

[Author]

Posts