[Floob]

The video above should help.

But in short, get to a terminal screen on the Pi and type the following (assuming you have a Pi 2 Model B)

wget https://github.com/sselph/scraper/releases/download/v0.7.4-beta/scraper_rpi2.zip
then
sudo unzip scraper_rpi2.zip scraper -d /usr/local/bin/
then
scraper -scrape_all -thumb_only

[Floob]

Are you sure your 0.37b5 romsets are correct?
You can verify that by using the dat files on this page:
https://github.com/retropie/RetroPie-Setup/wiki/Managing-ROMs

In RetroPie 3, those roms should go here:
/home/pi/RetroPie/roms/mame-mame4all

As the game starts to boot, you should get the option to press “x” this lets you choose if you want to run it with mame4all-pi or Mame-libretro. I tend to use mame4all-pi.

More details here:

MAME versions and romsets on RetroPie

[Floob]

No, youre nuts. :)

Or maybe not.

To start with, what emulator are you running neogeo with? FBA or gnGEO?

Have you checked your romsets with the details on this page?
https://github.com/retropie/RetroPie-Setup/wiki/Managing-ROMs

[Floob]

This link and video may help:

(Link shows what version of MAME works with which emulator – details at bottom of wiki)
https://github.com/retropie/RetroPie-Setup/wiki/Managing-ROMs

You will see in link above that fba-libretro can use romsets from 2014, so pretty recent.

[Floob]

I’d be sorely tempted to upgrade/re-install to the latest version 3 if thats practical.
There have been a lot of improvements.

[Floob]

I’d recommend using sselphs scraper. It is currently far better than the built in ES one.

https://github.com/sselph/scraper

[Floob]

In RetroPie 3 its in:
/opt/retropie/configs/mame-mame4all/cfg/default.cfg

[Floob]

What command did you type?

Change to this directory
cd /opt/retropie/emulators/retroarch/configs

then list it with “ls”

Then you can edit the file with
“sudo nano insertfilename.cfg”

The two vids above explain it better.

[Floob]

The game save files are the .srm, and the save states that RetroArch can use directly are the .state files.

This should help:

How to save games in RetroPie / RetroArch

[Floob]

I’d recommend going back to the clean image as you have edited the retroarch.cfg files quite a bit. You could put them back how they were but may well be easier starting again.

When you configure the retroarch joypad from the menu, it updates the controller file in this directory.

/opt/retropie/emulators/retroarch/configs

This is referred to in the main retroarch.cfg file
/opt/retropie/configs/all/retroarch.cfg in these line

input_autodetect_enable = true
joypad_autoconfig_dir = /opt/retropie/emulators/retroarch/configs/

If you start editing the retroarch.cfg its very easy to screw this up.

Rule of thumb is if you want auto detection etc.. keep the default truned on.
If you want to heavily customize the controller for each system, do it in the system config directories, I’d really try to leave retroarch.cfg alone.

I *think* your joypad is the USB_Gamepad_.cfg file

This video should help

You can double check your controller settings with jstest

[Floob]

Press TAB to configure the controls when your game has loaded

[Floob]

I’ll stick my neck out and say FBA romsets dont use/reference CHDs.
There is no reference in the dat files anyway, plus check this out:

http://www.epforums.org/showthread.php?81371-Are-CHD-files-important

[Floob]

[quote=94251]
i thought if i changed the path to an external hd i have (with the chd’s on it), that it would work but i get the same file not found error. the line in question is in the following file:

/opt/retropie/configs/mame-advmame/advmame.rc

the line is:

dir_image /media/MAME106/chds

[/quote]

That .rc filename doesnt look quite right – I think (in RetroPie 3) there are 2 rc files in there one for 1.2 and one for 0.94 – do a “ls” in that dir to confirm.

You can get it to search multiple paths by separating each one with a :

So you could have
dir_image /opt/cheese:/opt/biscuits:/home/pi:/media/MAME106/chds

if you wanted.

[Floob]

[quote=94247]Floob, great input. For FBA chd’s would we assume
/opt/retropie/configs/fba/image
?[/quote]

Nope – FBA works a little differently I think. If you give me a game example I can check.

[Floob]

Thats odd – I’ve set some emulator specific settings in the relevant retroarch.cfg and it certainly seems to be reading them. For example I set some specific shader for the Megadrive and it kicks in quite happily.

[Floob]

Create your CHD folder in here:
/opt/retropie/configs/mame-advmame/image

So yours would be
/opt/retropie/configs/mame-advmame/image/area51/area51.chd

I’ll let you worry about how to get a lightgun working :)

[Floob]

Default gamelists are sent here:
/home/pi/.emulationstation/gamelists/{systemname}

If you dont use ES to scrape, the gamelists will often be in the rom dir.

[Floob]

[quote=94156]HI all,

I can’t seem to get any games that require CHD’s to load, it always says the file was not found. i have tried putting the cud in the rom folder, also in it’s own folder within the rom folder but still the same can’t find the file error.

anyone been able to get cud games to load with advMAME on a pi?

thanks
[/quote]

Which game have you tried? I’ll try it on mine.

[Floob]

The user “Roo” is the expert here, but essentially:

