I’ve made some progress with ‘The Gladiator’ by IGS

this can’t be considered working yet because it needs quite a few hacks to get it this far, the intro doesn’t play (boots straight to title screen, crashes on game over), and it only seems to operate in freeplay mode, scrolling is broken, and sound + inputs fail once you reach the 2nd level….

thanks to rtw for running some tests on the PCB

As you may have noticed this site has been down for a few days due to technical issues.

During this time somebody issued ‘UME 0.150×3’ and ‘UME 0.151’ builds. These are not official builds and are not built from unmodified official sources (the 0.151 build especially contains dangerous hacks to remove the nag screens and add hiscore.dat support which have a tendency to destabilize builds) I would have made this clear sooner, except I didn’t have a site to post on.

What this does show however is that if I don’t offer official UME builds then people are just going to build unofficial ones, and with those you really don’t know what you’re getting.

As expected Mamedev have decided to ignore / bury the code licensing issue, and the foolhardy arrogance being demonstrated on a number of Mameworld threads shows that they’re clearly never really going to care about it. I guess I could continue to offer new official binaries with a disclaimer telling people to contact both Mamedev and myself if they feel any code has been incorrectly relicensed by the ongoing process, at which point I’ll immediately remove any binaries etc. containing the offending code (although I can’t speak for Mamedev, draw your own conclusions there). Obviously I can’t offer older builds at all due to the Yamaha copyright issue, that isn’t up for debate. This does make the situation with code of mine that has been incorrectly relicensed tricky, but this whole issue was never really about my code anyway, I’m simply willing to do what is ‘best’ for the project and least disruptive to users going forward.

MAME has a -mt option to turn on some extra multithreading to give a tiny speedup by handling the final blit on a different thread. This is unrelated to drivers which have their own threading implementations for larger speedups.

For several versions now this has been the default.

However, it is not a *safe* option to use, and should really be turned off.

The problem appears to be that for games using indexed palette modes the palette / video aren’t buffered properly and end up out of sync in what MAME outputs at a frame, or even sub-frame (if single stepping) level.

This is very evident in some cases, for example in “Rapid Hero” the initial fade at the start of a level becomes a flickering mess with -mt enabled, and in games like “DoDonPachi Dai-Ou-Jou” the area surrounding the AMI logo fades at a different speed to the rest of the image creating an obvious border, in addition the ending text fades are horrible broken. Several CPS2 games including the of the intro screens of “Gigawing” exhibit similar issues with -mt enabled. In other cases it caused more severe palette glitches; I had to work around it in Casanova by converting the whole driver to use RGB32 mode.

The issues introduced can be rather system-specific, and depend on the unchecked timing of everything else in your machine, so depending on what hardware you’re using the glitches may be different for you.

While in some case such glitches occurred on real hardware, and are thus emulated, the -mt option is creating many more incorrect cases where this happens and is significantly harmful to the fidelity of our emulation. I do not know why it is turned on by default for some marginal performance gain on older systems, it seems to go against the MAME philosophy of putting correctness of emulation as the first priority.

There are already Mametesters entries associated with this bug, for example
http://mametesters.org/view.php?id=3356

I’ve requested that it be turned off several times, but it appears the development team are not interested in turning it off, so I feel the need to highlight this issue as a public service. If you want to guarantee MAME operates as expected without additional glitches being introduced based on the hardware configuration of your machine then you should ensure you run with -nomt or equivalent way of turning off the multithreading from your frontend.

UME builds still ship with it turned on because I wish to ship unmodified baseline sources (so this applies equally to that) but it does irritate me that I’m shipping a piece of software with options know to cause defects in the emulation turned on by default.

I’ve highlighted what a fantastic resource MARP is in the past, especially when they provide complete 1 Credit Clear replay files for games recorded with modern MAME versions. In the case of games where I’ve worked on the emulation, or there have been recent improvements I do take the effort to watch them. (It’s a real shame some drives like DoDonPachi II don’t record properly for unknown reasons)

