MAME 0.249 ROM Mapping (Clones) project

[floatingyeti]

3 minutes ago, brudibru said:

Maybe a picture of Dolly, the cloned sheep who was technically an orphan  

 Thats a possibility.

I may just remove the <cloneof> info and list them all as parents.

Anyone using the merged set could download the orphans individually from the non-merged set.

split and non-merged users would already have them.

[r0man0]

here is my app to convert an xml file with clones to a rom mapping ini file :

https://mega.nz/file/zVRiTJDB#jTCDdYMIt4SZ8eB0litTHj5ow-kYF0thOcgEZsuR7kY

For the moment it's a beta version but if there is no issue i will set it as final

Let's go guys , test it !

[Creezz67]

12 hours ago, r0man0 said:

here is my app to convert an xml file with clones to a rom mapping ini file :

https://mega.nz/file/zVRiTJDB#jTCDdYMIt4SZ8eB0litTHj5ow-kYF0thOcgEZsuR7kY

For the moment it's a beta version but if there is no issue i will set it as final

Let's go guys , test it !

Awesome work as usual, though I am finding I have to exit out of the app every time I want to do a new xml, or the next one gets all scrambled up with incorrect data.

Once I exit and select new xml again, all works perfectly (and it is lightning fast)

[Creezz67]

On 12/21/2022 at 8:53 PM, r0man0 said:

here is the 54 clones (working) with parents (non working) for mame 0.250

 

25pacmano
bk001001
bronx
bship82
cashcatnz
cobram3
cobram3a
countrunb
dirtdasha
dirtdashj
dolphntra
dolphntrb
dsfdcta
goal92
incasunnz
itunlim
jansoua
kaypro2x
kgalaha
kollonc
macxl
magicrdeb
nzeroteam
nzeroteama
orao103
orchidmsnz
oscara5a
ougonhaib1
ougonhaib2
pcnfrk4mk
pengpaya
pengpayc
qnileb
qnilebr
qnilenl
qnilenz
retrsama
retrsamb
sbuggera
spk100
spk114it
spk115it
spk116it
spk116itmx
spkrform
swhr2a
toutangonl
ttmahjng
unicorndnz
v4psibc
v4psibcd
wamazona
x820
zerotm2k

There is even more than this.

alexkidd

kof2000

burnforc

Just a few more I have found, that if you switch ini to clone they both load.

[floatingyeti]

The only xmls with clone info are arcade(mame) systems.

I tested it on Sega Naomi and it was an easy straightforward process.

Sega Naomi.xml

Sega Naomi.ini

I might go through a non-arcade system like NES at some point to see how much work it would be to prep a none arcade xml for use with the app.

[floatingyeti]

4 minutes ago, Creezz67 said:

There is even more than this.

alexkidd

kof2000

burnforc

I'm confused because those are all currently parent roms.

Are you using an older database?

[Creezz67]

11 minutes ago, floatingyeti said:

I'm confused because those are all currently parent roms.

Are you using an older database?

I am using the latest 0.250 all games xml created by roman.

The parent won't load, but when you load the clone it works, also when you switch clone and parent on rom mapping they both load.

Maybe I am doing something wrong ?

[Creezz67]

16 minutes ago, floatingyeti said:

I'm confused because those are all currently parent roms.

Are you using an older database?

I needed to do the following to get them to work:

kof2000 to kof2000n
burnforc to burnforco
alexkidd to alexkidd1

This only seems to be a rom mapping issue, as when I turn it off they will load ok.

[Creezz67]

45 minutes ago, floatingyeti said:

The only xmls with clone info are arcade(mame) systems.

I tested it on Sega Naomi and it was an easy straightforward process.

Sega Naomi.xml 70.25 kB · 0 downloads

Sega Naomi.ini 2.67 kB · 0 downloads

I might go through a non-arcade system like NES at some point to see how much work it would be to prep a none arcade xml for use with the app.

Just so I know if I am doing something wrong, can you load up alienfnt using this rom mapping ?

Also club2k3.

when I try it throws an error (I am using a merged romset)

ps, both load fine with rom mapping disabled.

Thanks

[floatingyeti]

thats true for 25pacman because its a bad dump

25pacmano is the working clone

