"No Config Found For X System" on Multiple Consoles

AlphaBetaPie

UPDATE

So after circling back around on this thread some time later (by Googling my issue and stumbling onto my own thread), I figured I'd resurrect this one instead of cluttering up the forum with more topics.

So I'm trying to get Mame running on my pie, but I'm having some trouble. Base on my official image install, it looks like I didn't have a default Mame emulator installed (or if I did, it was Mame4All I believe). I did an update via source, but it doesn't seem to be working still. Or I may not have my emulators config file pointed at the right thing. Anyone have any issues getting Mame to work right out of the box, or is there any easy fix I'm overlooking?

dankcushions

@alphabetapie all official images have a mame install. if you used retropie-4.5.1-rpi2_rpi3.img it would have installed lr-mame2003 which creates the /opt/retropie/configs/mame-libretro and ~/RetroPie/roms/mame-libretro folders , etc. what makes you think you don't have it? what exactly did you update via source?

it was indeed the issue. The system was generating the codes in the ETC version of es_systems. I had a copy in OPT, which I use to only list the systems currently installed

why do you have a copy in opt? unless there's a specific reason, you're just giving yourself additional work every time you add a system.

AlphaBetaPie

@dankcushions said in "No Config Found For X System" on Multiple Consoles:

@alphabetapie all official images have a mame install. if you used retropie-4.5.1-rpi2_rpi3.img it would have installed lr-mame2003 which creates the /opt/retropie/configs/mame-libretro and ~/RetroPie/roms/mame-libretro folders , etc. what makes you think you don't have it? what exactly did you update via source?

it was indeed the issue. The system was generating the codes in the ETC version of es_systems. I had a copy in OPT, which I use to only list the systems currently installed

why do you have a copy in opt? unless there's a specific reason, you're just giving yourself additional work every time you add a system.

Thanks for following up. So I went back and retraced my steps, looks like the original mame-libretro folder was moved or deleted in some other theme work I was doing. So the first thing I did, was just uninstall Mame4All (which is what I had updated from source original to get it, thinking I needed it), and then reinstalled mame-libretro from source to get all my files back. So that put everything back where it should be. Also, to answer your other question, I was advised to put a copy in OPT to prevent overwrites from future updates. I also use this copy to rearrange the sort order of the consoles, and I get a permissions error/problem when I try to use the other.

The problem is, I'm still not having any luck launching anything. I have two folders in my roms directory; arcade and mame-libretro. Both have the mame2003 folder inside. I put my roms in the root directory of each, and have pointed the line of the cfg file dealing with mame roms to both folders during different attempts, but they still won't load. Here is my current setup, tell me if I'm missing something.

<system>
<name>mame-libretro</name>
<fullname>Arcade</fullname>
<path>/home/pi/RetroPie/roms/mame-libretro</path>
<extension>.zip .ZIP</extension>
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS mame-libretro %ROM%</command>
<platform>arcade</platform>
<theme>arcade</theme>
</system>

mitu

This post is deleted!

dankcushions

@alphabetapie

The problem is, I'm still not having any luck launching anything.

what do you specifically mean by this? please provide a verbose log - my guess is incorrect romset.

editing the opt version of es_systems.cfg is fine, and there shouldn't be any debate about the right format as you can just reference the one in etc if you're confused. for reference, mine looks like:

  <system>
    <name>mame-libretro</name>
    <fullname>Multiple Arcade Machine Emulator</fullname>
    <path>/home/pi/RetroPie/roms/mame-libretro</path>
    <extension>.zip .ZIP</extension>
    <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ mame-libretro %ROM%</command>
    <platform>arcade</platform>
    <theme>mame</theme>
  </system>

so yours looks fine at a glance.

AlphaBetaPie

When I say it won't load, I mean I can select a game from my list, but then it crashes back to the previous menu of my theme. All my other consoles load fine. After hearing what you said about wrong rom sets, I'm thinking it might be that. I did not use a rom auditor to pick my zip files, but rather found the ones with the county/naming conventions in the file name and compared them to online databases (to try and pick the version and country I wanted). Not sure how I would correct that now, so if that is the case, I'll need some guidance there.

Here are the log files. I tried launching 1943 and Alien vs Predator. Here is what it said on both:

"Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003/mame2003_libretro.so --config /opt/retropie/configs/mame-libretro/retroarch.cfg "/home/pi/RetroPie/roms/mame-libretro/1943ua.zip" --appendconfig /dev/shm/retroarch.cfg"

and...

"Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003/mame2003_libretro.so --config /opt/retropie/configs/mame-libretro/retroarch.cfg "/home/pi/RetroPie/roms/mame-libretro/avspu.zip" --appendconfig /dev/shm/retroarch.cfg"

mitu

@alphabetapie You need to choose verbose logging when launching the roms to get more info. If the romsets are incorrect, the missing files will be logged there.

dankcushions

@alphabetapie said in "No Config Found For X System" on Multiple Consoles:

I did not use a rom auditor to pick my zip files, but rather found the ones with the county/naming conventions in the file name and compared them to online databases (to try and pick the version and country I wanted). Not sure how I would correct that now, so if that is the case, I'll need some guidance there.

i don’t know what you mean by “rom auditors” but the requirements for arcade cores are specific: https://retropie.org.uk/docs/Arcade/

and there are specific rom filtering methods for them: https://retropie.org.uk/docs/Validating%2C-Rebuilding%2C-and-Filtering-ROM-Collections/

assuming your verbose log reveals missing/incorrect rom files, rather than try to work with what you have i suggest starting from a complete non-merged romset collection for the romset version required for your emulator of choice, and then taking what you want from that.

AlphaBetaPie

I'm still working on getting the verbose logging set up, as I originally disabled all these input commands at launch in the setup I'm working on (to make it more of a kiosk-style, where only the games themselves are accessible). I'll try to walk this back and get the run command to work again, so I can launch with verbose logging (but I'll have to check my notes and try to remember what I did). Unless someone knows how to get the run command to launch a ROM with verbose logging without the input press at the launch?

dankcushions

@alphabetapie said in "No Config Found For X System" on Multiple Consoles:

I'm still working on getting the verbose logging set up, as I originally disabled all these input commands at launch in the setup I'm working on (to make it more of a kiosk-style, where only the games themselves are accessible). I'll try to walk this back and get the run command to work again, so I can launch with verbose logging (but I'll have to check my notes and try to remember what I did). Unless someone knows how to get the run command to launch a ROM with verbose logging without the input press at the launch?

the process to re enable runcommand is on the same doc as the verbose log instructions - https://retropie.org.uk/docs/Runcommand/

it's simple - just do that.

AlphaBetaPie

So I went ahead and tried to work the problem from the outside in. Instead of digging back through several of my edits and changes to my RetroPie scripts so figure out which one disabled the run command prompt, I just went and found a Mame 0.78 rom set. I swamped out a few of the roms that wouldn't load the last time with ones from this set and BOOM. All is good now! So thanks for that tip. This issue forced me to learn a bit more about MAME rom emulation vs regular console emulation (which I didn't realize was so different).

Speaking of which, did run into one other issue that I figured I can just leave here, instead of starting a new thread.

About 75% of the games I had in my list were found in the Mame 0.78 set. But several were not. I'd say about 20+ (and they aren't even on the newer side, like mad dog mcgee, space invaders, etc). It's possible I just overlooked some, but most I know I can't find. So what is another good set with a wider range of roms that will also work like the Mame 0.78 did (if I were to just drop in those few I'm still missing)?

dankcushions

@alphabetapie said in "No Config Found For X System" on Multiple Consoles:

About 75% of the games I had in my list were found in the Mame 0.78 set. But several were not. I'd say about 20+ (and they aren't even on the newer side, like mad dog mcgee, space invaders, etc). It's possible I just overlooked some, but most I know I can't find. So what is another good set with a wider range of roms that will also work like the Mame 0.78 did (if I were to just drop in those few I'm still missing)?

what do you mean in your "list"? the games mame2003 supports are the ones in the dat - which is linked here

mame2003 only supports 0.78. fbneo supports many additional games, and is also recommended for as per the docs. the later versions of mame retropie supports support more games still, but the cores are less mature.

AlphaBetaPie

@dankcushions Are there any systems/cores available in retropie that are compatible with rom set .226? That is the one I started on this originally.

dankcushions

@alphabetapie you can see the supported MAME versions on same page: https://retropie.org.uk/docs/MAME

note .226 is current MAME or thereabouts. current MAME will perform badly on pi systems right now.