Come and get it. The first full release in almost 2 months. Have fun!
Ok, so I lied. We’re not quite ready for 0.128 without a little more testing, so here we have 0.127u8. If you are playing with this version, make sure the Neo-Geo and Sega C2 drivers are working as expected, and report bugs as usual to MAMETesters.
One final update before 0.128. If there are any new showstoppers introduced since 0.127, make sure you have reported them on MAMETesters.
Ok, we’re up to 6 updates this go-around. I expect a u7 next week and then hopefully we can move on to 0.128.
It’s time to grab the latest MAME source update from the Source Updates page. Go on, you know you want to.
Time for another MAME update. Grab it from the Source Updates page.
Time for the latest update to MAME, over at the Source Updates page.
Now available over at the Source Updates page.
After a large amount of internal changes and restructuring, release day is finally here. Grab the final MAME 0.127 release from our Latest Release page.
This release marks a new “first” in MAME history: the first officially supported laserdisc game, Cube Quest, is now up and running. This was definitely one of the more obscure and challenging games to emulate, so special kudos to Philip Bennett, Joe Magiera, and Warren Ondras for figuring it all out!
On the Source Updates page. The dev cycle for 0.126 is winding down, so please get your bug reports in to MAMETesters as soon as you can!
Get it while it’s hot over on the Source Updates page. It’s worth pointing out that the cheat system is re-enabled with this version, but it is in read-only mode (that is, it can read new-format cheats but has no tools to generate new ones yet). Until there is a converted database, the code is still very much in the early test phase, so don’t get too excited just yet. With luck, we’ll have cheats working again in an update or two.
Time for a massive update: MAME 0.126u3. Due to a change internally with the way memory regions are handled, a large percentage of all files in the project needed to be updated.
There’s been a regression test against the change already, so we should be beyond crashing problems. But it is possible that some games may be missing sound due to mismatched sound regions. If you hear anything funky, please report it to MAMETesters so that we can get the problems ironed out in time for u4.
Grab the latest update from the Latest Updates page!
The first update of the MAME 0.127 development cycle is now available. Please make note of the fact that the cheat engine is under serious construction right now and has been disabled.
At last, it is time for a full MAME update: grab MAME 0.126 from the Latest Release page.
In addition to the usual large pile of changes and improvements, there are several big changes come along with this release that you should be aware of:
Hopefully we’ll get back to a normal 1 month development cycle starting with the next release. In the meantime, enjoy the update!
Just posted over at the Source Updates page is hopefully the final update to the MAME 0.125 dev cycle. It’s been a long road! Now is the time to check this out and ensure that all your favorites are still in fine working order before we lock down for MAME 0.126.
Oops, a major bug crept into the last release at the last second, so without further ado, please grab the small update to MAME 0.125u8 from the Source Updates page. There will still be a u9 next week, and hopefully a 0.126 to follow shortly thereafter.
Time for the weekly MAME update: get MAME 0.125u7 over at the Source Updates page. I anticipate a u8 next week followed shortly thereafter with MAME 0.126, so now would be a great time to verify that there are no showstoppers in any games you care about!
An important note about this release: inclusion of debugging support in MAME is no longer optional. That is, you can still disable it (using the -nodebug option, or setting ‘debug’ to 0 in your mame.ini file), but you can no longer compile without it. This will give a small-ish performance hit (under 5% in most cases) in exchange for always being able to pull up the debugger and will reduce the test matrix necessary to verify MAME’s behavior.
Note that due to a slight oversight, the debugger is enabled by default in this build, so you may need to explicitly turn it off. This will default to off in u8.
The latest in the now long-running series of updates to MAME 0.125 is now available. There will likely be at least two more intermediate updates before 0.126, due to the large number of changes in the dynamic recompilers and elsewhere in the system. So hang in there and please give these updates a try to ensure that everything still works as expected. As usual, report your bugs over at MAMETesters.