[Mutex]

I am using .cue/.iso roms in mednafen-pce.
Make sure you have the syscard3.pce in your BIOS folder. Then check your es_systems.cfg (probably in /etc/emulationstation) to see if your entry for the pc engine has .iso added to the supported file endings. Also if you are using .cue files check if the filename of the .iso file is the same name as the one written down in your cuefile. (it’s case sensitive)

[Mutex]

The controls don’t become unresponsive, they just switch to the second player. If you connect another gamepad and switch the controller as soon as your controls don’t work anymore you can easily play the game.

And yes there are now new emulators that don’t have that problem. snes-9x-next for example works flawlessly with the game, althogh a pi1 is probably not powerful enough to use that emulator.

[Mutex]

Emulationstation will look for both actually. If there’s one in ~/.emulationstation it will overwrite the one in /etc/emulationstation

The /etc/ one is meant to be the default one and if you want to change something around in the es_systems.cfg copy it to ~/.emulationstation.

That way if there’s an update for the es_systems.cfg it won’t overwrite your version and you can easily compare and add the changes to your es_systems.cfg if you want to.

If you just want to get the one in /etc/ to be used, delete the one in ~/.emulationstation/

[Mutex]

Actually with the newest image that could work. You can choose the emulator for every rom that you want to play, but you would have to do some cfg tinkering and add the fba emulator and the mame emulator to one emulator.cfg.
Then you can choose the corresponding emulator for every single rom, so that would be a lot of work.

[Mutex]

You can copy the es_systems.cfg in /etc/emulationstation/ to ~/.emulationstation.

Then you can edit the es_systems.cfg in your home folder and remove all the emulators you don’t need (additionally you can change the order of the systems shown by emulation station). If you want to be really thorough you can then remove all folders connected to the deleted systems in ~/.emulationstation/ (that’s where all the gamelist.xml files are)

[Mutex]

Are you using zip archives? I don’t know if every retroarch core supports playing zipped roms.

If that doesn’t help you could tell us which core you are using. You can find that out by pressing x or m before the emulator starts.

[Mutex]

Just because you have 2000 games doesn’t mean you have the right version of those games. Mame is different from pretty much every other emulator in that you have to make certain that every file needed by the emulator is within the zip file for that game. You don’t just have one binary file with the rom dump like other systems, but you actually have lots of different files that are need to run the game.

That’s the reason you need a specific romset version to run with a certain emulator, i.e. pimame4all uses the romset version 0.37b5. That is a relatively old version of MAME so the compatibility with modern roms is lacklustre. If you download a MAME-rom somewhere that version is most likely for a newer Mame version and you need to use programs like clrmame to transform the game into the right version for your emulator.

If you try the games from the right romset version you will see that noone lied about the emulator running those games.

[Mutex]

Its actually not that complicated

just add

input_player1_a_btn=""
input_player1_b_btn=""
input_player1_x_btn=""
input_player1_y_btn=""

to your /opt/retropie/configs/%system%/retroarch.cfg
(for snes /opt/retropie/configs/snes/retroarch.cfg)

That overwrites the button layout for the first player.
For the second player you have to obviously replace the 1 with a 2.

And of course you have to add the corresponding button number in between the quotation marks.

[Mutex]

You coud try running it in final burn alpha (pifba on your pi) since its a cps2 game.

[Mutex]

Much like raspbmc, OSMC is a full operating system focused around Kodi. You can try to install the retropie_setup skript on a OSMC installation – i think it’s still debianbased – but I’m not sure that it will work.

The option to install Kodi in the retropie_setup is exactly that… it installs the kodi stuff on Raspbian. It’s not a full operating system or anything and you can’t install a different OS through Retropie. You could theoretically check the OSMC sources if available for all the changes made (i.e. the Kodi skin used by OSMC) and pack that together to install it on top of a Kodi installation but that’s a lot of work.

[Mutex]

It’s defined by the way the emulator executable is called (check the es_systems.cfg). For retroarch it loads the retroarch.cfg in the corresponding system folder. That retroarch.cfg includes the one in configs/all. So if you want to overwrite the button layout you can do it in the system specific config folder. The system specific config also has the variable input_remapping_directory which defines a folder with a new config cfg.

If you want to do it for every retroarch core you can change the auto config file for your controller. Changing the retroarch.cfg in configs/all with a new button layout did nothing for me while the autoconfig was enabled.

