Viewing Issue Advanced Details
[ Jump to Notes ]
dataeast/cbuster.cpp
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
03393 Sound Minor Always Aug 16, 2009, 22:17 Aug 16, 2009, 22:56
Tester HyperDuel View Status Public Platform MAME (Official Binary)
Assigned To Resolution Duplicate OS Windows XP (32-bit)
Status [?] Closed Driver
dataeast/cbuster.cpp
Version 0.133 Fixed in Version Build Normal
Fixed in Git Commit Github Pull Request #
Summary 03393: Crude Buster and all clone roms ( cbuster): Music goes fast when someone is using a flame attack
Description In MAME when you get the first stage's miniboss (the guy in the suit with a flamethrower), when he uses his flamethrower the music goes twice as fast. Now I own the Two Crude PCB (US version of Crude Buster) and when he does the flamethrower attack the music doesn't speed up. I wish I have a way to record footage from my PCB but I don't have any way to do it. Please take my word on it.

This is my first bug report, if I did something wrong please let me know. I have more bug reports to list shortly.
Steps To Reproduce Play the game (on any cbuster rom) and get to the first stage miniboss. Wait for him to do the flamethrower attack and hear the music.
Additional Information vaportra.c drivers might also have the same flamethrower problem as well, I must check.
Github Commit
Flags
Regression Version
Affected Sets / Systems Crude Buster and all clone roms (cbuster)
Attached Files
  
Relationships
duplicate of 00389Confirmed  cbuster, cbusterj: The tempo of the music played by one of the OKI6295's (#1 I think) speeds up when the flamethrower is used 
Notes
1
User avatar
No.04823
Tafoid
Administrator
Aug 16, 2009, 22:56
 The submission is fine except for "affected sets".. please list the parent set as it is in MAME, it's setname. "cbuster and clones" would be adequate.

Notice this bug is already mentioned here: 00389

I don't want to discourage you from posting valid bugs, but please make sure you have FULLY researched a problem to see if it's already been addressed, previously noted or even already fixed. Make good use of the link to "View & Search" page and it's powerful searching filters. Duplicate work only wastes time for you and those testing.

Marking this as a Duplicate and closing the bug.