The reason I watch them is to make sure bugs have properly been fixed, it brings some further level of closure to the reports, and increases the level of confidence we have in our emulation. In the case of Thunder Dragon 2 there were sprite priority fixes from trap15 in 0.150 so I wanted to watch the replay to make sure there were no obvious remaining sprite issues.

Instead of seeing sprite issues I saw something else, once the game hit the level 4 boss there were background glitches, as you can see below.

(Thunder Dragon 2 surprisingly has problems with the background tilemaps in 0.150 / 0.150×1)

This came as a surprise to me because I thought I’d fixed all the background problems in the nmk16 driver a long time ago, my logic seemed sound, and from a hardware point of view made sense. Seeing these glitches didn’t really make sense tho, where were they coming from? A bit of poking around later and I found the issue, only the first tilemap bank was being marked as dirty when the tile graphic bank was changed, meaning that if the tile data was written before the graphic bank change MAME wouldn’t be updating the cache bitmaps. This is still one area you have to be careful in MAME, it’s an optimization MAME has for drawing tilemaps, but if you don’t mark things properly it can lead to glitches like this.

Thankfully it was easy to find, and easy to fix. I assume it’s been like that since I first fixed things in the driver, which means that technically the driver has never had proper video through the years, be it the sprite priority glitches, the tilemap scroll glitches before I rewrote it, or the glitches caused by this oversight.

I didn’t notice any sprite issues during the run, and with the tilemaps hopefully now fixed for good as well 0.151 will almost certainly be *the* version you should be using for Thunder Dragon 2.

Of course me being me I can’t help messing around a bit, and while the replay file on MARP was for Thunder Dragon 2 I actually played it back with the Big Bang clone, and the older Thunder Dragon 2 set as well. In both cases the game played the same way, with no desyncs and the player finished with the same score, this is kinda interesting because it means that if the difference between the revisions was a gameplay tweak or bugfix the player recording the replay didn’t encounter the issue.

I’ve recorded a video file from the replay with the fixes applied and put it on YouTube. The player is ‘edusword’ and it shows the game (running the Big Bang set) from start to finish, as you can see the emulation is looking pretty good these days! Hopefully the player doesn’t have any issue with this being uploaded, I wholeheartedly thank them for the replay!

Content not available.
Please allow cookies by clicking Accept on the banner

One interesting thing about the game is that you can destroy the various messages that appear at the start of levels for extra points. You can even destroy the end credits and the points continue to rack up, although for whatever reason they don’t count in your final score!

If you’re wondering about other NMK news I’m afraid to say things have gone very, very quiet on the NMK004 dumping front, not sure what happened because it sounded like the guys looking at it were very close to the end!

The official MAME/MESS 0.150 release saw the concept of ‘u’ updates abolished. This I feel was long overdue, but at the same time there are points in the development cycle where clear improvements have been made over the previous release.

For this reason I’ve decided to offer my own unofficial updates here. I’m calling them ‘x’ builds, to avoid confusion with the old official ‘u’ builds. I’ll only be compiling / offering these in UME form, not MAME / MESS, and like with the MAME / MESS updates I’ll post a little synopsis with each update highlighting the more important changes.

I doubt I’ll have to do this too often, but for now the first of these updates is 0.150×1, and it’s based off SVN revision 25500.

The changelog (simply a copy/paste of the SVN log) can be read here. This isn’t formatted as a whatsnew, but as mentioned I’ll summarize the main points below.

UME 0.150×1 Windows binaries – 32-bit, 64-bit and all tools
UME 0.150×1 sources

In addition to the above I’m offering a test binary compiled with different settings and a slight source modification as described by MooglyGuy here. This includes an experimental change that could improve the N64 performance on some systems (it doesn’t seem to make a difference here) I’m only offering this in 64-bit flavor as there is little point in a 32-bit build. It requires at least a Core2Duo to run.

