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

bbilford83

Actually @Folly, I didn't know about the runcommand.log file before, that is obviously very useful! But looking at that now I don't think it is a bios problem. This is what it says:

But I do have lr-mess, mame, and mess all updated to current, so I thought it should "know" it is a working system?

Folly

@bbilford83

You can find the runcommand.log in /dev/shm.
Indeed this is probably a different issue, have you tried mame standalone ?

Can you check your version of lr-mess in the mame UI (about)

bbilford83

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

@bbilford83

You can find the runcommand.log in /dev/shm.
Indeed this is probably a different issue, have you tried mame standalone ?

@Folly yes, standalone cart, standalone basename, lr-mess, all kick me right back out.

Can you check your version of lr-mess in the mame UI (about)

In mame UI, about (loaded a diferent game), says MAME .261 (ILP32), Revision: 7d5e2708. Retroarch "information" says the same - MAME (.261 (7d5e2708).

Do I maybe need to update from source instead of binary? For any other newly-added systems/games so long as the .2XX number has matched it has worked for whatever was listed as newly-working so long as I updated to the current binary.

Folly

@bbilford83

Ok your version seems correct.
No need to update.
I would always install from binary.

Can you post me the runcommand of mame-basename from the emulators.cfg ?

BTW :
Noticed that I never tried lr-mess so I have to try later.

bbilford83

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

Can you post me the runcommand of mame-basename from the emulators.cfg ?

Of course, here you go:

mame-videoart-basename = "/opt/retropie/emulators/mame/mame -rompath /home/pi/RetroPie/BIOS/mame;/home/pi/RetroPie/roms/videoart -v -c -ui_active -statename videoart/%BASENAME% videoart %BASENAME% -view %BASENAME%"

Folly

@bbilford83

I don't see strange things in your runcommand.
Tested everything ok with mame and lr-mess with cart and basename.
Will think about it, have to work now.
So we will proceed later.

bbilford83

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

@bbilford83

I don't see strange things in your runcommand.
Tested everything ok with mame and lr-mess with cart and basename.
Will think about it, have to work now.
So we will proceed later.

Thanks, no rush. I was going to try a different romset but given the error in the runcommand it seems like it is probably not that either.

ladba1975

I have tried to run PMD-85 emulator on PI4, as shown in tutorial https://retropie.org.uk/forum/topic/32045/tesla-pmd-85-computer-in-retropie/23

However, it doesn't work: It is not possible to run "RetroPie-Setup" from emulationstation (to update scripts) after downloading the module-script file.

Previous I have successfully installed it on PI3.
Should the same steps work on PI4?

mitu

@ladba1975 I merged your topic to the one from where the scripts originated.

Folly

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

I have tried to run PMD-85 emulator on PI4, as shown in tutorial https://retropie.org.uk/forum/topic/32045/tesla-pmd-85-computer-in-retropie/23

However, it doesn't work: It is not possible to run "RetroPie-Setup" from emulationstation (to update scripts) after downloading the module-script file.
Previous I have successfully installed it on PI3.
Should the same steps work on PI4?

It looks like you have tried to downloaded an old module-script and it probably has the wrong or no content.
This can happen with a curl command when you don't have a good internet connection.
If an empty .sh file is in the RetroPie-Setup then the RetroPie-Setup will refuse to work.
Check where you have saved the add-systems-mamedev.sh file and remove it.
The file should still be on github and working however that script is deprecated.
I would suggest to check my first post and add the new mamedev.sh script.

Folly

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

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

@bbilford83

I don't see strange things in your runcommand.
Tested everything ok with mame and lr-mess with cart and basename.
Will think about it, have to work now.
So we will proceed later.

Thanks, no rush. I was going to try a different romset but given the error in the runcommand it seems like it is probably not that either.

Just tested on both mame standalone and lr-mess on rpi4 with original binaries.
Mame standalone works and lr-mess doesn't work.
So It's very likely that the driver videoart isn't correctly added to the non-arcade subtarget list of the source-code of lr-mess.
Probably why videoart doesn't work.
Can you check mame standalone again, I think it should work.
Here is the mess subtarget list in the source code :
https://github.com/libretro/mame/blob/master/src/mame/mess.flt
Can't find videoart it is clearly missing (misc/videoart.cpp) :

/opt/retropie/emulators/mame/mame -listsource videoart
videoart         misc/videoart.cpp

(above is the command to find the source of the driver)

I will check if other pure lr-mess binaries have the same issue.

The reason it worked for me on my x86_64 VM is that I use a full lr-mame/lr-mess binary from the libretro buildbot so all drivers are in there just like with mame standalone.

bbilford83

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

Can you check mame standalone again, I think it should work.

I did but it still boots out to emulationstation right away. Here's what the runcommand says.

(deleted)

Folly

@bbilford83

You should share your runcommand.log differently, use your gdrive .
Or use pastebin.com and make sure you burn it after a while.
(you can re-use your old post)

Have you added this bios too ? :
ef9365.zip

bbilford83

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

@bbilford83

You should share your runcommand.log differently, use your gdrive .
Or use pastebin.com and make sure you burn it after a while.
(you can re-use your old post)

Have you added this bios too ? :
ef9365.zip

I removed the screengrab since I think it wasn't showing anything relevant anyway.

I just added that bios, didn't know it was needed, and you are right, now it is working in mame standalone! Thank you. Though it is super slow for some reason, even with autoframeskip - I think that is something weird about my system though, you have said before mame should run faster than lr-mame but for me it never does.

Folly

@bbilford83

Looks like we found the issues.
Good to know it is working now although sad to hear your mame isn't running fast enough, really not sure why.

I would suggest you play with removing and adding the bios file I mentioned.
So you can see the difference in the runcommand.log.
Look for NOT FOUND then you know in which bioses mame will search.
If you use my option from the restricted you will notice that these bios names will be added in the form to get them from the list ultimately when proceeding.

For this videoart system only it's not really worth patching or add an issue for lr-mess right now.
I think we do need to check this in the future for both lr-mess and lr-mame if the new drivers are added thoroughly enough.

bbilford83

@Folly I should have been more clear, in the "games" standalone mame is always fast enough, but for Videoart and some other systems I've tested when I am in the in-mame menu it crawls, and has trouble even registering button presses. Not sure why. But the games are working, awful as they are :). I don't know if you would want it for the script but I did create a gamelist with images and descriptions... obviously there is nowhere to scrape it but I found the original manuals for each games and used the cover for an image and the little blurb on the back for a description.

Folly

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

@Folly I should have been more clear, in the "games" standalone mame is always fast enough, but for Videoart and some other systems I've tested when I am in the in-mame menu it crawls, and has trouble even registering button presses. Not sure why.

I have seen that issue before.
On my 64 bit (aarch64) Manjaro Arch linux build I have the same issue using the binary of stickfreaks or mine build on my Apple M1.
When I installed it from source on the pi4 the issue was gone.
(at least if I remember correctly)
Btw :
Did you start with a fresh image for your pi4 ?
If you used your pi3 image check your config.txt if it uses the correct video driver like this :

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

How much memory does your pi4 have ?
I would try to increase the gpu memory a bit in the config.txt when having a pi4 with less memory.
Because if you have a pi4 with 1 or 2Gb by default the gpu memory will also be lower than having a 4Gb or a 8Gb.
If this doesn't work then it could be that your pi4 just doesn't have enough memory.
But that is guessing.

But the games are working, awful as they are :).