[Mutex]

Lakka is a retroarch distribution that is forked from openElec. It seems that it only supports playing retroarch cores and not any standard kodi features. I don’t know if there is any plan to add normal kodi to lakka.

I found a tweet from lakka.tv that said that if you want to use kodi you need to install openelec…

Tweet

[Mutex]

There’s an option in the retropie_setup script, I think in the experimental subfolder. I think you can install all addons since it installs a full Kodi installation. It could be slower than a separately installed OpenElec, since OpenElec is a bare-bones Kodi without much in the background (no complete Rasbian running) and is optimized to run exactly that, Kodi, but I’m not sure. Last time I tried that, it ran pretty smoothly but could have been a bit slower and laggier than a separate installation.

[Mutex]

You can’t use openeelec with retropie per se. What you can do is a dualboot setup. Either use Noobs with a Rasbian/OpenElec installation or use Berryboot with the same (i think there’s a Retropie 2.6 squashfs (needed for Berryboot) floating around in these forums). Beware that Noobs will default to splitting your sd card “in half”, every os-partition will be the same size.
Alternatively you can just install Kodi on a Retropie Installation.

[Mutex]

You can install Noobs, install Raspbian via Noobs and then use the retropie setup script to install retropie.
You cannot install anything along Noobs but you can use Noobs to install multiple operating systems, i.e. raspbian and openelec. Alternatively you can use Berryboot to do the same thing (install multiple os). Berryboot additionally has a prepared retropie image and someone here in the forum created a new Berryboot image for Retropie 2.6.

[Mutex]

You could try pressing F4 (exit emulation station) and check what the error message in the terminal is saying.

What game is “sta3.zip”?

[Mutex]

That can also happen with low quality usb cables. I had exactly that problem and after i changed the usb cable the square disappeared.

[Mutex]

PAL uses only 50Hz refreshrate compared to 60Hz on NTSC Systems. If you are now using an NTSC game in an PAL system only 50 FRAMES of those 60 are displayed in 1 second. So the game will actually run slower. That also works the other way round. Using a PAL game on an NTSC system lets the game run faster than intended. Some Systems are able to adapt the framerate according to the system used (sms, genesis come to mind) but not all. If you want to use a PAL romset you should check if the used emulator supports switching between PAL/NTSC or maybe even has an autodetect feature. Additionally not all Monitors/TVs support PAL/NTSC.

[Mutex]

The raspberry pi has 256/512/1024 MB of RAM. That RAM is split between your CPU und the graphics chip. So a 128/128 split on a rpiA means that 128 mb of your RAM are reserved for your graphics chip. Some applications need a minimum amount of ram reservered for your cpu/gpu.

What you should use depends on what you want to do with your pi. In Retropie you normally don’t need a 50/50 split on a rpi2. The biggest consumer for your gpu is emulationstation which needs atleast 256 mb of gpu-ram. Most emulators are more cpu heavy than gpu heavy, so having more ram for your cpu is good. The default mem-split set in the retroarch setup script is 384 mb for your gpu, which is plenty enough.

[Mutex]

I’m using the same gamepad and had similar results. I ended up disabling the gamepad autodetect in the retroarch.cfg and adding my buttonmapping to the retroarch.cfg.

I was able to change the button layout in the autoconfig file for the f710 but that doesn’t work well with all emulators especially with genesis.

If autoconfig is activated retroarch doesn’t check the configfolders defined in the es_systems file and just uses the autoconfig for every emulator. At least it did that for me.

[Mutex]

into the ~/RetroPie/BIOS folder

[Mutex]

it should be installed but not as a sms emulator. Its the default gamegear emulator in retropie. If you want to use it as sms emulator you have to do some tinkering with your es_systems.cfg.

[Mutex]

[quote=86696]

<div class=”d4p-bbt-quote-title”>franky wrote:</div>You might be using a PAL rom. That would explain why it’s slower than you’re used to.

Hmm I don’t think that this could be the problem since I use the same rom file on my Samsung Galaxy S4 in an emulator where it runs absolutly smooth and how it should be. :/ But I’m not quite into it. Are there really speed differences between the local versions of mega man?
[/quote]

