Development of module-script generator for lr-mess, lr-mame and mame standalone
-
@xxcitoxx as mitu already pointed out... That's a no-no. Google is your friend with everything related to ROM/BIOS files. Might take some time, but you'll find everything.
-
@jamrom2 said in Development of module-script generator for lr-mess and mame standalone:
@folly I've been finishing up my CoCo2 list, and working on my CoCo3 now. I'm going to make a dedicated Tandy CoCo3 logo as well as I think it's warranted to seperate the two visually rather than just a Tandy logo.
I'll play around with this tonight as well.
Nice to hear !
The CoCo2 list, is that a gamelist with media showing in emulationstation ?
If so, we should add it to the google-drive of @DTEAM, so everyone can download it in the script.
Can we make that possible ? -
@folly I don't know if that would help anyone as far as meta-data. It's my gamelist based on whatever I named or used, so their ROMs would need to match whatever I have in my file.
As much as I would love to share it all, it's definitely not a full list, and it's a lot of hand-picked games.
But I will admit, I've done everything I can to use the best versions of box art I could find for every game system I have. I've even made some of my own when needed.
-
I understand, all those different files and filenames can be a problem.
Is it an idea to make a separate thread for making shareable ES gamelists with media and try to make some solutions for dealing with above issue ?
-
@folly said in Development of module-script generator for lr-mess and mame standalone:
I understand, all those different files and filenames can be a problem.
Is it an idea to make a separate thread for making shareable ES gamelists with media and try to make some solutions for dealing with above issue ?
Yes, it's a good idea but we should do that for MAME roms (.zip and .7z) only. Otherwise there are too many different kinds of roms names for a single game.
-
@dteam said in Development of module-script generator for lr-mess and mame standalone:
@folly said in Development of module-script generator for lr-mess and mame standalone:
I understand, all those different files and filenames can be a problem.
Is it an idea to make a separate thread for making shareable ES gamelists with media and try to make some solutions for dealing with above issue ?
Yes, it's a good idea but we should do that for MAME roms (.zip and .7z) only. Otherwise there are too many different kinds of roms names for a single game.
Yes, that's a good start.
I will make a new thread.
I think we should reserve the first 4 posts for summarization.
So I will take the first and the second posts.
Can you take the third ?
And @jamrom2 should take the fourth.That way all 3 of us can be the "admin" for the thread.
The first can then redirect to the second,third and fourth post so we can all can be the "admin" of the thread or splitting up some summarisation tasks.Good idea ?
-
-
@folly
I'll modify what I wrote in my third post depending what you will write in your first post. -
That's ok.
Lets see how it evolves, we are quite flexible now. -
-
@folly Sounds good to me.
At this point, we'll need to post instructions on how this all works and some known issues like performace, interaction with command for certain auto-load cycles, and what keys might need to be remapped.
I think we can offer a basic list of gamelist.xmls based on what we tested with? Most of the TOSEC and other archived games are where people pull ROMs from. It's the other websites I used that might be a problem...and we can't point to those saying "use this site or our files".
-
@jamrom2 said in Development of module-script generator for lr-mess and mame standalone:
At this point, we'll need to post instructions on how this all works and some known issues like performance, interaction with command for certain auto-load cycles, and what keys might need to be remapped.
That is indeed something that should be added.
We have multiple possibilities on how we can do this :
- add "instructions" to the script
- add instructions to the first post
- or separate the instructions to a new thread
We will have to think about it how we want to structure it.
-
I vote for keeping it all in the thread we are making. It will be easier for users to keep open and work with the Pi/files at the same time....and easier for us to update as needed.
-
Good argument, let keep it here.
-
-
I think you might be interested and I would like to ask you if you can test my latest commit to this script.
Read post 1 on how to install)I merged the knowledge of my old Philips CDI script to this script now.
Basically when cdimono1 is installed then some patched configs are written to get :- working mouse and mouse buttons
- full 4:3 screen without small display
- above fixes to work with lr-run_mess and plain media and basename lr-mess loaders
To use the basename loaders you can use this structure :
pi@raspberrypi:~/RetroPie/roms/cdimono1 $ find -name "arc*"
~/RetroPie/roms/cdimono1/arcadecl.zip <=empty dummy file
~/RetroPie/roms/cdimono1/arcadecl/arcade classics (1996)(namco - philips)(eu)[compilation].chd@jamrom2 @DTEAM
Do you both like it too ?
Have some fun.I did quite some testing and everything should be ok.
In above process I enable mouse for basename loaders for all systems too.
This could be an improvement when we load games, that use mouse, with the basename loaders in general.
But it can also mean that we run into some issues with some systems.
For the custom media loaders it was already enabled from the beginning and we never had any issues so I think we are good.Can you both let me know if you run into problems ?
-
@folly said in Development of module-script generator for lr-mess and mame standalone:
@jamrom2 @DTEAM
Do you both like it too ?
Have some fun.
I did quite some testing and everything should be ok.
In above process I enable mouse for basename loaders for all systems too.
This could be an improvement when we load games, that use mouse, with the basename loaders in general.
But it can also mean that we run into some issues with some systems.
For the custom media loaders it was already enabled from the beginning and we never had any issues so I think we are good.
Can you both let me know if you run into problems ?I'll try it today!
-
Downloading the gamelists and media with the script doesn't work correctly anymore.
I have encountered this problem here :
https://retropie.org.uk/forum/topic/32188/creating-es-gamelists-with-media-for-mame-lr-mess/13EDIT :
Problem has been solved :
MATT has updated his script, It's working again ;-) -
@folly said in Development of module-script generator for lr-mess and mame standalone:
@jamrom2 @DTEAM
Do you both like it too ?
Have some fun.
I did quite some testing and everything should be ok.
In above process I enable mouse for basename loaders for all systems too.
This could be an improvement when we load games, that use mouse, with the basename loaders in general.
But it can also mean that we run into some issues with some systems.
For the custom media loaders it was already enabled from the beginning and we never had any issues so I think we are good.
Can you both let me know if you run into problems ?It's nice!
I did a test with MSX2 (Sony ...) and Gamate. It works fine. Great job!! -
@Folly
Do you think It could be possible to have save state slots per game for MAME and not per system like lr-mess does? -
I was thinking that both mame and lr-mess made per game save-states.
Do have an example on what you do/what happens with both mame and lr-mess when making a save state ?
Which loaders do you use ? -
For Lr-Mess, it's libretro core. So that's fine. For MAME, they use the driver (system) and not the game. It seems to be ok for Arcade games but not for console.
NEW EDIT: I found something. In /opt/retropie/configs/
arcadearcadia
They create a custom-core-options.cfg file. Probably Valerino script Inside we can see:mame_saves = "game"
Maybe it's the solution.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.