Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
04367 Crash/Freeze Minor Always Jun 7, 2011, 00:31 Nov 28, 2016, 15:58
Tester Samurai Fox View Status Public Platform MAME (Official Binary)
Assigned To Resolution Fixed OS Windows Vista/7 (64-bit)
Status [?] Resolved Driver seta2.cpp
Version 0.142 Fixed in Version Build Normal
Summary 04367: gundamex: Temporary freeze before game starts, major speed hit.
Description Starting the game with a command line seems to always cause a temporary freeze for about a minute before emulation begins (the game information that displays before starting a ROM doesn't seem to fully go away until the "freeze" period is over). Interestingly, double-clicking MAME's executable and selecting the game in the list will only "randomly" cause a temporary freeze; some of the time the emulation starts immediately without a problem..

There also seems to be a major speed hit as well, although it may be due to improvements in emulation accuracy. It still might be an issue worth investigating, just in case. It seems most if not all seta2.c games suffer from this problem.
Steps To Reproduce Start gundamex via command line for this to reproduce every time, or for a random freeze just double-click MAME's executable and select gundamex in the list.
Additional Information
Regression Version
Affected Sets / Systems gundamex
Attached Files
There are no relationsihp linked to this issue.
User avatar
Jun 7, 2011, 01:39
edited on: Jun 7, 2011, 01:40
I don't experience such a delay when starting the game, either via command-line or in the MAME internal menu. You and I had a discussion a few weeks ago about this game/driver on IRC... this game and others like it got emulation improvements in the graphics rendering, specifically:
r11717 (before 0.141u3)
seta2.c update: [Luca Elia]
- Horizontal clipping of "tilemap" sprites
- Shadows emulation
Some sizeable changes were made to the rendering code for this driver obviously effecting some games in it. While I agree the performance has dropped well over 2x from before this patch in some instances, loss of performance isn't really the sole reason to report a bug. If there were no work done on the driver or surrounding architecture and a driver took a dive like that - it might be reason for concern and a report.

My opinion of the performance drop, as we discussed, it's not a reportable emulation bug. As far as your other delay issue before the game even starts, I don't have it here (32-bit, mamedev built 0.142) and I'll leave the bug open for others to verify (w/0.142, 64-bit) or maybe SDLMAME.

User avatar
Samurai Fox
Jun 7, 2011, 02:23
edited on: Jun 7, 2011, 02:29
Yeah, I know we've discussed the speed issue already, but I felt it was worth noting in case it may be more than just a simple consequence of improved emulation. Such huge drop in the speed makes me very suspicious, but as you've said, sizable changes were made to the driver so it's probably just that and nothing more.

About the delay, it only seems to affect Gundam EX Revue. The other seta2.c games do not exhibit this issue. I've only tried the official 32-bit binary so far. I'll try the 64-bit one and see if anything's different.

User avatar
Senior Tester
Jun 9, 2011, 12:53
It's probably trying to draw some stupidly large sprite(s) with unoptimized code.

The real hardware probably has sprite limits to prevent such sprites being drawn, and the code could probably be better optimized too.

The fact that it locks MAME solid for a couple of seconds means I'd consider it a legitimate bug rather than a mere performance issue.
User avatar
Jun 9, 2011, 13:49
Are you stating that this temporary freeze (for about a minute) happens for you with 0.142?

Otherwise, given that it's before emulation begins and the fact that it's largely random and no on else can reproduce it, I'm betting more on an issue with the OP's machine (needs reboot or restart). Some people never shut down their machines unless forced to and with a dual core processor, anything can happen.
User avatar
Senior Tester
Jun 9, 2011, 17:51
I've seen it before, and reported it to you in the past..
User avatar
Jun 10, 2011, 01:30
edited on: Jun 17, 2011, 06:24
Only takes about 15 secs to boot into game using self compiled 0.142u5 X64
i7 930 CPU @ 4.0GhZ with Nvidia GTX 480

I played for about 1 hour and experienced no freezing or anything else unusual.

running with -verbose displays this unusual information.

User avatar
Jun 17, 2011, 06:36
I have been doing some testing regarding this issue and can reproduce the 10 sec black screen before it goes in game with the following games that use the same driver seta2.c

Deer Hunting USA V2
Deer Hunting USA V4.0
Deer Hunting USA V4.2
Deer Hunting USA V4.3
Trophy Hunting - Bear & Moose V1.0
Turkey Hunting USA V1.0
Wakakusamonogatari Mahjong Yonshimai (Japan)
Wing Shooting Championship V1.01
Wing Shooting Championship V2.00

This glitch or bug seems to happen more frequently on 64-bits but occurs on 32-bits self compiled 0.142u5 win 7 x64 O/S
I also tested by deleting contents of all directories before launching mame or mame64.exe (cfg,nvram,diff, etc)

even simply opening MAME by double clicking mame or mame64.exe to launch the above games, it's possible to reproduce the issue. Try all of the above about 10 times each and you will see, unless it's isolated to a few peoples machines, but I highly doubt it.
User avatar
Jun 17, 2011, 07:12
I use 64-bit build and don't have any freeze in seta2.c games even after a 10+ time boot test.
It takes only 2 or 3 seconds till the press OK screen appears.

Core2 Duo, Win7 64
User avatar
Jun 19, 2011, 08:02
After doing much testing with all previous mame versions, I have been able to figure out the black screen delay before jumping in game seems to start at 0.141u2

The problem I'm having is this "delay bug" I will call it, doesn't occur with 100% consistency. Sometimes it jumps directly in game as it should and sometimes I get the delay bug.

This delay bug is most common with gundamex and mj4simai

When the black screen occurs on my machine, ESC, TAB, even clicking X to close the window do absolutely nothing. Once the game eventually boots then keys or closing window has effect.

Please see the snaps I took
User avatar
Senior Tester
Jun 19, 2011, 19:33
if it's random I'm guessing it's either depending on a specific frame being drawn, or RAM initialization (if RAM is uninitialized it could be drawing wildly huge multi-part zoomed sprites in the first frames, randomly ;-)
User avatar
Jun 19, 2011, 22:56
It was random in previous versions of mame. In u5 and u6 the "delay bug" happens everytime.

 I suppose if it will help, I can pinpoint what version it happens randomly, and what version it happens for me everytime.

After compiling u6 and creating a fresh mame.ini + deleting contents of CFG, nvram,
I can make this happen everytime I attempt to launch gundamex & Mj4simai
User avatar
Nov 28, 2016, 15:58
This issue was fixed.