kof2000, burnforc, and alexkidd are all parents (and a more current version or set) than those clone versions

Since all three of those only have one older version clone, i suggest getting the non-merged version of them

They will load with no issue.

just replace only those three and you can keep using your merged set.

 

[floatingyeti]

2 minutes ago, Creezz67 said:

Just so I know if I am doing something wrong, can you load up alienfnt using this rom mapping ?

when I try it throws an error.

Thanks

Was using the outdated xml from hyperlist to test for Romano.  Someone probably uploaded a better one.

The one I'm using has all the clones removed and is a cropped list of only RetroArch (Flycast compatible) games.

[Creezz67]

9 minutes ago, floatingyeti said:

thats true for 25pacman because its a bad dump

25pacmano is the working clone

kof2000, burnforc, and alexkidd are all parents (and a more resent version or set) than those clone versions

Since all three of those only have one older version clone, i suggest getting the non-merged version of them

They will load with no issue.

just replace only those three and you can keep using your merged set.

 

Thanks, I just tested a non merged version and as you say it loads fine.

I have gone from spending 10 years only using a split set of roms, to merged ..... and now it looks like I am going to go to non merged !!!!

I think just for updating in future it will be better for me just to replace my entire merged set with non merged.

Thanks for info

[floatingyeti]

Just now, Creezz67 said:

I have gone from spending 10 years only using a split set of roms, to merged ..... and now it looks like I am going to go to non merged !!!!

I think your testing with the merged set proved it was more compatible with Rom Mapping.

Non-merged has every game separated like the split set (incredibly confusing name) so they work independently.

So, keep your merged set if you have the space because you might want to test the behavior of both sets with Rom Mapping.

If you discover anything new, please let me know.

[Creezz67]

16 minutes ago, floatingyeti said:

I think your testing with the merged set proved it was more compatible with Rom Mapping.

Non-merged has every game separated like the split set (incredibly confusing name) so they work independently.

So, keep your merged set if you have the space because you might want to test the behavior of both sets with Rom Mapping.

If you discover anything new, please let me know.

95% of games load fine with merged for me, but split doesn't work well at all.

I will test non merged and choose from the 2, based on if it plays the ones that won't load with merged set.

As I update every month, I don't want to mix non merged and merged roms, as it will get confusing over time.

fyi, tested club2k3 and alienfnt with non merged and both load fine !

[r0man0]

3 hours ago, Creezz67 said:

Awesome work as usual, though I am finding I have to exit out of the app every time I want to do a new xml, or the next one gets all scrambled up with incorrect data.

Once I exit and select new xml again, all works perfectly (and it is lightning fast)

ok , i've fixed this issue with a new beta :

https://mega.nz/file/vdxhRbSD#5oVm78knesDyta-3fhXvlo0huFgP5Ju4om_8gP63jq0

Please tell me if it's ok for you

[Creezz67]

21 minutes ago, r0man0 said:

ok , i've fixed this issue with a new beta :

https://mega.nz/file/vdxhRbSD#5oVm78knesDyta-3fhXvlo0huFgP5Ju4om_8gP63jq0

Please tell me if it's ok for you

No, it has not fixed it.

Did AAE, then this and this is what it generated (altered beast info at the bottom)

Altered Beast Collection.ini

[r0man0]

7 minutes ago, Creezz67 said:

No, it has not fixed it.

Did AAE, then this and this is what it generated (altered beast info at the bottom)

Altered Beast Collection.ini 3.22 kB · 1 download

Ok so , maybe that one :

https://mega.nz/file/DchEzArC#4-vhp36jd1l-iCqxFYet22WWn30T52d0VVJ4UWc4fWc

[Creezz67]

6 minutes ago, r0man0 said:

Ok so , maybe that one :

https://mega.nz/file/DchEzArC#4-vhp36jd1l-iCqxFYet22WWn30T52d0VVJ4UWc4fWc

Looks like that one did the trick

Thanks again for your excellent app

[r0man0]

4 minutes ago, Creezz67 said:

Looks like that one did the trick

Thanks again for your excellent app

Ok , thanks for testing

[Creezz67]

23 hours ago, floatingyeti said:

I think your testing with the merged set proved it was more compatible with Rom Mapping.