UME 0.150×1 experimental Windows binaries – rsp.h modification, SSE2 optimization, 64-bit only, all tools (not recommended for general use)

Points of Interest

First I should probably start by saying that the Vector HLSL and effects+multi screen game issues are NOT fixed yet, that code hasn’t been touched at all, however, there have been some significant bugfixes / regression fixes.

The beatmania series (HDD error on startup)
Several Taito G-Net games (Super Puzzle Bobble flash card read error)
Meikyuu Hunter G sound (inadvertently broken when Ghost Busters was changed to use the Deco222 a while back)
Jangou Lady (broken by CPU core rewrites requiring interrupt handling in drivers to be more correct)
Double Dragon 3 refresh rate (became a bit too low when driver was merged with WWF Wrestlefest)
Uncio driver (Zero Point 2 / Burglar X) (tile dirty marking ended up being broken 2 and a half years ago during some refactoring, nobody had reported it until now!)
Genesis VDP timing (was using PAL timing in some cases when it shouldn’t have been after a previous refactor, this was causing visual glitches in many games eg. Dashin’ Desperadoes)
Rise of the Robots (HDD loading error)
X-Men 6 Player version (missing sprites after the m_screen refactoring)
GX4000 inputs (weren’t working for many games, even if they worked on the 6128+)
Atari Flat shaded 3D games (Hard Drivin’, Stun Runner) (confirms that the 68010 doesn’t have the ‘broken’ clr.b/.w/.l opcode behavior)
Flower (had been mistakenly set to 4-way in 0.150 due to a video of the cabinet showing a 4-way stick, but clearly seems to be an 8-way game, probably a faulty kit conversion)
Crypt Killer (HDD loading error)

Regrettably some of those were regressions I introduced (DD3, Atari, Meikyuu Hunter G) even after extensive testing at the time, goes to show you can’t catch everything so we’re always thankful for testers. Many of the others are due to the ongoing IDE/HDD type changes, and some are rather embarrassing (the logic for the dirty tile marking in Uncio was flawed beyond comprehension, but did give an opportunity to redactor and clean up the driver a bit while fixing it) The fixes here came from a variety of devs which is always good to see.

The list above alone should be enough reason to favor a 0.150×1 build over plain old 0.150, but naturally there are more improvements and additions included too.

(GX4000 controls were one of the long-term regression fixes, so inputs work again for many games, including player 2 support)



(video emulation in the Unico driver was another long term casualty, last working 2.5 years ago. 0.150×1 fixes that so backgrounds are present in Zero Point 2 again)

The conflict between the ‘shark’ game set ROMs in MAME and the ‘shark’ device ROMs in MESS when compiled as UME has been resolved, it was reported to have been causing some problems for frontends and ClrMAME in the last 2 UME releases. If you notice anything like this in the future which isn’t being picked up by -validate than let me know and I’ll ensure that it gets fixed as soon as possible. Not all devs are using a combined build, and when this specific type of conflict doesn’t show up with -validate even if they are it’s very easy to slip under the radar because we don’t typically make use of ROM managers or Frontends while working on MAME/MESS.

The web server code has seen numerous improvements too, mainly thanks to external contributor ‘Firehawke’ The code as-shipped in 0.150 could only run on port 8080 due to some hardcoded values in the code (so if you changed the port it wouldn’t work properly at all) The interface has also been vastly improved and several new features like the ability to load and save states are exposed via the web page you’re presented with. Fixes have also been made to improve rendering on mobile devices at different screen orientations etc. so controlling the MAME interface features via your phone or tablet now works better than it did in 0.150. If this feature was of interest to you then 0.150×1 is a big step up from 0.150.

