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

[Folly]

@bbilford83

I had a look and these drivers and the descriptions from mame are :

• Driver jak_dwmn (Dreamworks Movie Night (JAKKS Pacific TV Game, Oct 18 2006, prototype)):
• Driver jak_dwmno (Dreamworks Movie Night (JAKKS Pacific TV Game, Apr 24 2006, test program)):
• Driver jak_sith (Star Wars - Revenge of the Sith (JAKKS Pacific TV Game, Game-Key Ready)):
• Driver jak_sithp (Star Wars - Revenge of the Sith (JAKKS Pacific TV Game, Game-Key Ready, prototype)):

Seem that they are indeed somewhat obsolete.
However I can't filter them out so it's probably best to include them.

[bbilford83]

@Folly I am happy to put in duplicates but do you think it makes more sense to leave them out? Or I guess I can say these are outdated/earlier versions of the same games? For me I wouldn't want a prototype if the final is available but I understand some might.

FYI I moved onto the All_in1 and I am so far not very optimistic. There's soooooo little info out there about these compared to Jakks or the Classic Handhelds, I'm not sure I could make a decent gamelist. And honestly at least so far they've all just been bootleg compilations, so I can see why there wouldn't be tons of info out there about them. I may at the end keep only ones that aren't bootleg compilations and that I can find information about, but I would assume you wouldn't want my gamelist then and would prefer the generic-if-barebones one you have up there now?

[Folly]

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

@Folly I am happy to put in duplicates but do you think it makes more sense to leave them out? Or I guess I can say these are outdated/earlier versions of the same games? For me I wouldn't want a prototype if the final is available but I understand some might.

Thanks.
I think we should keep them in.
I like the idea that the collection is most complete and it will save me time to filter it out (if I should be able to).

FYI I moved onto the All_in1 and I am so far not very optimistic. There's soooooo little info out there about these compared to Jakks or the Classic Handhelds, I'm not sure I could make a decent gamelist. And honestly at least so far they've all just been bootleg compilations, so I can see why there wouldn't be tons of info out there about them. I may at the end keep only ones that aren't bootleg compilations and that I can find information about, but I would assume you wouldn't want my gamelist then and would prefer the generic-if-barebones one you have up there now?

I agree,
All_in1 is too difficult to describe all.
In my perspective the generic-if-barbones will do.

Just an idea :
It's possible to add your gdrive to the script just like with the one of DTEAM so one could choose between one and the other.
A sort of alternative with a few differences and some other system.
For me it would make sense to put it in as a gdrive with "wip - work in progress" predefined gamelists.
So in time stuff that goes to the grdrive of DTEAM can be deleted on your gdrive (if you want) and stuff that won't go the gdrive of DTEAM is an addon for the users.
Do you like that idea ?

[bbilford83]

@Folly That would be fine with me, whatever you think makes sense. I think I am pretty much done with the gamelists now actually... I was trying to give Pico and a couple others a shot but they're not really workable for a variety of reasons. So you are welcome to use them however you see fit, I hope they're helpful!

[DTEAM]

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

Just an idea :
It's possible to add your gdrive to the script just like with the one of DTEAM so one could choose between one and the other.
A sort of alternative with a few differences and some other system.
For me it would make sense to put it in as a gdrive with "wip - work in progress" predefined gamelists.
So in time stuff that goes to the grdrive of DTEAM can be deleted on your gdrive (if you want) and stuff that won't go the gdrive of DTEAM is an addon for the users.
Do you like that idea ?

I'll update my drive with @bbilford83 additions (comments and upgrades) , I'll try to do that next week.

Does somebody is able to run UBOAT from MAME 0.259. On my side, it won't load.
Bandai U-Boat [hap, Sean Riddle, eggs] ROM name= UBOAT

[Folly]

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

Does somebody is able to run UBOAT from MAME 0.259. On my side, it won't load.

It does load (on my x64 vm) however the controls do not seem to work correctly for P2. ( not tested on my pi yet )
For player 2 left and right are flipped. (key d and key g)
I think the destroyer is above and the uboat below.
The destroyer shoots from top to bottom and the uboat seems to shoot in the upper screen from left to right.
Perhaps we have to look at the manual.

How did you download it, manual from mame-merged or did you use my restricted option ?

Edit :
I found the manual on archive (manuals-handheld-games-Bandai-UBoat)
The flipped player2 controls make some sense as it looks there are 2 screens in oposite direction.

[DTEAM]

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

How did you download it, manual from mame-merged or did you use my restricted option ?

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

[Folly]

@DTEAM

That runcommand works for me too.

My question was a different one and is your rom ok ?
Is your mame version on 259 now, can you check ?

[DTEAM]

@Folly

Mame-merged

[Folly]

@DTEAM

Just curious.
Do you do that always manually ?

[DTEAM]

@Folly
Most of the time yes , but not all the time.

[Folly]

@DTEAM

Ok, know enough

Not sure why it doesn't work will check on my pi later.
Did you check your log ?

[DTEAM]

@Folly
Not yet, I'll do it tomorrow

[Folly]

@DTEAM

FYI, It works on my pi.

[bbilford83]

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

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

I assume it should work the same as the art currently downloaded by the script - i.e. move the zip to bios/mame/artwork and it will automatically load?

Yes, but as far as I can see for mame standalone it will be :
roms/mame/artwork
For lr-mame / lr-mess I think it would be :
BIOS/mame/artwork

