mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support
-
@barbudreadmon I take it you mean by using ClrMamePro? I have followed this tutorial and watched a couple on youtube, but nothing gives me a usable rom.
I am not at all versed in the inner workings of ClrMamePro, so, honestly, I don't really know what I'm doing when rebuilding, but no matter what DAT-file I use in the profiler, I keep getting sent back to Emulationstation when launching the resulting game.
When I rebuild using the 'mame2003-plus'-DAT (which actually is an xml-file), I end up with a 1kb version of spacefev.zip. When I only scan the rom, I never get any useful information and the 'fix' option also seems to do nothing with it.
Any pointers would be welcome. TIA
-
@WeirdH Isn't Space Launcher archive named
spacelnc
?spacefv
is Space Fever.I see that even though the game appears to be added, it's not in the
.xml
available on the Github, you'll have to generate the.dat
file from the Emulator - https://docs.libretro.com/library/mame2003_plus/#step-1-obtaining-an-xml-dat. -
@WeirdH - Space Fever (spacefev) should be around 7kb since you're file is 1kb I would guess you missing ROMs. Even though you run it through a ROM management utility doesn't necessarily mean it will build the correct set. You might be missing ROMs. Which program are you using? Did you get any missing ROM errors?
Here's what should be in the zip file. The filename and more importantly the hash:
<game name="spacefev"> <description>Space Fever (New Ver.)</description> <year>1979</year> <manufacturer>Nintendo</manufacturer> <rom name="f1.bin" size="1024" crc="35f295bd" sha1="34d1df25fcdea598ca1191cecc2125e6f63dbce3" region="cpu1" offset="0"/> <rom name="f2.bin" size="1024" crc="0c633f4c" sha1="a551ddbf21670fb1f000404b92da87a97f7ba157" region="cpu1" offset="400"/> <rom name="g1.bin" size="1024" crc="f3d851cb" sha1="535c52a56e54a064aa3d1c48a129f714234a1007" region="cpu1" offset="800"/> <rom name="g2.bin" size="1024" crc="1faef63a" sha1="68e1bfc45587bfb1ee2eb477b60efd4f69dffd2c" region="cpu1" offset="c00"/> <rom name="h1.bin" size="1024" crc="b365389d" sha1="e681f2c5e37cc07912915ef74184ff9336309de3" region="cpu1" offset="1000"/> <rom name="h2.bin" size="1024" crc="a163e800" sha1="e8817f3e17f099a0dc66213d2d3d3fdeb117b10e" region="cpu1" offset="1400"/> <rom name="i1.bin" size="1024" crc="00027be2" sha1="551a779a2e5a6455b7a348d246731c094e0ec709" region="cpu1" offset="1800"/> <rom name="ss3.ic2" size="1024" crc="95c2c1ee" sha1="42a3a382fc7d2782052372d71f6d0e8a153e74d0" region="cpu2" offset="0"/> <rom name="f5.bpr" size="32" crc="c5914ec1" sha1="198875fcab36d09c8726bb21e2fdff9882f6721a" region="proms" offset="0"/> </game>
@mitu - Thanks for the link! I had no idea there was a nice tutorial with the steps.
-
@WeirdH said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
When I rebuild using the 'mame2003-plus'-DAT (which actually is an xml-file), I end up with a 1kb version of spacefev.zip. When I only scan the rom, I never get any useful information and the 'fix' option also seems to do nothing with it.
clrmamepro won't magically create files from nothing, it'll just verify your romsets and tell you what's wrong with them
-
@mitu said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
@WeirdH Isn't Space Launcher archive named
spacelnc
?spacefv
is Space Fever.Yes, that's right. ClrMamePro reads spacelnc.zip and then outputs spacefev.zip. It was one of my points of confusion.
@Riverstorm said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
@WeirdH - Space Fever (spacefev) should be around 7kb since you're file is 1kb I would guess you missing ROMs. Even though you run it through a ROM management utility doesn't necessarily mean it will build the correct set. You might be missing ROMs. Which program are you using? Did you get any missing ROM errors?
Yes, ClrMamePro created the zip-file with only one actual file in it. It also thought it was another game. I believe it matched spacelnc to my mame2003-plus profile and only found spacefev as closest match or something (if I'm even interpreting the workings of ClrMamePro correctly). I got no missing errors, just some skipped files. Then again, I might not have been looking at the right output, as I'm a complete noob when it comes to CMP.
@barbudreadmon said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
clrmamepro won't magically create files from nothing, it'll just verify your romsets and tell you what's wrong with them
Okay, that much I had gathered. But the tutorial I linked (I believe it's by Herb Fargus) mentioned the 'rebuild' option to create a rom for the right version of Mame. Other tutorials also claimed a non-working rom could be made to work this way in ClrMamePro. Again, I don't really know what I'm doing, aside from following steps.
I assumed it worked like this: I use Mame2003-plus, but my spacelnc.zip is for a later version of Mame. I then load the Mame2003-plus DAT-file as a profile in CMP and tell it to match the rom against that. If not matched, the rebuild option would correct the version of the rom, making it launchable in Mame2003-plus. How incorrect is my assumption? (because it probably is :D)
@mitu said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
I see that even though the game appears to be added, it's not in the
.xml
available on the Github, you'll have to generate the.dat
file from the Emulator - https://docs.libretro.com/library/mame2003_plus/#step-1-obtaining-an-xml-dat.Thanks. I'll try and fiddle some more with it.
-
@WeirdH said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
the rebuild option would correct the version of the rom, making it launchable in Mame2003-plus. How incorrect is my assumption?
Again, files won't be created magically, rebuild will just try to rebuild the romsets from dumps scattered in another directory, but a missing dump is still a missing dump. The trick to be able to rebuild any romset for whatever version of mame you want is to have the mame romsets & the corresponding rollback romsets (they are a collection of all the dumps that got previously discarded by mame).
-
@WeirdH - You're close. It doesn't match the whole zip but each individual file in the zip if that makes sense. It will attempt to rebuild the set but it still needs the correct ROMs to do it.
So for example if you use the Rebuilder as mentioned and specify a source path(s) to ROMs. You can have more than one here. There are many options available but just do the basics for now.
Also don't get caught up in the XML format. There's way more formats than you can shake a stick at for different things.
It will attempt to validate the ROMs from the source path(s) provided against the DAT provided and then rebuild the set in the target folder provided.
It will scan through each source folder looking for the specific ROM(s) belonging to each game zip.
If it finds a match it will add it to the correct game zip. If the game zip doesn't exist it will create it. Name is irrelevant because it could be named incorrectly inside any zip in the source folder so it searches each and every zip for a match by hash. When it finds a file match it will rename it accordingly to the DAT specifics.
Not to throw things off but the only thing that really matters is the zip archive name. The names inside a zip really don't matter. This is a cool "feature" that can be exploited to your advantage later.
In your case it found a matching hash for one file in your version of spacelnc and added it spacefev.
If that matching file had belonged to 15 game zips it would have created and/or added it to 15 game zips even though they are partial game zips. It's basically trying to build a complete set even if it's only a partial set.It then continued looking through your source folders provided and found no other other matches. So you have a partial ROM (spacefev) with one file hence it crashes back to Emulationstation due to missing ROMs.
Basically you're missing files and need to find the correct ones. Don't get caught up in name because they change so it's really about the file hash with ClrMamePro unless one isn't provided in the DAT. You'll see missing SHA1 info. etc. sometimes.
If you can't find a pre-built set anywhere with the correct ROMs then current MAME and the rollback set will build an almost complete set.
There's a a few minor exceptions noted below that aren't official MAME ROMs and need to be tracked down separately for a perfect mame2003-plus set.
Bubble Bobble (Ultra Version)(USA) [folder: bublboblu - parent: bublbobl - size: 548kb] a78-05u.52 [size: 65536] [CRC32: b31d2edc] [SHA1: b7d317c0b5b86c0bf39b18cfe584bca9d22d4eba] a78-06u.51 [size: 32768] [CRC32: a6345edd] [SHA1: 144f33002ee40acdbfa6a49119092a319048bb00] a78-08u.37 [size: 32768] [CRC32: d544be2e] [SHA1: 1472db52dcd9e17a866ea2766cfea500d8f712ab] Donkey Kong Remix [folder: dkrdemo - parent: dkong - sampleparent: dkong - size: 33kb] dkrdemo.5at [size: 4096] [CRC32: e59d406c] [SHA1: 7698e319ae191bb8bf7deeea5c4f18da04d73f73] dkrdemo.5bt [size: 4096] [CRC32: 660d43ec] [SHA1: 8bba334cec022ea851c4a82f6ecbc91c0708daea] dkrdemo.5ct [size: 4096] [CRC32: f48cb898] [SHA1: 470b8bee7f55e1d828abc0b1ec4b423392c83a78] dkrdemo.5et [size: 4096] [CRC32: f9fdff29] [SHA1: c2eb8f0ede8384369e17d8616f4ce063ae12b6c2] Hyper Street Fighter II: The Anniversary Edition (Asia 040202) [folder: hsf2a - size: 45mb] hs2ax.03 [size: 524288] [CRC32: 5f3d7397] [SHA1: 96f327dd998105ad5dc46bc9d3b741805a840d68] hs2ax.04 [size: 524288] [CRC32: 59acf108] [SHA1: e68fe233681175b29a35badab249c2b892b23af3] SegaSonic Bros (Japan, prototype) [folder: ssonicbr - size: 640kb] ssonicbr.ic31 [size: 262144] [CRC32: 03709746] [SHA1: 0b457f557da77acd3f43950428117c1decdfaf26] ssonicbr.ic32 [size: 262144] [CRC32: cf254ecd] [SHA1: 4bb295ec80f8ddfeab4e360eebf12c5e2dfb9800] ssonicbr.ic4 [size: 131072] [CRC32: 78e56a51] [SHA1: 8a72c12975cd74919b4337e0f681273e6b5cbbc6] The King of Fighters 2003 (Decrypted) [system: Neo-Geo - folder: kof2003d - size: 125mb] 271-v1d.bin [size: 16777216] [CRC32: 2964f36e] Tron (freeplay) [folder: tronfp - parent: tron - size: 108kb] 625_v11.bin [size: 8192] [CRC32: 402a99dc] [SHA1: d3fdf877f185473d3dbf33cd1a3d0dae4173e479]
-
@Riverstorm said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
There's a a few minor exceptions noted below that aren't official MAME ROMs and need to be tracked down separately for a perfect mame2003-plus set.
Yeah, mame2003-plus includes some non-MAME roms.
-
@Riverstorm
Cool, thanks for the thorough explanation, it makes more sense now.
@mitu said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
I see that even though the game appears to be added, it's not in the
.xml
available on the Github, you'll have to generate the.dat
file from the Emulator - https://docs.libretro.com/library/mame2003_plus/#step-1-obtaining-an-xml-dat.Thanks. I'll try and fiddle some more with it.
When I generate my own from 2003-plus, I still get an xml that makes no mention of Space Launcher (and I updated all packages yesterday). Am I out of luck, DAT-wise?
-
@WeirdH - Did you update mame2003-plus from source first? It's in the RetroPie setup menu Manage Packages -> Manage Experimental Packages? I created a new DAT last week and it's in there.
<game name="spacelnc"> <description>Space Launcher</description> <year>1979</year> <manufacturer>Nintendo</manufacturer> <rom name="sl_f1.f1" size="1024" crc="6ad59e40" sha1="d416f7e6f5f55178df5c390548cd299650853022" region="cpu1" offset="0"/> <rom name="sl_f2.f2" size="1024" crc="2de568e2" sha1="f13740d3d9bf7434b7760e9286ef6e2ede40845f" region="cpu1" offset="400"/> <rom name="sl_g1.g1" size="1024" crc="06d0ab36" sha1="bf063100b065dbf511d6f32da169fb461568d15d" region="cpu1" offset="800"/> <rom name="sl_g2.g2" size="1024" crc="73ac4fe6" sha1="7fa8c09692446bdf804900158e040f0b875a2e32" region="cpu1" offset="c00"/> <rom name="sl_h1.h1" size="1024" crc="7f42a94b" sha1="ad85706de5e3f952b12756275be1ea1276a10666" region="cpu1" offset="1000"/> <rom name="sl_h2.h2" size="1024" crc="04b7a5f9" sha1="589b0a0c8dcb1300623fe8478f1d7173b2bc575f" region="cpu1" offset="1400"/> <rom name="sl_i1.i1" size="1024" crc="d30007a3" sha1="9e5905df8f7822385daef159a07f0e8257cb862a" region="cpu1" offset="1800"/> <rom name="sl_i2.i2" size="1024" crc="640ffd2f" sha1="65c21396c39dc99ec263f66f400a8e4c7712b20a" region="cpu1" offset="1c00"/> <rom name="sl_sound.ic2" size="1024" crc="8e1ff929" sha1="5c7da97b05fb8fff242158978199f5d35b234426" region="cpu2" offset="0"/> <chip type="cpu" name="8080" clock="2520000"/> <chip type="cpu" soundonly="yes" name="I8035" clock="400000"/> <chip type="audio" name="DAC"/> <chip type="audio" name="SN76477"/> <video screen="raster" orientation="vertical" width="224" height="256" aspectx="3" aspecty="4" refresh="60.000000"/> <sound channels="1"/> <input players="2" control="joy8way" buttons="1" coins="1"/> <dipswitch name="Lives"> <dipvalue name="3" default="yes"/> <dipvalue name="4"/> <dipvalue name="5"/> <dipvalue name="6"/> </dipswitch> <driver status="good" color="good" sound="imperfect" palettesize="2"/> </game>
-
@Riverstorm Well, I must have gone from binary then. I'll go check it out. Thanks again!
-
@barbudreadmon Yup, just read about rollback sets. This has been an educational day for me. Thanks for your replies.
-
@Riverstorm It works now, Space launcher up and running. Thanks, any and all, for your help.
-
@WeirdH said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
@Riverstorm It works now, Space launcher up and running. Thanks, any and all, for your help.
Well done you got there in the end :) BTW how do the colours look.?? Space Launcher was one of arnold's additions, i would have added the colour prom from Space Fever as per this change
0.82u2: Stefan Jokisch decided to add the color prom from Space Fever to Space Launcher.
-
@arcadez2003 Well, glad you asked. Something's definitely up: everything is white, like a vanilla Space Invaders without any background artwork. The sound is also not right, when compared to gameplay on youtube: it plays a looping riff unless you press the button and there are no explosions. I must have done something wrong still...
EDIT: I did manage to get Match It 2 running perfectly, though, so I don't know what's wrong with Space Launcher.
-
@WeirdH said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
@arcadez2003 Well, glad you asked. Something's definitely up: everything is white, like a vanilla Space Invaders without any background artwork. The sound is also not right, when compared to gameplay on youtube: it plays a looping riff unless you press the button and there are no explosions. I must have done something wrong still...
EDIT: I did manage to get Match It 2 running perfectly, though, so I don't know what's wrong with Space Launcher.
This is what i getting with arnold's code in my MAME72 test build.........
Sound is borked though, when i drop the same rom into my MAME84 emu Space Launcher is in colour and the sound is fine, this update is what will sort everything
that is wrong with Space Launcher and the other games which share the same hardware.......0.82u2: Added vidhrdw\n8080.c and sndhrdw\n8080.c. Nintendo 8080 hardware update [Stefan Jokisch]: The driver has now been split into three parts (drivers, sndhrdw\ and vidhrdw\n8080.c).
0.80u2: Added n8080.c driver. Stefan Jokisch update the Nintendo 8080 based games. Added Space Fever, Space Fever High Splitter, Space Launcher, Sheriff / Bandido and Helifire from the 8080bw to the n8080 driver. Fixed CPU speed, unified memory maps and changed ROM labels in all games.
13th March 2004: Stefan Jokisch sent in an update to the early Nintendo 8080 games driver, fixing a lot of bugs and graphics glitches in the individual games.Alotta graft but i might take this one on and plod away at it since it's classic Nintendo we're talking about here.
-
Hi guys, thanks for all your work it's fantastic.
But i have a problem, i launch your core, go to the menu generate the DAT XML to try some rom set, i try on PI Batocera and on PC Windows and i can't found the dat file anywhere ???
Where is it generated please?
If you van give me the actuel one it can help a lot, but i would like to understand because i see you will release a new great update in a near future ....
Thanks -
@darknior said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:
Where is it generated please?
"if your roms are in /RetroPie/roms/mame-libretro/
your dat will be in
/RetroPie/roms/mame-libretro/mame2003-plus/ mame2003-plus.xml"(from this post)
-
@WeirdH Yes i've think to this and search in /userdata/roms/mame froam Batocera and it is not here :(
Same on PC shere i drag n drop my rom file ...
I will try on my Retropie but if you can share the file here.
Thanks -
I've try on my Retropie and same :(
Not there : /home/pi/RetroPie/roms/Arcade
Not there : /home/pi/RetroPie/roms/mame
Not there : /home/pi/RetroPie/BIOS/mame2003-plusIf some one can share his file, really i don't understand :(
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.