4 ms·
How I dumped an arcade game for MAME
- dale_glass 4y agoMAME has always confused me with its mode of operation. Why is there a game list with specific required hashes built into the code? Why refuse to run an unrecognized version of a game? Most other emulators seem to just try to emulate whatever you happen to give them.
- deleted 4y ago[deleted]
- vore 4y agoBecause arcade consoles differ a lot from direct-to-consumer consoles, where the hardware configuration is much less uniform than, say, a Game Boy Advance which has the same parts in the console and the parts in the cartridge are mostly the same from game to game. The article itself alludes to this: It’s easy to think of game cartridges as just being a single thing, but arcade game boards typically have a large number of chips. Why’s that? It’s partly technical; specific chips can be connected directly to particular regions of the system’s hardware, like graphics or sound, which means that even though it’s less flexible than an all-in-one ROM, it has some performance advantages too. The two chips I dumped here are program code for two different CPUs: one for the 68000 CPU in the system itself, and one for the ARM7 CPU in the game cartridge.
- dale_glass 4y agoFair enough, but something like the Neo Geo took cartridges internally, no? Excluding cartridges with special bits on them (and I kinda doubt there's that much unique hardware on a system that mostly had fighting games) there shouldn't be anything that specific per game on that system. And yet MAME is just as picky with those as it is with anything else.
- Firehawke 4y agoAnother good reason is to prevent the accidental use of bad dumps. A number of the systems supported in MAME have been redumped multiple times as it was discovered that bitrot had set in on chips, or the dumper made mistakes, or any of a dozen other things happened. This is also why your older dumps of e.g. Pac-Man for MAME 0.02 won't work on a modern MAME build-- we didn't have the color data PALs dumped, some of the early ROMs were later proven to be bad dumps, and so forth. Locking it down to specific "best we know of as of this moment" prevents people from easily using materials we know to be incorrect, which in turn also prevents people from sending invalid bug reports.
- derefr 4y ago> Locking it down to specific "best we know of as of this moment" prevents people from easily using materials we know to be incorrect One big downside I would see is that it somewhat inhibits the creation/growth of an arcade-machine romhacking scene. (Unless there's some explicit provision in MAME for loading arbitrary patches on top of the known-good game versions.) > which in turn also prevents people from sending invalid bug reports Something to consider: some other emulators do this not by burning hashes into the code, but rather by downloading at runtime (tracking via RSS or the like) an independently-maintained known-good-dumps-hashes DB. (Compare/contrast, the way that the http://www.accuraterip.com/ http://www.accuraterip.com/ database is used in audio CD ripping.) This approach enables a separation of responsibilities between "building good emulator software" vs "archiving and conserving specific games" — with one of the touted advantages usually being that that the database of good dump hashes can then be used for things other than just powering one specific emulator. It can be shared by many emulators, and other ecosystem tools; and it can even be used by anthropologists to study the "family trees" of game releases. Also, when emulators besides MAME that use such techniques, detect that a game has a known-bad hash, they don't prevent you from playing it. They just tell you really loudly that you're about to play a bad dump (implicitly, disclaiming all liability for your doing so.) Like a modern web browser's "insecure" warning when retrieving a page over a non-HTTPS connection.
- vore 4y ago
- tenebrisalietum 4y agoSo you don't blame MAME if your ROM is not genuine.
- mike50 4y agoFinal Burn Alpha does what you want. Looks like its been forked into FB Neo. https://github.com/finalburnneo/FBNeo/wiki https://github.com/finalburnneo/FBNeo/wiki
- tinus_hn 4y agoProbably to avoid all the bug reports you get from people who use bad dumps or dumps of roms that require different hardware. It’s open source and not hard to compile, so feel free to change the hashes or remove the check, I guess.
- stevage 4y ago
- anikom15 4y agoWork on obscure games sometimes trickles down to get the more popular stuff working or improved. Popularity of a game doesn’t much correlate to its functioning or accuracy. The starry background in Galaga was broken for years. Sometimes the mamedevs just don’t have a way of fixing a problem (encryption, missing dumps) or the performance isn’t there yet (N64, consoles since the PS2).
- deleted 4y ago[deleted]
- pvg 4y agoPlease don't post shallow dismissals, especially of other people's work https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- LukeShu 4y agoFWIW, I didn't interpret the parent post as a dismissal.
- nfgrep 4y agoHad no idea copy protection would be so intense for those old arcade boards. A whole ARM 7 right on the cart, hardcore!
- mysterydip 4y agoGame developers wanted to keep selling new cabinets to arcades. Arcade owners wanted to maximize ROI and reuse assets with new/modified games, which some enterprising engineers were able to provide. Ms Pac-Man started this way: https://en.m.wikipedia.org/wiki/Ms._Pac-Man https://en.m.wikipedia.org/wiki/Ms._Pac-Man
- bsaul 4y agoI’ve yet to find a beat them all as good as the two D&D from capcom. I’m really surprised they didn’t keep the franchise, those games were such a huge hit when they got out..