Main > Software Forum
Front end questions
<< < (2/4) > >>
u_rebelscum:

--- Quote from: jlfreund on August 21, 2006, 12:17:47 pm ---- I still don't understand why some games are distributed as multiple zips?  Is there a reason why they can't be combined?

--- End quote ---

They can be combined.  And used combined.  Or not: "merged" (what you're talking about), "split" (the most common), and even "non-merged".  You can merge your zips if you want.  (I'd use cmpro instead of doing it by hand.)

The reason the most common distribution is "split" is it takes up less bandwidth in two ways: files (ROMs) shared between two parent/clone games only need to be downloaded once (in the parent zip file), and you don't need to download any of the clones if you don't want them.  Also, if just one of the versions has one of the ROMs changed (fix a bad dump, for example), the whole merged zip would need to be changed, instead of one smaller zip file of just that version; effecting any internet caches that might hold them (I'm not talking local caches, but ones that help speed up comcast, ect).

Not having to download the clones is the biggest reason split is used so much, but you can find merged sets out there.


--- Quote ---It seems ridiculous for every user in the world to have to customize their front end game list menu to hide unusable zip files.
--- End quote ---

I think you're mixing different concepts, and blaming mame's multiple zips.
A. By "unusable", I think you mean ones you don't have?  Whether a FE displays all the possible games (6100+) or just the ones you have by default is up to the FE not mame, nor if you have merged sets or not.
B. If all versions of a game were in a single zip file (aka "merged"), many FEs would still show all the versions unless you set it differently.  (I can't tell if this is a problem for you.)
C. "Mame is not about playing the games; it's about documenting the hardware.  Playing is a nice side effect."  This mameDev's official stance, not my personal view.  This means any complaints about how hard mame is to use will not be listened to by those who count the most in mame's development.
D. If the arcade game had different versions with significant differences, mame will (try to) emulate all of them.  The "user" reason is person A remembers playing version B, while person X remembers version Y.  The real reason is there were different versions in the arcades, and mame wants to document all of them.
jlfreund:

--- Quote from: u_rebelscum on August 22, 2006, 12:42:09 pm ---I think you're mixing different concepts, and blaming mame's multiple zips.
A. By "unusable", I think you mean ones you don't have?  Whether a FE displays all the possible games (6100+) or just the ones you have by default is up to the FE not mame, nor if you have merged sets or not.
B. If all versions of a game were in a single zip file (aka "merged"), many FEs would still show all the versions unless you set it differently.  (I can't tell if this is a problem for you.)
C. "Mame is not about playing the games; it's about documenting the hardware.  Playing is a nice side effect."  This mameDev's official stance, not my personal view.  This means any complaints about how hard mame is to use will not be listened to by those who count the most in mame's development.
D. If the arcade game had different versions with significant differences, mame will (try to) emulate all of them.  The "user" reason is person A remembers playing version B, while person X remembers version Y.  The real reason is there were different versions in the arcades, and mame wants to document all of them.

--- End quote ---

By "unusable" I mean zips that rely on others, show up in a front end menu, but aren't themselves playable.  Or maybe I misunderstood what splits are about. Is everything in a frontend menu playable?  For example, when you see "set 1" and "set 2", are both always playable?

If everything displayed is always playable -- and these set1, set2 options are just two different playable versions of the same game, then it's not as big a deal as I thought.  It would just be confusing if front ends are listing partial sets and you can't tell which menu items are playable (of course, ignoring the case where a front end displays games that haven't been downloaded yet -- that's different).

Havok:

--- Quote from: jlfreund on August 28, 2006, 04:52:20 am ---Is everything in a frontend menu playable?  For example, when you see "set 1" and "set 2", are both always playable?

If everything displayed is always playable -- and these set1, set2 options are just two different playable versions of the same game, then it's not as big a deal as I thought.  It would just be confusing if front ends are listing partial sets and you can't tell which menu items are playable (of course, ignoring the case where a front end displays games that haven't been downloaded yet -- that's different).



--- End quote ---

Sometimes not everything is playable. However, this is where filtering comes in. AtomicFE, for example, has the ability to remove the unplayable games from your displayed list.
Tiger-Heli:

--- Quote from: jlfreund on August 28, 2006, 04:52:20 am ---By "unusable" I mean zips that rely on others, show up in a front end menu, but aren't themselves playable.  Or maybe I misunderstood what splits are about. Is everything in a frontend menu playable?  For example, when you see "set 1" and "set 2", are both always playable?
If everything displayed is always playable -- and these set1, set2 options are just two different playable versions of the same game, then it's not as big a deal as I thought.  It would just be confusing if front ends are listing partial sets and you can't tell which menu items are playable (of course, ignoring the case where a front end displays games that haven't been downloaded yet -- that's different).

--- End quote ---
Again - you are mixing concepts and it depends on your frontend.  I will use EmuLoader as an example here.

I would say in 95% of the cases, if you have the parent rom set and the set 1 and set 2 set available, all three games should show up in the front-end and be playable.

Some FE's will filter on Working/Non-Working, but this is based on a flag in MAME's XML and is less accurate than you would hope - i.e. the game may lock up on Level 15, but be flagged as non-working, or it didn't work 5 version ago, but now does and they didn't remove the flag.  In other cases, the game may not be flagged at all, but when you run it, you get a message the the protection is not broken yet and there are working clones.  This is sloppy on MAMEdev's fault, but as Urebel said, they are mainly about accurate emulation and documenting working/non-working flags is somewhat secondary.

Also, most FE's will search your roms and list available/unavailable and let you filter on these.  In EmuLoader's case, it just checks your Rom folder and if it finds Bzone2.zip in your ROMS folder (even an empty file), it assumes the game is playable and will list it.  EmuLoader assumes you either have a good rom set or that you run a utility like ClrMAME or RomCenter first.  Other frontends will actually check whether all the required files are available before filtering the list, but this makes it a much longer process.

Hope this helps.
jlfreund:

--- Quote from: Tiger-Heli on August 28, 2006, 10:00:20 am ---
--- Quote from: jlfreund on August 28, 2006, 04:52:20 am ---By "unusable" I mean zips that rely on others, show up in a front end menu, but aren't themselves playable.  Or maybe I misunderstood what splits are about. Is everything in a frontend menu playable?  For example, when you see "set 1" and "set 2", are both always playable?
If everything displayed is always playable -- and these set1, set2 options are just two different playable versions of the same game, then it's not as big a deal as I thought.  It would just be confusing if front ends are listing partial sets and you can't tell which menu items are playable (of course, ignoring the case where a front end displays games that haven't been downloaded yet -- that's different).

--- End quote ---
Again - you are mixing concepts and it depends on your frontend.  I will use EmuLoader as an example here.

I would say in 95% of the cases, if you have the parent rom set and the set 1 and set 2 set available, all three games should show up in the front-end and be playable.


--- End quote ---

What I still don't understand is if everything that appears in the front end menu _could_ be playable (assuming you downloaded the ROM, and assuming the ROM works).  Putting aside the fact that FE's can use different heuristics for constructing a list -- do any front ends display a menu item for something that can never be played because it belongs to a set? 

I've tried MameWah and a couple others and see most games have "... set1" "... set 2", or "... 1a", "... 1b", or "... (World)", "... (Japan)", etc.  Are all of those unique games (ie different versions of the same game that _could_ be playable, or are there sometimes partial sets listed as separate menu items that don't belong on the menu?

Thanks,
Jason
Navigation
Message Index
Next page
Previous page

Go to full version