xboxscene.org forums
OG Xbox Forums => Software Forums => Emulators => Topic started by: RMCF on January 05, 2003, 04:05:00 PM
-
Does it reach 100% or is there stuttering?
-
Depending on which games you want to play, there is a size limitation when it comes to the size of the roms it can handle in memory, as the Xbox only has 64meg and the emulator trys to load the whole rom and the emulator into memory. FBAx does play most of the CPS1/2 games better in my option.
-
Wasup.
The Neo Geo roms that Mame-X CAN play, play flawlessly. No sound stuttering, no slowdown.(well, except for Metal Slug 2, but that has slowdown normally, so eh...) In fact, it looks better than my actual Neo Geo, because of the better television interface. It's second to xSNES9X as the most professional-feeling emulator out for Xbox right now. Its just a shame that it has a problem with larger romsets.
As for the CPS-2 games, I'll agree with Nerf on this one. I don't know what Final Burn does that Mame-X doesn't, but all the large Capcom roms that couldn't be played on Mame-X can and do play fine on Final Burn. Once you see Marvel vs. Capcom playing flawlessly, you'll be awfully tempted to invest in a couple X-Arcade joysticks. One caveat: Final Burn still has some problems with its control setup, so be prepared to spend some time fussing with configuring your buttons. That should hopefully be remedied in the next release however, so I'm picking nits on an otherwise great emulator.
Later,
mr jones
-
Like it was just stated, both emulators run at the most high sound and image quality settings flawlessly. MAME-X is a great emulator for most MAME games and Neo-Geo roms, but you should play your CPS1/CPS2 roms on Final Burn Alpha X, which performs better emulating Capcom systems.
The only problem with MAME-X is the memory limitation... you can only load games that are up to 53Mb uncompressed... in other words, you will not be able to emulate the latest Neo-Geo games, unless you have a 128Mb Xbox system.
- I would like to ask anyone, is there any theorical way to "fix" this memory issue without performing a RAM upgrade?