Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06214 Sound Trivial Always May 15, 2016, 23:16 May 17, 2016, 16:05
Tester Augusto View Status Public Platform MAME (Official Binary)
Assigned To Resolution Bugs That Aren't Bugs OS Windows Vista/7/8 (64-bit)
Status [?] Resolved Driver cps1.cpp
Version 0.173 Fixed in Version Build Normal
Summary 06214: ffight and all others sets: All players characters has the same jump voice when finish the scene before second boss
Description The three players characters has voice when in jump kick attack. The voices not are the same.
In stage 2 scene 3 before of fight against Sodom exactly on moment of the image posted when moving to next scene the player character make an jump kick attack.
The jump kick voice attack in moment for any one of the three characters is the character Guy.
Not is problem in emulation. Is an arcade bug that Capcom not had fixed even in any others revisions of arcade PCB.
Thanks for read my post.
Steps To Reproduce
Additional Information
Regression Version
Affected Sets / Systems ffight and all others sets
Attached Files
png file icon 0001.png (16,071 bytes) May 15, 2016, 23:16 Uploaded by Augusto
There are no relationsihp linked to this issue.
User avatar
May 16, 2016, 03:38
Is this a bug present in real hardware but not in MAME? or is it present on both real hardware and MAME?
User avatar
May 16, 2016, 04:24
This bug is in real arcade PCB and MAME emulate perfectly the issue.
User avatar
Senior Tester
May 16, 2016, 07:05
Out of curiosity... why open a MAME bug to report a real hardware issue? If it's not a MAME bug, there's no need to fill up a report that will be closed with BTANB flag.... My opinion.
User avatar
May 16, 2016, 07:29
I had that post about the issue.
The game has an bug and need to say that is an issue in real arcade. Thus avoiding problem in project with false reports.
I remember Haze saying to RB about mame users saying bugs in Neo Geo emulation being that the bugs are in real arcade.
My act in report is correct thus how I had posted about an bug in real arcade about Twin Cobra in another post.
Thanks for read my post and that God continue helping the life of the coders and others good workers in the project that is in first place of priority in all here.
User avatar
May 16, 2016, 08:37
Thanks Tafoid and Fujix.
God bless.
User avatar
May 17, 2016, 11:08
"Out of curiosity... why open a MAME bug to report a real hardware issue?"

Because documentation matters.
User avatar
Senior Tester
May 17, 2016, 11:39
"Because documentation matters."

I wasn't aware of this, I always thought MAME is for playing games for free. Thanks for enlight me after all these years.
User avatar
May 17, 2016, 13:29
Augusto did good.
Now a search will bring up his entry and stop people from opening a (real) bug entry.

Irony doesn't help I think.
User avatar
Senior Tester
May 17, 2016, 14:25
edited on: May 17, 2016, 14:34
I wasn't saying Augusto did wrong. I was only asking if wouldn't be better, instead opening a new bug for a real hardware issue, report and discuss it first in another place, like EmuChat at MAMEWorld for example. Then write a note directly in source code driver. IMO, it could a better way to document the bug.

As usual, a Developer wasted his time to answer me with a non-sense reply. All of us already know that MAME is in first instance an attempt to document arcades, computers, consoles hardware/software before it's too late.

User avatar
May 17, 2016, 16:05
My opinion is it's extremely valuable to have these kind of bugs that occur on real hardware posted here. MASH then adds the information to mameinfo.dat which I myself often look at ahead of time before launching a game whether I'm using MAME's internal UI or a proper front-end like QMC2 which displays this information when a game is highlighted on the game listing.

Your average user is more likely to read this information displayed in this fashion rather than searching forums or source code.