In terms of newly supported stuff one of the most interesting additions is a prototype clone of Taito’s ‘Growl’ found / owned by the same ‘Dsyde’ and ‘muddymusic’ combo that brought us the ‘Bubble Bobble 2’ prototype previously shown here. There is a fair bit to write about this prototype, but I want to wait until they’ve put up their own post on Jamma+ about it.

(A prototype of Growl, right, was added. I’m not going to write more about it until the owners have done their own comparisons tho)

There’s also of course ‘Dolmen’ which slotted right in a few hours after 0.150 hit, and the playable, but still marked as not-working due to potential issues ‘Carket’ added yesterday.

(Dolmen, the Puzzle Bobble clone from Afega works fine)



(Carket Ball still has issues and will continue to do so until the protection data is dumped, but still runs to a degree)

Support was also added to the cps3 driver to load the bootleg CPS3 multi-game conversions from Darksoft, there are two sets, one runs on a dead / blank cart with replaced bios (same key as 2nd Impact) and the other runs with a cart with both the bios replaced and CPU replaced with a regular SH2. Due to the difference in the way the encryption works with a dead cart (encrypted code mixed with non-encrypted data) neither bootleg has complete coverage. I know there are a number of people who don’t think MAME should be supporting things like this, or disagree with the term ‘bootleg’ but they are what they are, and as they’re being used in the wild it is up to MAME to document them, and document the ability to use a regular SH2 regardless of personal opinions.

(the CPS3 bootleg sets run on dead carts or ones with the custom CPU replaced with a regular SH2, not all games can be flashed even if they appear in the menu)

Brian Troha was involved in adding a large number of old Player’s Edge Plus sets were also sorted out for this release, and while most are minor variations on the same themes it is good to have them better documented.


(lots of new Player’s Edge Plus sets are recognized)

Some work was done by Barry Rodewald on the ‘Williams WPC (Alpha Numeric)’ driver pinball, meaning most sets in there now show some start-up strings and attempt to boot, although like all the Pinball drivers I doubt MAME will ever serve as more than the emulation core part of another piece of software like PinMAME did.

In MESS Curt Coder continued on his quest to emulate every obscure C64 peripheral you could possibly imagine, adding support for the PARTNER 64 personal organizer cartridge while also factoring out some legacy code.

(PARTNER 64 was a cartridge based personal organizer for the C64, screenshot taken from bannister.org thread)

R.Belmont added a missing FPU opcode to the 68k cores for the benefit of Sim City 2000 on the emulated Mac platforms.


(The Mac version of Sim City 2000 required a missing 68k FPU opcode to be implemented, screenshot taken from bannister.org thread)

A non-working driver for redemption game ‘Frantic Fred’ was added. This is another Kyle Hodgetts game and the emulation exposes a few bugs in the driver, one of which has been fixed, the other (page flipping problem) remains. The game is marked as NOT WORKING because the inputs don’t function. It should use a wheel and one button, but I’ve been unable to find where the wheel maps. It might require somebody more familiar with the TMS32010 to fix it up. I tried using a similar mapping to the other games on the hardware where a spinner was utilized but it doesn’t appear to be the same.


(Frantic Fred is a Kyle Hodgetts redemption game, currently not working due to missing inputs)

Softlist additions on working platforms have been a little quiet of late because etabeta usually does a lot of that work and he’s been busy, however there was the Ultraman Saturn cartridge added to the lists (mentioned in the article below)

The PROM to the very rare Desert Dan was dumped by Zab, allowing for correct colours in that (yes, the desert is white)

(Desert Dan with proper colours)

For less noticeable but still worthwhile changes you have things like iq_132 cleaning up the 1943 protection simulation, by returning the expected values based on the writes made rather than looking directly into a CPU register for the correct result (which is an ugly hack) Functionality should be identical tho!

Many other changes have been made, especially in the MESS side with work being done on a number of fairly obscure systems, or affecting things in ways I’m not familiar enough to provide information on. As always check the changelogs because a lot of the really hard work being done does go under-appreciated.