Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
01472 DIP/Input Trivial Sometimes Mar 9, 2008, 20:28 Jul 25, 2008, 06:04
Tester takearushfan View Status Public Platform MAME (Official Binary)
Assigned To Haze Resolution Fixed OS Windows XP/Vista 32-bit
Status [?] Resolved Driver
Version 0.123u4 Fixed in Version 0.126u2 Build Normal
Fixed in Git Commit Github Pull Request #
Summary 01472: flower: Starting a game doesn't always register.
Description After instering a coin, for a one/two player game, the button pushed to actually start the game isn't immediately recognized. It can take several tries before the game actually starts.
Steps To Reproduce Insert one or two coins, then press the button to attempt to start the game. As mentioned, this occurs, "sometimes", but not always.
Additional Information None.
Github Commit
Flags
Regression Version 0.114u1
Affected Sets / Systems flower
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
10
User avatar
No.00077
Fujix
Administrator
Mar 9, 2008, 20:52
Regression in 0.115?
User avatar
No.00078
Tafoid
Administrator
Mar 9, 2008, 21:20
Specifically starts happening to me on 0.114u1 - confirmed.
Not sure as to the reason why, however.
User avatar
No.00082
takearushfan
Tester
Mar 10, 2008, 03:51
For some reason, this error is more severe when using MAMEUI. Using the latest build (including the interum updates), the MAMEUI version requires even more button presses before the game start is acknowledged.
User avatar
No.00098
Twisty
Senior Tester
Mar 12, 2008, 08:10
To me the problem (ie. number of req'd start button presses) seems very random with the official build. I would doubt there's any diff between UI and not on this particular bug.
User avatar
No.01703
etabeta
Developer
Jul 19, 2008, 10:47
edited on: Jul 19, 2008, 10:48
if you overclock CPU0 (the one which reads coins) to 130%, then insert a coin and press P1 start it register the pressure each time (or at least more frequently: it still has to fail to me after 10 tries)

maybe it's a synch problem between the CPUs...
User avatar
No.01707
Haze
Senior Tester
Jul 19, 2008, 12:04
fixed
User avatar
No.01753
takearushfan
Tester
Jul 23, 2008, 04:20
The issue isn't resolved. The same problem still occurres. I'm not sure how thorough the testing was, but the error is still there.
User avatar
No.01754
robiza
Developer
Jul 23, 2008, 06:05
not confirmed. in my build is fixed
User avatar
No.01755
Tafoid
Administrator
Jul 23, 2008, 06:22
edited on: Jul 23, 2008, 06:24
Keep in mind this this was proclaimed fixed on Saturday, two full days after the U1 sources were released. I'd expect it to work for U2. Changing the fixed version to indicate this. Please wait until U2 is released to test this bug.

Just a reminder to Devs to please set the fixed version field when resolving a bug as fixed to avoid tester confusion.
User avatar
No.01782
takearushfan
Tester
Jul 25, 2008, 06:04
Sorry. You're right. As of the U2 update that was just released, the bug has been fixed.