[Floob]

I’m pretty sure its all good if you use 2.4.2 and update the RetroPie setup script.

[Floob]

Try changing the xbmc there to kodi. You save by pressing Ctrl-x then press “y” to confirm.

Its odd though because it sounds like xbmc works fine for you from the command line.

[Floob]

Navigate to
/home/pi/RetroPie/roms/ports in a SSH session with PuTTY for example (as opposed to using an FTP client)

Then edit the file with the command
sudo nano xbmc.sh

In there you will see the command its trying to run.

There is no need to rename the filename itself.

[Floob]

What does your xbmc.sh file have in it?
/home/pi/RetroPie/roms/ports/xbmc.sh
or do you also have
/home/pi/RetroPie/roms/ports/xbmc.sh

Regardless the command should either be “kodi” or “xbmc”
Although I think the paramater –standalone may also be used.

[Floob]

2.3 should work fine, but there isnt really a burning need to update the binaries – just use the image as it comes.

[Floob]

You can check the expected file extensions by reading this file

/etc/emulationstation/es_systems.cfg

[Floob]

hmm, I have read this, I’ll try it:

Gngeo-Pi is compliant with roms set of mame 0.138.

AdvMAME uses 0.106

[Floob]

This should help with save states

How to save games in RetroPie / RetroArch

and here is more detail on hotkeys

[Floob]

I know its not a very specific answer, but I would be tempted to start from the top with a fairly recent tutorial. Saying that it could be as something as simple as you are using RetroPie 2.3 but adding roms in a zip format.

Download the 2.4.2 image based on this guide:

You can download it here:
https://www.petrockblock.com/retropie/retropie-downloads/download-info/retropie-sd-card-image-v2-4-2-beta/

[Floob]

Great, thanks for looking into it.

Have to say, besides that issue, the setup script worked fine for me. I didnt have to configure or install anything else at all.
It recognizes the bluetooth device on reboot so is pretty much complete.

[Floob]

Try
sudo rm USB,2-axis8-buttongamepad.cfg.save

[Floob]

Ok – so Sudo nano USBGamepad.cfg will never open those files because they have a different name. Hence it is opening an empty file when you try it.

You have 3 files listed there made on the 3rd Jan (Starting USB,…..) – I am really not sure how they have ended up with the extension .save on them though.

Get rid of them with
rm ‘filename’

Then give this another go:

[Floob]

The retroarch file (and some others to be honest) is far from the stock version, and from your description you seem to have a 2.3 and 2.4 retropie running, all a bit odd.
You could resolve the config setup you have, but may well be far easier to install a new image.

This video may help with your multiple controllers.

[Floob]

Have you tried tweaking the es_systems.cfg file to change video mode for the Atari only?

[Floob]

Well I’m pretty sure those lines will append/fix your joypads in the retroarch.cfg so you would always need to use them for all the systems. In the video below I suggest just using the auto procedure instead.

You can of course hardcode them in the retroarch.cfg – if you attach the file I could look at it for any obvious errors.

[Floob]

This may help:

Managing ROMs with clrmamepro

In terms of the base build, I’d just use 2.4.2 and not update it, the image is ready to go as is.

[Floob]

Overclocking is pretty common, and as far as I’m aware wont invalidate your warranty

https://github.com/retropie/RetroPie-Setup/wiki/Advanced-Configuration

[Floob]

I made a quick MAME based update here:

[Floob]

Does writing the image (to a card at least 4GB) not work with this program?
http://sourceforge.net/projects/win32diskimager/

[Floob]

No, sorry I meant the hotkey.sh file is there on 2.4.x

Although I think all the keys are listed in retroarch.cfg, the only ones I tend to use are the shaders and saving and loading games along with exit emulator. Lots of options show in the RGUI as well with F1.

[Floob]

Yep, you can set an exit button combo pretty easily

[Floob]

This may help as a hotkey overview

[Floob]

The file that specifies the emulator to run is

/etc/emulationstation/es_systems.cfg

If you navigate there and edit it with
sudo nano es_systems.cfg

you will scroll to the MAME section, and you’ll see which it is using, often of it isnt set to mame4all already, the mame4all option would be there but commented out, so its easy to enable it.

But as Roo says, much better idea to use a newer image.

[Floob]

My first thought is that you simply have a different joypad to me.

So, when you are in that configs directory, type
ls -lah

and look at the time stamps next to the files, one of them should be quite current (the date you configured your joypad) see what the filename is for that.

Then type

sudo nano (the filename with the recent datestamp)

[Floob]

hmm, its there on version 2.4, I’m not sure which version you are running though.

I’m not too sure what you are trying to achieve though, currently you can either set a key to act as a hotkey or not, thats not an issue.

[Floob]

Sorry it didnt work – I’ll see if I can get it to work on my setup.
But yes, updating to the latest image would be a good idea to get the latest benefits.

I’ll look out for you here:
http://www.playblackpool.com/

:)

[Floob]

Yes, it should look jibberish as its not a text file. But please backup yours in case there is an issue.
I’m not sure of the approved clean way of resetting the config besides this sort of approach (or rebuild the image/emulator)

[Floob]

Most functions in the retroarch.cfg can be enabled with a hotkey – but its either they work with a hotkey_enabled set, or without. I cant see how you could possibly mix and match.

This may help:

[Floob]

I guess you could try deleting (or just rename it):
/opt/retropie/configs/mame4all/cfg/default.cfg

I’ve attached my copy (you need to rename it to .cfg).

[Floob]

This bit looks really screwed in your USBconfig.cfg file

input_enable_hotkey_btn = “9”
input_exit_emulator_btn = “8”
input_save_state_btn = “4”
input_load_state_btn = “5”

My first thought is that you havent used the correct ” symbol – try copying it from one of the other lines.

[Floob]

Which version of RetroPie are you running?

[Floob]

Are you using the 0.37b5 romset?

Also, have you tried using the keyboard as a controller to check that is responding ok to that?

Make sure you are using at least RetroPie 2.3 as that makes mame4all the default emulator, which is pretty good.

I’ve put a controller video together here:

[Floob]

These should help:

[Floob]

Quit EmulationStation (or change the boot sequence to not run it) then try to configure your controller.

[Floob]

Yep thats better. That file looks ok to be honest.
Can you do your controller file in the same way?

It should be
cat /opt/retropie/emulators/RetroArch/configs/USBconfig.cfg
and
cat /opt/retropie/configs/{the system you are using}/retroarch.cfg

[Author]

Posts