@Folly, I decided to give this one more try and I made .zip artwork files for two more games based on the ones you did. I am not sure they will work - I was really struggling along in Gimp - but then when I went to test them none of them seem to work anyways. Nothing automatically loads when I add the artwork to either folder, and I think it is because these are software list roms rather than "mainline" mame roms, if that makes sense. Game and watch, Tiger, Konami, and ClassicH (all of which I can use the art) are all "normal" mame roms, so I think that is why it is different. But everything I can find online isn't helping me figure out how to make it work. Wondering if you have any ideas?

I am not confident my artwork will work anyway but I will give it a shot if I can :).

[Folly]

@bbilford83

I assume you are talking about the microsvn artwork.
Did you try mine first without editing ?
Can you share it in your folder with the pictures ?
Then I can take a look.

[bbilford83]

@Folly Yes, sorry, the microvsn artwork. I tested yours before the others I made, mame isn't picking up any of them. I goofed around trying other ideas (I thought maybe a subfolder first with "microvsn" but no). I tried a bunch of searches to see how the art would differ for software list roms but didn't find anything helpful. But it makes sense that it wouldn't just work, because I assume some of the rom filenames in software list systems are the same (as each other and as some arcade roms).

I added yours + the two I made to a subfolder in my gmail folder you linked. I stopped trying to make more because I'm super slow and don't know if they're going to work... I'm not rearranging anything in the layout file and just trying to place the correct new artwork over the old ones in the one you made.

Edit: Truth is I'm not sure it matters anyway, I can't for the life of me get the games to control/be playable. I mapped all 12 buttons and still can't seem to get anything to play, it seems to me like the paddle at the bottom just isn't moving even though it's registering the input properly in mame. So I may be giving up on the system even if we get the art working :).

[Folly]

@bbilford83

I looked at your files.
I see what the problem is.
You can't use these names, you have to integrate all all gameviews inside one artwork file called microvsn.zip.
So use only 1 layout file.
Take a look at the vectrex.zip I added.
That's the only way it will work with the regular runcommands.
Mame doesn't pick up artwork by softlist names by default only artwork with driver names.

[bbilford83]

@Folly Interesting, thank you! This did get the art to load, but it won't remember the art game-by game.... i.e. when I set it and exit it, it defaults to the first art layout in the .lay file the next time you load it. When you use the art in regular mame (i.e. non-software list roms) it remembers your art choice in each game... I guess there's no way to make it differentiate between the different games here?

I think for the same reason I can't set controls game-by-game. In regular mame when you set it by "system," so for Tiger etc. I was able to map the controls to what made sense for each game. That's even more necessary here since there are twelve possible "buttons" but most games only use six or fewer. Right now I have all 12 buttons mapped and it will save across all the microvision games, but I if I try to remap in any of the games it remaps for all of them :(.

In any case it seems a moot point for me, I still can't get the games to control properly. I'll keep trying a bit but probably will give up sooner or later.

Note also the two other artworks I made work, but the baseball one is supposed to overlap the screen, and because I can't figure out how to set the opacity it's not working right (it's just blocking the whole screen).

Even though I don't think I'm going to figure this out I might as well document what I did in case someone more clever comes along...

[Folly]

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

@Folly Interesting, thank you! This did get the art to load, but it won't remember the art game-by game.... i.e. when I set it and exit it, it defaults to the first art layout in the .lay file the next time you load it. When you use the art in regular mame (i.e. non-software list roms) it remembers your art choice in each game... I guess there's no way to make it differentiate between the different games here?

Yes, it will load now and the disadvantage is that you have to select the view every time.
Although it's possible to load the artwork you want is possible in the runcommand.
You can see here what the options are :
https://docs.mamedev.org/commandline/commandline-all.html
I have experimented with this earlier.
There are some things to solve this issue.
However it probably means an extra runcommand load option or adding stuff to my patched runcommand.sh.
So if we want to implement we or I have to look at this again.

I think for the same reason I can't set controls game-by-game. In regular mame when you set it by "system," so for Tiger etc. I was able to map the controls to what made sense for each game. That's even more necessary here since there are twelve possible "buttons" but most games only use six or fewer. Right now I have all 12 buttons mapped and it will save across all the microvision games, but I if I try to remap in any of the games it remaps for all of them :(.

Yes, correct that somewhat the same reason.
For this problem you can use my game-specific runcommands.
Have a look when you load the rom and then select a the game-specific runcommand, that should solve your problem.

In any case it seems a moot point for me, I still can't get the games to control properly. I'll keep trying a bit but probably will give up sooner or later.

If I gave up we didn't have my beautiful script.
Of-course it will take a lot of time but it's worth it.
Mame has a very steep learning curve but once you know it it's quite easy to understand.
It's the same with gimp, man that's a good program.
Sometimes I let it rest for a while and pick it up later again.
That works almost all the time and just be patient.

Note also the two other artworks I made work, but the baseball one is supposed to overlap the screen, and because I can't figure out how to set the opacity it's not working right (it's just blocking the whole screen).

You have to do it in an other way.
You have to use the magic tool to select the things you want to get rid of.
In this case you should not use opacity.

Even though I don't think I'm going to figure this out I might as well document what I did in case someone more clever comes along...

Making a summary is always a good thing.
I would like to motivate you to push your boundaries.
Remember you can't do it all in one day you have to take the time for stuff.
Learn one thing and then go to the other things.