Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05078 Gameplay Minor Always Dec 1, 2012, 17:34 Dec 12, 2012, 21:17
Tester Brian Deuel View Status Public Platform SDLMAME
Assigned To Resolution Bugs That Aren't Bugs OS MacOS X
Status [?] Resolved Driver
Version 0.147u3 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 05078: cball: The game generates a free credit after a period of time.
Description After a period of approximately 45 seconds, the game will generate a free credit. The behavior also occurs once a game is played and the attract mode runs for approximately 45 seconds. This bug doesn't occur during gameplay.
Steps To Reproduce
Additional Information Tested with both the original set and an old set with MASH's ROM hack.
Github Commit
Flags
Regression Version
Affected Sets / Systems cball
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
6
User avatar
No.09114
Tafoid
Administrator
Dec 1, 2012, 19:16
edited on: Dec 1, 2012, 19:30
It is a prototype and behavior would seem to suggest that the auto crediting is there to assist the game maker to not have to fuss around with sending a coin up signal while developing. I'm inclined to think this falls under BTANB. It's way to specific behavior (esp not happening during game) to believe it's an accidental emulation problem.
User avatar
No.09115
Brian Deuel
Tester
Dec 1, 2012, 20:33
The prototype status didn't cross my mind when I filed this; you're probably right. I could ask Owen Rubin if this was the intended behavior, but he may not remember. He seems to remember a few units of the game being sold, but cannot recall this with complete certainty.

I could trace the code through the debugger to be sure that this isn't a bug; another thing I didn't consider while filing this, all before having my coffee...
User avatar
No.09116
NekoEd
Senior Tester
Dec 2, 2012, 00:56
Acknowledged while this is researched.
User avatar
No.09119
Brian Deuel
Tester
Dec 2, 2012, 20:39
Here is Owen Rubin's response:

"No, would never have added that on purpose EXCEPT that there may be a Free Play mode, and that might not kick in until that reset. Also, that game was written very early in Atari's arcade games with processors, and the coin routines were very simple. Noise on the coin input might credit a coin actually, but I would expect that to be more random."

I guess the next logical step would be to trace the code, see if there's a timer in there for this behavior, and see where it automatically coins up...
User avatar
No.09120
Tafoid
Administrator
Dec 3, 2012, 01:41
edited on: Dec 3, 2012, 01:44
I took a cursory look through ram using integrated debugger for MAME (-debug)

$003a = a counter which starts at a value of $40 (64) upon reset and counts down.
$003d = credits in system (maximum 2).

- Periodically, $003a decreases by $01 at a steady, but staggered rate as the game shows flashing "GAME OVER"
- Upon coining up, this timer at $003a stops decrementing and during the played game, this value stays the same.
- Game ends and credits at $003d are back to $00, the game resets the value to $40 as the process begins again.
- Once $003a hits a value of $00, the credit value at $003d gets incremented by $01 and the timer stays at $00. It does not seem to attempt coining another credit.

This seems to me to be very deliberate programming to an end and would, to me, qualify as original behavior.
User avatar
No.09132
Brian Deuel
Tester
Dec 12, 2012, 21:17
edited on: Dec 12, 2012, 22:08
I'll have to agree. It may be an unfinished free play mode or something that someone (if not Owen) put in for testing purposes. It is a prototype, after all. I'd call this one resolved/BTANB, but will send Owen your findings for his comments...

EDIT: Owen's response:

"Thanks. The countdown timer was to manage the attract mode reset. I had the only prototype and sadly gave it a way a long time ago, so probably from the game I had in my house at one time. What I find strange is that this game went on field test, and I do not recall that behavior. So maybe this is from a different prototype? This could be a bug, but is is definitely not behavior I would have done on purpose."

Hmmm... I'd still call it BTANB, since its in the actual game code. I sent him a picture of the only known prototype board, and he doesn't recall some of the mods done to it, so either there was a second prototype that he doesn't recall, or someone else modified it later. His handwriting is on the ROMs of the picture I sent him, though. The mystery continues...