Aha, good.

I don't know if you would want it for the script but I did create a gamelist with images and descriptions... obviously there is nowhere to scrape it but I found the original manuals for each games and used the cover for an image and the little blurb on the back for a description.

Sure, why not, add it to your gdrive and use the relative paths and the /media/emualtionstation folder just like the others.

bbilford83

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

When I installed it from source on the pi4 the issue was gone.
(at least if I remember correctly)
Btw :
Did you start with a fresh image for your pi4 ?
If you used your pi3 image check your config.txt if it uses the correct video driver like this :

I did start with the blank retropie image for pi4, never owned a pi 3.

How much memory does your pi4 have ?
I would try to increase the gpu memory a bit in the config.txt when having a pi4 with less memory.
Because if you have a pi4 with 1 or 2Gb by default the gpu memory will also be lower than having a 4Gb or a 8Gb.

4GB, so that probably isn't it. But maybe I will try installing from source if that helped you once, couldn't hurt to try. Thanks!

Sure, why not, add it to your gdrive and use the relative paths and the /media/emulationstation folder just like the others.

I again had done it my other way (with the images going where they scrape in retropie) but I think I fixed it properly, it should be there now with gamelist and art nested the way your script needs. Let me know if you see anything wrong, but otherwise feel free to use it however you'd like. FYI only there is no good similar picture for "activity cartridge" because it didn't come with a manual... it was basically a demo with "pages" from all the other 8 games.

bbilford83

And one other minor thing @Folly, by any chance did you ever figure out if there is a way to load a specific controller (or "unload" it) via the runcommand? It didn't end up that there were many msx games that needed it on the zemmix, but there are some on the Atari XEGS that you can't play without changing the controller to paddles. I can note in the gamelist entries that they require paddle controllers but obviously it would be nicer if it could be automated so you don't have to change it every time you play.

Folly

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

4GB, so that probably isn't it. But maybe I will try installing from source if that helped you once, couldn't hurt to try. Thanks!

Indeed, that is probably not the issue.
If you want to try to install from source then I would recommend to, at least, double the swap inside the mame.sh module-script otherwise it will probably fail.
Be warned it will take 5 hours or so.