Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
02056 DIP/Input Major Always Jul 31, 2008, 16:48 Aug 2, 2008, 08:35
Tester Tafoid View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Fixed OS Windows 2000
Status [?] Resolved Driver
Version 0.126u3 Fixed in Version 0.126u4 Build Normal
Fixed in Git Commit Github Pull Request #
Summary 02056: pbobble, qzshowby, spacedx, spacedxj: Unable to enter coins
Description After starting emulation, you are unable to enter a coin to start play.
Steps To Reproduce
Additional Information Strangely, in the case of Space Invaders DX - version 2.0 works, but the parent set of 2.1 does NOT work.
Github Commit
Flags
Regression Version 0.126u2
Affected Sets / Systems pbobble, qzshowby, spacedx, spacedxj
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
3
User avatar
No.01858
etabeta
Developer
Jul 31, 2008, 17:15
edited on: Jul 31, 2008, 20:06
not really that strange, since spacedxo uses a different set of inputs ;)

anyway, it seems I broke this recently, so I'll take a look to fix it tonight.

EDIT: additional informations:

the breakage seems to come from TC0640FIO_r which is only used by these games in taito_b.c. However:

1. slapshot.c games which uses the same handler work perfectly (and their inputs were modified in the exact same way as taito_b.c ones in u2)
2. even reverting the changes occurred to inputs in u2 doesn't fix the issue

This leaves me a bit lost about which other change could have produced this regression... but I'll keep investigating
User avatar
No.01873
etabeta
Developer
Aug 1, 2008, 02:07
Further investigations show that in pbobble the coins somehow are read when you press P2 keys (by default A,S,Q), while in qzshowby coins seems not to be recognized at all

I'm really puzzled, but I'll try to find out what's wrong. in the meanwhile service coins work perfectly if you want to simply play the games
User avatar
No.01879
etabeta
Developer
Aug 2, 2008, 08:35
I was wrong and it was a stupid mistake in the name of the tags in the eeprom_r handler.

fix submitted.