MAME Testers - ISSUES

04050: (twineag2) Missing graphic effect in screen transitions

In different moment there's a screen transition; in a real HW the screen is clean from the bottom of the screen
probably the effect is handled by 1c0064-1c0065

the value go down from d4 to 30 and go up from 30 to d4

04049: (ghox) There's a small bit of garbage on the ending screen.

There's a small bit of garbage on the ending screen.

04048: (shdancer, shdancer1) [possible] Background corruption during Train scene (Level 2-2)

During play in Level 2-2 of the game, as the train comes to a stop, there is a noticeable change in the background that is visible between the cars as the train slows down.

04047: (tknight, wildfang, wildfangs) Gfx glitch near "Insert Coin" word

Gfx glitch near "Insert Coin" word

04046: (popnpop) 16-bit EEPROM set with 8-bit data

When the game starts, the line
16-bit EEPROM set with 8-bit data
is displayed 4 times.

I don't know if it is an issue with the new memory management system but it didn't appeared before.
AFAIK, there is no other issue with the emulation itself.

Please tell me if such message have to be reported or not.

04045: (lockload) Shooting doesn't work

You can't shoot at anything.If you will shoot,the screen will flash,but nothing will happen.

04044: (batsugun and clones) [possible] batsugun VDP mixing still not correct

The attached screenshot is the screen shown at the end of a level that tallies up your bonus points for medals (the large and small spinning gold chevrons left by destroyed enemies) At least if the Saturn version is something to go by, there should be medal sprites to the left of the two equals signs, one small and one large.

04043: (metlhawk) Metal Hawk incorrectly requires metlhawk.nv (NVRAM)

Metal Hawk incorrectly requires metlhawk.nv in metlhawk.zip. This is wrong as that file is the NVRAM data which is saved in the NVRAM directory. Also no other Namco System 2 game seems to have this issue.

Apparently this bug was introduced in 0.137u1

04042: (All sets in dambustr.c) [possible] If you go too far without dying, background becomes complete garbage. Emulation bug or bad ROM?

If you go too far without dying, background becomes complete garbage, but it then appears again correctly. Is there a bad dumped ROM or is emulation bugged somewhere ? Verification against real PCB is needed !

04041: (rainbowo) Original PCB video

Original PCB running attract mode through an RGB board and into my PC. There is a loose and/or bad cap causing problems with the colors but it should otherwise be useful.

http://smitdogg.mameworld.info/mametesters/rainbowo.wmv

04040: (fatfury1) Original PCB video

Original PCB running attract mode and a game through an RGB board and into my PC. Sound is set to mono.

http://smitdogg.mameworld.info/mametesters/fatfury1.wmv

04039: (dmnfrnta) Original PCB videos

Here are videos of the first 3 stages. I'll eventually add the others.

http://smitdogg.mameworld.info/mametesters/df1.wmv
http://smitdogg.mameworld.info/mametesters/df2.wmv
http://smitdogg.mameworld.info/mametesters/df3.wmv

04038: (tekken2) Original PCB video

Original PCB running attract mode and service mode through an RGB board and into my PC. Sound is stereo.

http://smitdogg.mameworld.info/mametesters/tekken2.wmv

04037: (All sets in vsnes.c) Games no longer working after 137_u2

vs Duckhunt, Gradius, Super Mario, Super Xevious (and probably others) do not work/are incompatible with/are non functional in all subsequent MAME versions following 137_u2.

04035: (All sets in chihiro.c) Assert before OK

Fatal error: Cannot call debug_console_register_command() when debugger is not running
Caused by assert: src/emu/debug/debugcon.c:413: (machine->debug_flags & DEBUG_FLAG_ENABLED) != 0

04034: (All sets in viper.c) [debug] Assert in Debug build

There is an assert to all games in this driver using a Debug build. The assert comes up before OK.

"Assert: src/emu/memory.c:4302: maxunits < ARRAY_LENGTH(m_subshift)"

04032: (All sets in dkong.c) [debug] Game does not start

Emulation stops and displays this message after typing OK with Debug build:

i8257_do_operation: invalid mode!

04031: (a51site4) [debug] Black Screen

If using a Debug build, the game does not start and you only see a black screen like it's hung up on something. Normal build starts up ok.

04030: (All sets in taito_f3.c, taito_z.c, kaneko16.c, konamigq.c, overdriv.c) "16-bit EEPROM set with 8-bit data"

A new warning printf detects issues with the following drivers. They do not interfere with the game running but they need correction.

04029: (All sets in murogem.c) Severe graphic corruption

When compared to 0.139u1, there is a major corruption in graphics as well as input/game does not react properly or at all.

04028: (ronjan) Crash after OK

After you type ok, MAME quickly crashes.

04027: (All sets in 20pacgal.c) Game does not successfully boot

Depending on set, the games in the driver will either show a black screen or version messaging with a "Stuck IRQ" message, hanging.

04026: (combatscb) Experiences various graphics glitches.

There're some gfx glitches when the tilemap is rebuilded

04025: (sprtauth) Photos of the real PCB running

Photos of the real PCB running through an RGB card into a TV.

04024: (ghox) Gfx glitchs in boot screen

Gfx glitchs in boot screen