Non-merged has every game separated like the split set (incredibly confusing name) so they work independently.

So, keep your merged set if you have the space because you might want to test the behavior of both sets with Rom Mapping.

If you discover anything new, please let me know.

** FIXED FYI, Non merged set also work with Roman0's rom mapping ini files.

 

[floatingyeti]

14 hours ago, Creezz67 said:

FYI, Non merged set do NOT work with Roman0's rom mapping ini files.

I have now tried 6 different systems and all of them just bring up one single rom, instead of all the clones.

When they are switched back to merged roms all working again.

Only a MERGED MAME romset will work with his ini files.

There is nothing wrong with Romanos ini or the app that generates them. This is more an issue with Rocketlauncher and it not having the versatility (Rom Mapping) required to make this process user-friendly

I have tested on merged/nonmerged/split and it works

I am attempting to replicate the issue you are encountering (using non-merged) but I'm unable to.

There will only be an issue (with any romset option) if clones are not present within the parent rom (merged) or individually (split or non-merged)

Let's look at Zeroteam for example

Using Romanos ini and non-merged set:

All non-merged parent/clones are present and the list is generated (all games launch)

here are my RM settings:

This will work with "First Matching Extension" set to "True" or "False"

So Non-merged (in this scenario) works

Obviously, I can't dismiss the issues you are experiencing so let's go over a scenario where non-merged rom mapping doesn't work.

Here's what happens if non-merged zeroteam is present, but the non-merged clones are removed:

It crashes! 

Using MAME 0.250 it never gets past the Fade screen. I waited 5 minutes and there wasn't even an eventual error message. I couldn't even "end process".

Using RetroArch (MAME 0.250) it at least crashed to an error message and didn't completely lockup my PC.

It has nothing to do with the database or Romano's ini file (it is correct).

This behavior or (Rocket Launcher) bug will occur with non-merged or split set if all clones are not present.

It's not so much an issue with the split set because most people would have the entire set in their rom folder

I do think it's a flaw (that should be fix by RL devs) for the non-merged set.  One of the best features of the non-merged set is that all roms are "portable" and you can have a functional incomplete romset if you choose.

But there still is some versatility. Rom Mapping will work (non-merged) if it can find at least one listed clone.

 Let's look at zeroteam again with one clone removed from roms folder:

And it does work (with one less clone displayed)

 

Creezz67 were you testing only the non-merged parent rom without the non-merged clones in your rom folder?

I do think you should continue using the merged set because it is working for you, and you prefer it.

Sorry for the long explanation, I just didn't want anyone reading the thread to think that non-merged doesn't work with Rom Mapping.

