Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
08666 Misc. Minor Always Jun 16, 2023, 20:07 Jun 25, 2023, 05:12
Tester Balthier View Status Public Platform MAME (Official Binary)
Assigned To hap Resolution Fixed OS Windows 10/11 (64-bit)
Status [?] Resolved Driver
Version 0.255 Fixed in Version 0.256 Build 64-bit
Fixed in Git Commit 59e0d82 Github Pull Request #
Summary 08666: All sets in segahang.cpp: Coin counters increase at each boot up even though credits are not being added, coin inputs not working correctly
Description When running a game, the coin counters numbers in the machine's cfg file will increase by 1 on each start up even though credits are not being added by the user. The 6 key for Coin 2 only increases the first coin counter.
Steps To Reproduce 1. run any of the affected games ( ).
2. let the game run for a little bit, just don't add any credits.
3. exit the game, go to your cfg directory and examine the game's cfg file. The coin counter numbers should be at 1 now.
4. run the same game and repeat step 2.
5. repeat step 3, and the counters will now be at 2.

Now try pressing the 6 key in-game to add credits, only the first counter will increase.
Additional Information Example sharrier.cfg after one run, no credits added:
<?xml version="1.0"?>
<!-- This file is autogenerated; comments and unknown tags will be stripped -->
<mameconfig version="10">
    <system name="sharrier">
            <coins index="0" number="1" />
            <coins index="1" number="1" />
Github Commit
Regression Version
Affected Sets / Systems All sets in segahang.cpp
Attached Files
There are no relationship linked to this issue.
User avatar
Jun 17, 2023, 11:21
coincounters incrementing at boot is fixed (8255 tristate again)
I think coincounter #2 works fine, it's similar to turbo, where it only counts when Coin A/Coin B dsw differs.
User avatar
Jun 17, 2023, 16:05
Thanks again, hap. I have a few more reports to file for this autoincrementing problem. Luckily it appears that this wasn't some global problem in mame and isolated to only a small amount of drivers.