Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
02108 Sound Minor Always Aug 10, 2008, 20:32 Nov 12, 2023, 13:21
Tester vidpro1 View Status Public Platform MAME (Official Binary)
Assigned To AJR Resolution Fixed OS
Status [?] Resolved Driver
Version 0.126u4 Fixed in Version 0.214 Build Normal
Fixed in Git Commit Github Pull Request #
Summary 02108: vaportra, vaportrau, kuhga: Data East Vapor Trail Sound Driver messed up during game play, tempo all wrong when firing.
Description Data East Vapor Trail Sound Driver messed up during game play, tempo all wrong when firing.
Steps To Reproduce
Additional Information
Github Commit
Flags Verified with Original
Regression Version
Affected Sets / Systems vaportra, vaportrau, kuhga
Attached Files
related to 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 
related to 06974Resolved  cninja: Sound speeds up when fighting with the stage 4.2 boss 
User avatar
Senior Tester
Aug 10, 2008, 21:27
edited on: Aug 10, 2008, 21:27
wrong driver, please take more care with bug submissions.

also if you're going to post 'verfied with PCB' it would also be helpful to supply evidence, in this case a sound recording and the clocks from the PCB which could help. Also the description of the problem isn't even very detailed.

please don't post 'rushed' reports.
User avatar
Jul 25, 2015, 18:04
Also related to 00130
User avatar
Senior Tester
Jul 27, 2015, 06:59
Commenting out line 85 in vaportra.c fixes the issue:
	AM_RANGE(0x1fec00, 0x1fec01) AM_DEVWRITE("audiocpu", h6280_device, timer_w)
Though I don't know if it's correct fix and sincerely I don't understand why this line is in the driver. Shouldn't CPU timers be handled by internal CPU core and not to be driver specific ? For example, in DEC0.C there are games with very similar hardware to vaportra.c and this line in the AUDIO CPU memory map is not present.
I could submit this to GIT but I'd like to have a feedback first.
Note that this change will probably fix ID 00130 and ID 00389
User avatar
Senior Tester
Jul 27, 2015, 09:37
edited on: Jul 27, 2015, 09:38
the h6280 should be internal to the h6280 device, so commenting it out is a hack, yes (as once it's internal to the device you won't be able to comment it out without breaking PCE stuff)

the fact it's in the driver rather than the core is also a hack, but the original core presumably predates that actually being possible.

in fact I believe all games with a 6820 should also have the 6820 internal audio hardware, even if none of the Data East games use it, they just use it as if it were a regular CPU.
User avatar
Senior Tester
Jul 27, 2015, 10:25
By the way yes I can confirm this is definitely wrong - PCB doesn't do it (or does it so slightly I can't really tell) while in MAME it's fairly dramatic and obvious.
User avatar
Senior Tester
Jul 28, 2015, 14:16
edited on: Jul 28, 2015, 15:01
looking at the CPU core it might actually help to implement the timer as an actual timer in MAME (although sometimes that is not good for performance)

right now all the timer counting is done during opcode execution which I'd guess isn't actually correct (it could be, although I feel it's unlikely)
User avatar
Aug 21, 2017, 02:46
Updated flags as per system11 reporting.
User avatar
Sep 9, 2019, 18:01
3f4f237dde89ea02b5a2724f391e3054cfc659d7 fixes this for now.
User avatar
Nov 12, 2023, 13:21
Use of plugin-provided autofire clearly shows that this bug still present.