 No.02034
Haze 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. |
|---|---|
|
No.11895
moa Tester
Jul 25, 2015, 18:04
|
Also related to 00130 |
 No.11897
Mamesick 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 |
|
No.11898
Haze 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. |
 No.11899
system11 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. |
|
No.11904
Haze 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) |
 No.14129
Kale Developer
Aug 21, 2017, 02:46
|
Updated flags as per system11 reporting. |
|
No.16874
AJR Developer
Sep 9, 2019, 18:01
|
3f4f237dde89ea02b5a2724f391e3054cfc659d7 fixes this for now. |
 No.21830
VasiliyFamiliya Tester
Nov 12, 2023, 13:21
|
Use of plugin-provided autofire clearly shows that this bug still present. |