Development of module-script generator for lr-mess, lr-mame and mame standalone

Folly

The script has been updated to use the mame 0.245 data.

Within the 0245 database the lightgun data has been added.
So it's now possible to install the arcade category "lightgun".
Because there are no vertically playable lightgun roms the "lightgun90º" entry's are missing.

Although the category lightgun exists now, there are no artwork files or overlays files yet to support the sinden lightgun.
So if you want to make use of that, you still have to add that manually.

From the restricted part 122 of 329 lightgun games are available.

testudo

@Folly
Added the latest add-mamedev-systems.sh scriptmodule (0245.02) on my Ubuntu system and I am getting this error when trying to add new systems:

/home/testudo/RetroPie-Setup/scriptmodules/supplementary/add-mamedev-systems.sh: line 806: /home/testudo/RetroPie-Setup/scriptmodules/supplementary/add-mamedev-systems.sh: line 791: /usr/bin/dialog: Argument list too long: syntax error: operand expected (error token is "/home/testudo/RetroPie-Setup/scriptmodules/supplementary/add-mamedev-systems.sh: line 791: /usr/bin/dialog: Argument list too long")
/home/testudo/RetroPie-Setup/scriptmodules/supplementary/add-mamedev-systems.sh: line 809: /home/testudo/RetroPie-Setup/scriptmodules/supplementary/add-mamedev-systems.sh: line 791: /usr/bin/dialog: Argument list too long: syntax error: operand expected (error token is "/home/testudo/RetroPie-Setup/scriptmodules/supplementary/add-mamedev-systems.sh: line 791: /usr/bin/dialog: Argument list too long")

Any idea on what I have done wrong?

Folly

@testudo

I am aware that there is somehow one bug in the script, only when using a x86 or x86_64 cpu or other OSes.
The bug was there from the start of the front-end.

The issue is that when you want to display all the systems, and install one from there, then the error occurs.

When selecting system in alphabetical order there should be no problem

So :
Are you able to go into front-end ?
Did you select to install a default system from the whole list ?
Do the other menu options work ?

testudo

@Folly

Yes, I was attempting to access the full list of default systems. It has been awhile since I added anything new, so I may have forgotten that bug existed.

Anyway, I am able to use the alphabetical listing options and get systems added, so all good now.

Thanks for the instructions.

Folly

@testudo

Not sure why the error occurs because on a raspberry pi it's no issue.
Perhaps I will dig in it once more.
On the other hand, is it a solution to just remove the menu options 1 and 2 ?
What do you think ?

testudo

@Folly said in Development of module-script generator for lr-mess, lr-mame and mame standalone:

@testudo

Not sure why the error occurs because on a raspberry pi it's no issue.
Perhaps I will dig in it once more.
On the other hand, is it a solution to just remove the menu options 1 and 2 ?
What do you think ?

Removing the menu options seems like a logical fix, be it temporary or permanent.

Folly

@testudo

Seems I found the issue and did an update :
https://github.com/FollyMaddy/RetroPie-Share/commit/e23e2a058872b2a8c05f391ef4020c8bcde092e1

Can you test it for me ?

EDIT :
Just tested both "description list" and "systems list".
Seems the issue is in the"description list".
So the error is not fixed yet.
I will have a second look ;-)

Folly

@testudo

I turned "Display all upon descriptions" off for x86 and x86_64 PC's.
You will now get a message.
Can you test it for me ?

https://github.com/FollyMaddy/RetroPie-Share/commit/8bbaa26a88521183fe1330c1e31ec02ba190e36f

testudo

@Folly said in Development of module-script generator for lr-mess, lr-mame and mame standalone:

@testudo

Seems I found the issue and did an update :
https://github.com/FollyMaddy/RetroPie-Share/commit/e23e2a058872b2a8c05f391ef4020c8bcde092e1

Can you test it for me ?

EDIT :
Just tested both "description list" and "systems list".
Seems the issue is in the"description list".
So the error is not fixed yet.
I will have a second look ;-)

@Folly

I received the following errors:
script errors.png

Folly

@testudo

Yes, I know, the earlier commit didn't fix anything.
In the last commit "Display all upon descriptions" will now only work on arm cpu's.
Can you update to 245.05 and see if you get a message instead of the error ?

testudo

@Folly said in Development of module-script generator for lr-mess, lr-mame and mame standalone:

@testudo

