Mame works a bit different in that it is capable of pulling the parent and bios separately from the same folder (merged) and boot the game independent of it's other parts. However you'll need "full non merged" Mame roms as they contain the parent, clone and bios all within the same zip file. Unless, once again, you're trying to use some low powered Nest A/C unit connected to a screen or some shit.Īll FBNeo does is update it's compatibility based on the Mame set as they add new games to the emulator, if it's in the FBNeo library it will work. Anything that doesn't work in MAME because I broke the set or whatever, I use in FBNeo.ĭon't bother with MAME 2003, 2005, 2013, or any other version that's not just plain ol MAME. My current run is the latest MAME roms from the megathread - or at the time when I last ran through my stuff, which was. But most of those aren't going to be the games you'll be looking to play regardless. 230 the gap isn't big enough to break much, unless it's a title that didn't work on. The biggest difference is that if you want to play SF2, for example, you're probably going to need all of the regions, variants, and bootlegs to get the game to work on MAME whereas you just need the SF2 from the region you want to play for FBNeo.īut you can find MAME roms with all of the various parts and bootlegs in a single zip file, or part of a set that requires two separate zips instead of six or more. If you're up to date, MAME and FBNeo files are relatively interchangable, though you can still run into issues.
And you run into the issue where some games you might want to play won't even work on MAME 2003 because it didn't become compatible until 2013. Old MAME requires less to get decent performance out of games, but like you already know, you're losing out on accuracy and bugfixes.
If you're not using some low powered retro portable or some weak ass PC hardware, there's no point in using old MAME. You are absolutely correct, don't use the older MAME core.
0 kommentar(er)