– Every MAME version released supports certain romsets
– A romset is a .zip file with various roms inside, i.e. dumps of the graphics, sounds etc.. within a given game.
– Romsets can change from one version of MAME to another, i.e. a new or improved rom may be added, or one removed.
– So trying to use the 0.160 set of romsets may well not work with an older version of mame, because the contents of the romsets may differ.
– The dat files contain the names of the roms that should exist in each romset, therefore you can build a romset based on one or many other versions.
– The rebuilding process copies out the relevant roms to create new romsets

The most current arcade emualtor on RetroPie is the libretro-fba.

[Floob]

Did clrmamepro pass your roms as 100% correct with the dat file?

[Floob]

Have you scraped with sselphs tool?

[Floob]

You can “rebuild” the 037b5 set using this guide:
https://github.com/retropie/RetroPie-Setup/wiki/Managing-ROMs

You should be able to rebuild most of it from the 0.160
The rebuild will create it from nothing, it just copies out the bits it needs from the source set.

You may find roms called “MAME – Rollback ROMs” helpful as that would contain the differences between 0.160 and changes made previously.

Dont forget there are other arcade emualtors available on RetroPie

MAME versions and romsets on RetroPie

[Floob]

Have you selected to run fba-libretro by pressing “x” when you start the game?

[Floob]

[quote=94084]Warning, according with the source, Final Burn Alpha v0.2.97.30 romset is synched with MAME v149 instead of v154.[/quote]

I went by the info on this page:
http://www.barryharris.me.uk/article_view.php?id=198

[Floob]

[quote=94036]Could anyone explain the process of moving the ROMs to the correct destination?[/quote]

There are paths set here:
https://github.com/retropie/RetroPie-Setup/wiki/MAME

You can copy the roms here using the normal method, FTP, USB etc..

[Floob]

General overview of setting shaders here:

[Floob]

FBA uses the same filenames as MAME, so run “scraper -mame”

Works for me.

[Floob]

That looks good, I’ll try them out.

Here is the shader you recommend (I need to sort my TV colour out):
http://youtu.be/_oGZhLsbTGs

Here is my config file based on your suggestions
/opt/retropie/configs/megadrive/retroarch.cfg

#include "/opt/retropie/configs/all/retroarch.cfg"
# All settings made here will override the global settings for the current emulator core
input_remapping_directory = /opt/retropie/configs/megadrive/

video_shader = /opt/retropie/emulators/retroarch/shader/crt/crt-hyllian-glow/crt-hyllian.glsl
video_shader_enable = "true"
video_smooth = "false"

video_crop_overscan = "false"
video_scale_integer = "true"
aspect_ratio_index = "21"

[Floob]

I’d agree, as there are so many changes from 2.6 to 3, just use the new image.

Upgrading in the future should be cleaner as the config files are a lot tidier now.

[Floob]

Thats sort of tricky as it would have to save it to the same filename as your set – which could work for mame, but tricky for consoles that have different names, but the same hashes. Even with mame it wont know which romsets you have decided to use.
You can grab your images from emumovies.com – sselphs scraper can use these locally store images and then it just grabs the metadata and doesnt need to download the image.

But in short, I’d just grab it with a scraper – you only have to do it once, and it takes about 5 mins per system.

[Floob]

Does this suggestion help?

PS3 bluetooth controller, correct method for retropie 2.3?

You may want to keep an eye on the datestamp and contents of this file, as this is what should hold your controller setup for ES.
/home/pi/.emulationstation/es_input.cfg

[Floob]

What happened when you tried to run a game before? The roms should just load unless they arent the correct version.

You can check they are the right version with clrmamepro:
https://github.com/retropie/RetroPie-Setup/wiki/Managing-ROMs

The dat files can be found in that link as well.

If you install 3.0.0 beta 2 mame4all is already installed (its already on all the RetroPie builds). The version 3 seems pretty stable, I’d run with it, but 2.6.0 is fine as well.

[Floob]

2.3.0 comes with mame4all already installed, so dont try a source install.

Also, mame4all will never show in the menu, the graphic is always “MAME” – it will still run mame4all there just is no need for a specific graphic.

The wiki you reference mentions where the directories already exist – no need to create them. They give the examples for RetroPie 2.6.0 and 3.0.0

To be honest I’d suggest using the 3.0.0 image.
Then you put your mame4all (0.37b5) roms here:
/home/pi/RetroPie/roms/mame-mame4all

If you want to use the 2.3.0 image, the roms go here:
/home/pi/RetroPie/roms/mame

[Floob]

A stock version of /opt/retropie/configs/all/retroarch.cfg should be fine.
Yours seems tweaked.

Try making these changes
xinput_player1_a = x
to
input_player1_a = x

Put a hash # at the start of these lines

input_player1_l2 =
input_player1_r2 =
input_player1_l3 =
input_player1_r2 =

Remove these lines (as your setup is pulling them from the auto config anyway)

input_enable_hotkey_btn = 8
input_exit_emulator_btn = 9
input_menu_toggle_btn = 5

Check this for multiple controllers:

[Floob]

The iBuffalo should work fine out of the box with 2.6.0

So on the tutorial you followed:

RetroPie: Build Your Own Raspberry Pi Retro Gaming Rig

Go to step 11 and undo that. Then try again.

[Author]

Posts