Yes PAL (50hz) uses a different refresh rate for your monitor than NTSC (60hz) and the NES emulator doesn’t detect if your rom is for NTSC (us) or PAL (EU) so that could have something to do with it. I just ran mega man 2 on my rpi2b and it ran flawlessly.

[quote=86704]Hi! did anyone already tested CATSFC (snes emulator) with this new board?[/quote]
I compiled it and tried Kriby Superstar with it but its way too slow. Didn’t try the emulator with a less taxing game but pocketsnes now plays every rom I tried (star fox/kirby superstar/mario world 2) at full speed.

[Mutex]

mame4all-pi is installed with the image / binary install. It’s configured to be the default mame emulator in retropie.
To see it in emulationstation you just need to add some roms to the mame folder in ~/Retropie/roms. Be aware that mame4all needs a 0.37b5 romset so make sure that the roms you are using are the right ones (google can help you with that).
As soon as mame appears in emulationstation you can choose a rom and start playing. You can press “tab” on your keyboard in the emulator to change the button layout. You don’t have to change any config files by hand.

[Mutex]

I compiled it on a recent raspbian image (on rpi2b). Are you using the picodrive core for sms emulation? it has lots of problems with several roms (i.e. shinobi). Osmose works way better but has it’s own problems (hangs everytime I exit the emulator, it’s not a libretro-core, so you have different controls, and the runcommand.sh is borked and breaks with osmose). I switched to the genesisplus-gx core (used for game gear emulation in retorpie). It works way better for sms games than the picodrive one.

[Mutex]

Just tried it with the GenesisPlus-GX libretro core. Had no problem to get into the game.

[Mutex]

I’d say try starting a game and check which layout fits best for you. If you try games like gunstar heroes, or contra you will have 3 different actions for the buttons. And those games use more or less “standard” controller layouts (i.e. shoot is the same button as in most other games). Other games like comix zone or castlevania have different button actions but can be reconfigured in the options.

[Mutex]

Press your hotkey-utton (Select, the one used for exiting emulators, but not the start-button) and press f1 on your keyboard to open the rgui. Check the core-options for the 6-button option in your megadrive core. The default controller for the megadrive/genesis only has 3 buttons, so it’s normal that the other buttons don’t do anything.

[Mutex]

Maybe the executable has no execution rights

If that’s the case this should fix it:
sudo chmod +x opt/retropie/emulators/pisnes/snes9x

You can remove the entries from the gamelist.xml in ~/.emulationstation/.
There’s also a folder with downloaded images and since emulationstation by default just looks for roms that have no image set it will skip those.
If you just moved the rom to a different folder after scraping the path to the rom set in the gamelist.xml is wrong and starting them shouldn’t work.

[Mutex]

The new folder structure in retropie needs root privileges. So you either get a basic understanding of unix and move the files manually from /home/pi to /opt/ or you have to access the system with the root user. So log into your raspberry pi and do what InsecureSpike suggests in this thread.

[Mutex]

[quote=11954]the hotkeys do not work for mame, as mame still uses its own config it seems, so if i have my keyboard plugged in i just do the whole “tab” thing and go from there. But i don’t want to use a keyboard every time i want to configure a game for mame, also it doesn’t save any changes i make. how can i get mame to use the same settings as everything else?[/quote]

The mame emulator cannot save the config since you’re running mame as pi user. The config folder in the mame emulator belongs to the root user, so you’re not allowed to make any changes to that folder. The easiest thing would be to run mame one time by hand as root user
/opt/retropie/emulators/mame4all-pi/mame
configure your controls by pressing [tab] and then restart emulationstation. The pi should now have your new controls saved. The other solution would be to change the ownership of the config file but that is a bit more complicated.

[Mutex]

If you have the “new” retropie image (2.0 and higher) the retropie folder moved to /opt/retropie/. So you have to move the gba.bios to /opt/retropie/emulators/gpsp/raspberrypi/

[Mutex]

Just start the retropie_setup script again and select source install.
In the list that follows you can mark every emulator that you want to be installed (by pressing space), but that will take its time again so…
If you want it faster just select the binary based install and remove all the emulators you don’t need. If theres an update to one of the emulators you can still select sourcebased install and only install that one.

[Mutex]

/opt/retropie/configs/all/retroarch.cfg

But check first that these lines aren’t already in there.

[Mutex]

What emulator (for which system) are you trying to quit?

[Author]

Posts