@shift I don't have dedicated threads for each individual lr-mess system I run, but the short answer is "more-or-less all of them".

Just to rattle off some of the ones I've tried on my Pi, with decent-to-perfect performance:

Phillips CD-i Epoch Super Cassette Vision V.tech V.Smile Various plug-and-play systems (both "official" and bootlegs) Tiger Game.com Fujitsu FM Towns

Once you get down how the core works (which admittedly is a bit of a nightmare), it's insanely versatile since it runs all the same systems as modern standalone MAME (according to the current docs, that's roughly 32,000; that link at the top is a good few years out of date). Arguably the most powerful core in all of RetroPie.

@theburgerking said in Integrating lr-mess quasi-cores into RetroPie-Setup:

Is there an lr-mame core? Could I build one? I have used lr-mess both prebuilt and built from source and I see from its build script that it just pulls from https://github.com/libretro/mame.git.

Yes. Both lr-mess and lr-mame are built from the same codebase you mentioned (forked upstream MAME), but with different build options, which results in different supported systems (arcade vs. non-arcade).
I was referring to MAME (the upstream project), not the libretro cores.

Does this mean that mame itself is the part of the mame distribution that can run that system?

Upstream MAME distributes only 1 binary which supports all systems included - either arcade, computer, mechanical, etc. There's no separate MESS anymore and I think hasn't been for quite some time.

Yep, same error. If I'm understanding that thread correctly, the only way around it is to have an older version of MAME? Which you cannot obtain unless you had a backup of it?

@Folly Heh. Yes. I'm guilty of being old. I was way better with all this just 7 years ago. Anyway thank you so much once more for your help!!! I'll be using this right away!

THANK YOU @dankcushions !

Your pointer was half of the solution so let me write the other half in case anyone else searches for this answer.

Setting the resolution in the retroarch Options menu did not have any effect until I also turned on "Alternate render method" in the same menu. At that point all resolution changes took immediate effect (upon leaving the retroarch UI) and now this all works perfectly.

I will write up the rest of my method to launch rom-less system soon!

Thanks again.

I am going to answer this one myself in case anyone else needs this info in the future. After looking through the run_mess.sh script itself, I was able to see that the message "hn613128pc64.bin NOT FOUND (tried in pv2000)" was trying to tell me that lr-mess was looking for the BIOS file in a pv2000 subdirectory of the main BIOS directory. Once it was placed there the logic to skip the software list/hash started working properly and I was able to launch roms that did not match the official hashes.

@dteam said in CD-I does not want to load after updating Retropie:

@folly said in CD-I does not want to load after updating Retropie:

Which files do you actually mean ?

zx405037p__cdi_servo_2.1__b43t__llek9215.mc68hc705c8a_withtestrom.7201
zx405042p__cdi_slave_2.0__b43t__zzmk9213.mc68hc705c8a_withtestrom.7206

Thanks.

I downloaded the BIOS and the new hash file for MAME 0.223 and everything is working!

SOLVED

@janderclander14

Thanks for the fps check.
For the sound, It depends, for some 2D games, the sound is not that bad (not far from a good experience).
In the Hash file , located in the BIOS/mame/hash folder , they commented slightly on the playability.
Some games are not playables even on both emulators.
I'm running Zool 2 or Bubsy at 49 FPS with Lr-Mess and 33 FPS with Lr- virtualjaguar (Big difference)

The RetroPie setup script already allocates 4G (see here), but I think the recent changed in upstream MAME have increased the memory needed for a successful compilation.

I solved this in the end by downloading the neokobe collection (all 90gb for the SECOND TIME) and making CHD's with an old version of Chdman.

Nostre, how are you launching thegames? I have a 'proper' chd with the disk name 'Galaxy Force II" and then one dummy chd with the name of the entry in fmtowns_cd.xml - something like gforce2. All games will launch from the dummy chd. Now i've successfully rebuilt mess i'm not sure the check sums need to match.

So far i've found:

Galaxy force and Genocide, pu-ra-li-ra panic bomber man and Afterburner 3 are both extremely playable with decent sound

4d sports, Chase HQ, Turbo Outrun and Flashback play but with compromised sound.

Its a shame Unz is closed source.

I finally figured it out, and in case anyone needs to know for future reference:

Option 1: Go into "Slot Devices" by pressing TAB to get into the MAME config menu and choose "Joy" under "ctrl2" - This is not set by default.

Option 2: Add -ctrl2 joy to your command line in emulators.cfg - This will force a controller to put put into controller port 2. So for example, my command line for Astrocade looks like this:

lr-mess-astrocade = "/home/pi/RetroPie-Setup/scriptmodules/run_mess.sh /opt/retropie/emulators/retroarch/bin/retroarch /opt/retropie/libretrocores/lr-mess/mess_libretro.so /opt/retropie/configs/astrocade/retroarch.cfg astrocde /home/pi/RetroPie/BIOS -ctrl2 joy -cart %ROM%"

@mitu Wow 30 hours... brutal!
Thx for all the info, that's all that i needed, i considered thread solved.

@Raleighguy The concurrency is set automatically, based on the #of CPUs you have and the system you're running on. On a PI3, it's probably 2, since it doesn't have enough memory and CPU anyway to sustain 4 compilation threads.

@BuZz After waiting for FBA to get neocd support, I finally got around to trying it. It doesn't support chd and it doesn't support cd audio. Any chance for a binary of lr-mess in the future? It takes over a day to compile and tends to fail the last time I tried, and atm it seems to be only emulator with proper neocd support.