Yes, I know, the earlier commit didn't fix anything.
In the last commit "Display all upon descriptions" will now only work on arm cpu's.
Can you update to 245.05 and see if you get a message instead of the error ?

Looks like it worked:

Screenshot from 2022-08-09 08-32-23.png

dmmarti

@Folly … I don’t use my RetroPie build much anymore (mainly use my Windows PC now), but I had a look at some of your previous posts and decided to test a few things out.

I’ve now been able to add support for Videoton TV 64 using floppy disks. This opens up a few more games using the latest MAME software list for tvc_flop. I’ve been playing Galaxy alot lately now.

Here’s the stand alone MAME command I used:

mame tvc64 -exp1 hbf -flop1 “Path/To/Rom/game.dsk”

Once the system is started, instead of using the cassette command of:

LOAD <enter>

Use this instead:

LOAD"*" <enter>

You might have already did this system, but I wasn’t sure. By looking at the -listslots for tvc64 I was able to deduce how to add floppy support. There are quite a few games in the tvc_flop software list that are pretty fun.

Folly

@dmmarti

Nice find !
I did not test this system driver.
I will have a look at that one.

Folly

I updated all links in the first post.
So when hovering over the link the correct post is displayed.

Folly

@dmmarti

I have tried galaxy too, looks nice.
Placed tvc64.zip and tvc_hbf.zip in BIOS/mame.

I have added tvc64 + flop1 support in >EXTRA<

https://github.com/FollyMaddy/RetroPie-Share/commit/2fa04f814fcf1088757d05b3834ecb3fd8a58aeb

Folly

@DTEAM

Here is some news about handheld vfd games :
https://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=97003&page=397

Looks like we need to update our roms in the next version.

mitu

@Folly just a heads-up - the name of the lr-mess core file has changed, due to an upstream re-organization. It's now mamemess_libretro.so instead of mess_libretro.so.

Folly

@mitu

Thanks, I will have a look at it.

Folly

To everyone who is using this project,

The name of the core mess_libretro.so will change into :
mamemess_libretro.so

For future compatibility I will add these changes to version 245.08 of add-mamedev-systems.sh .

Though when we do nothing we still face these other problems :

old emulators.cfg will still have the name mess_libretro.so in them
when still using the older mess_libretro.so, new installed systems, generated by 245.08, will not work because it will generate for mamemess_libretro.so
be aware of the fact that old generated module-script still contain the old mess_libretro.so name, so try to not install an old module-script

I decided to not implement fixes because they will be somewhat temporary.
So, here are some commands to make the switch to 245.08 :

#make a backup of all your configs files for security in /opt/retropie/configs.bak
sudo cp -a /opt/retropie/configs /opt/retropie/configs.bak
#change all mess_libretro.so entry's into mamemess_libretro.so entry's in all emulators.cfg files
find /opt/retropie/configs/ -name emulators.cfg|while read file;do echo "change mess_libretro.so into mamemess_libretro.so in $file";sed -i 's/\/mess/\/mamemess/g' $file;done
#change the name of the old mess_libretro.so 
#(can be possibly skipped when installing the latest lr-mess core with the name mamemess_libretro.so)
sudo mv /opt/retropie/libretrocores/lr-mess/mess_libretro.so /opt/retropie/libretrocores/lr-mess/mamemess_libretro.so

https://github.com/FollyMaddy/RetroPie-Share/commit/9aac70fbd6f3a31cca08a7e3563fe1b2362182cf
https://github.com/FollyMaddy/RetroPie-Share/commit/daa630e325475ac3712cbe568354e30cdaf0311e

bbilford83

Hi all,

This whole project is just amazing, and I can't express enough gratitude to everyone who got it running - I now have nearly a dozen new systems on my build I didn't have before.

I am having one issue that I can't find addressed by searching the thread, which is that whenever I try to change the standard "video mode" for any of the systems I installed via this project, it makes the system not work and loads a gray screen (similar to what happens when you don't have bios, but it doesn't say I am missing files). I have a home pi system and a piboy, and on the piboy everything works great because the standard resolution is set to always be 800x600 to match the screen's max capability. But my home TV is 4K, so I have to change the default video mode to something less (I usually use 87-9, which is 1920x1080). When I don't do that, even low-impact systems have screen tearing and other problems.

I can't remember the specific name of the loading screen where you choose the resolution/video mode but this is a photo of what I mean:

I can't figure out for the life of me why this is an issue or how to get around it, but changing the third option breaks any of the lr-mess systems. Any tips?