I can't say it's the "best" option (it's purely subjective), but I do feel the need to document it as a usable option.

[floatingyeti]

Has anyone else reading this thread tried Rom Mapping with MAME?

I know Creezz67 and Romano have successful used it? Romano's ini tool has made it more accessible and I'm sure Creez67's enthusiasm (and screenshots with artwork) have convinced someone to try RM.

I don't expect everyone to use it, but I would like to know if it's reaching more people.

[Creezz67]

17 hours ago, floatingyeti said:

There is nothing wrong with Romanos ini or the app that generates them. This is more an issue with Rocketlauncher and it not having the versatility (Rom Mapping) required to make this process user-friendly

I have tested on merged/nonmerged/split and it works

I am attempting to replicate the issue you are encountering (using non-merged) but I'm unable to.

There will only be an issue (with any romset option) if clones are not present within the parent rom (merged) or individually (split or non-merged)

Let's look at Zeroteam for example

Using Romanos ini and non-merged set:

All non-merged parent/clones are present and the list is generated (all games launch)

here are my RM settings:

This will work with "First Matching Extension" set to "True" or "False"

So Non-merged (in this scenario) works

Obviously, I can't dismiss the issues you are experiencing so let's go over a scenario where non-merged rom mapping doesn't work.

Here's what happens if non-merged zeroteam is present, but the non-merged clones are removed:

It crashes! 

Using MAME 0.250 it never gets past the Fade screen. I waited 5 minutes and there wasn't even an eventual error message. I couldn't even "end process".

Using RetroArch (MAME 0.250) it at least crashed to an error message and didn't completely lockup my PC.

It has nothing to do with the database or Romano's ini file (it is correct).

This behavior or (Rocket Launcher) bug will occur with non-merged or split set if all clones are not present.

It's not so much an issue with the split set because most people would have the entire set in their rom folder

I do think it's a flaw (that should be fix by RL devs) for the non-merged set.  One of the best features of the non-merged set is that all roms are "portable" and you can have a functional incomplete romset if you choose.

But there still is some versatility. Rom Mapping will work (non-merged) if it can find at least one listed clone.

 Let's look at zeroteam again with one clone removed from roms folder:

And it does work (with one less clone displayed)

 

Creezz67 were you testing only the non-merged parent rom without the non-merged clones in your rom folder?

I do think you should continue using the merged set because it is working for you, and you prefer it.

Sorry for the long explanation, I just didn't want anyone reading the thread to think that non-merged doesn't work with Rom Mapping.

I can't say it's the "best" option (it's purely subjective), but I do feel the need to document it as a usable option.

This is what I get using non merged romset and Romano's ini, with your settings:

As you can see I have a full 0.250 non merged set with bios files and all zeroteam clones are present.

 

 

 

[Creezz67]

17 hours ago, floatingyeti said:

There is nothing wrong with Romanos ini or the app that generates them. This is more an issue with Rocketlauncher and it not having the versatility (Rom Mapping) required to make this process user-friendly

I have tested on merged/nonmerged/split and it works

I am attempting to replicate the issue you are encountering (using non-merged) but I'm unable to.

There will only be an issue (with any romset option) if clones are not present within the parent rom (merged) or individually (split or non-merged)

Let's look at Zeroteam for example

Using Romanos ini and non-merged set:

All non-merged parent/clones are present and the list is generated (all games launch)

here are my RM settings:

This will work with "First Matching Extension" set to "True" or "False"

So Non-merged (in this scenario) works

Obviously, I can't dismiss the issues you are experiencing so let's go over a scenario where non-merged rom mapping doesn't work.

Here's what happens if non-merged zeroteam is present, but the non-merged clones are removed:

It crashes! 

Using MAME 0.250 it never gets past the Fade screen. I waited 5 minutes and there wasn't even an eventual error message. I couldn't even "end process".

Using RetroArch (MAME 0.250) it at least crashed to an error message and didn't completely lockup my PC.

It has nothing to do with the database or Romano's ini file (it is correct).

This behavior or (Rocket Launcher) bug will occur with non-merged or split set if all clones are not present.

It's not so much an issue with the split set because most people would have the entire set in their rom folder

I do think it's a flaw (that should be fix by RL devs) for the non-merged set.  One of the best features of the non-merged set is that all roms are "portable" and you can have a functional incomplete romset if you choose.

But there still is some versatility. Rom Mapping will work (non-merged) if it can find at least one listed clone.

 Let's look at zeroteam again with one clone removed from roms folder:

And it does work (with one less clone displayed)

 

Creezz67 were you testing only the non-merged parent rom without the non-merged clones in your rom folder?

I do think you should continue using the merged set because it is working for you, and you prefer it.

Sorry for the long explanation, I just didn't want anyone reading the thread to think that non-merged doesn't work with Rom Mapping.

I can't say it's the "best" option (it's purely subjective), but I do feel the need to document it as a usable option.

Now I have found something else.

When using all your settings and exactly the same non merged romset, if the game ONLY has 1 clone it shows up correctly (see 3stooges below) and works. If there is more than 1 it will not work for me and shows a list of all the same roms like above.

Strangely, on my merged set, every game that has MORE than 1 clone works fine, but any that has just 1 doesn't work unless I manually create a clone for it.

 

 

[floatingyeti]

10 minutes ago, Creezz67 said:

This is what I get using non merged romset and Romano's ini, with your settings:

Are you using a database that only contains the parent and not the clones?

Rocketlauncher launcher has to pull clone  description info from a database.

I don't know if it pulls info from the database in Hyperspin/Database or RocketlauncherUI database while HS is running (probably HS since it us active plugin)

I always keep identical databases in both folders. I know it will use RocketlauncherUI database info because it will also work without Hyperspin running.