Viewing Issue Advanced Details
[ Jump to Notes ]
neogeo/neogeo.cpp
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
04155 Cheat System Minor Always Dec 26, 2010, 09:50 Apr 27, 2014, 16:03
Tester Pugsy View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Fixed OS
Status [?] Resolved Driver
neogeo/neogeo.cpp
Version 0.140u1 Fixed in Version 0.152 Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 04155: CHEAT.C: tobcd/frombcd errors with invalid number of parameters
Description When running any cheats which use tobcd or frombcd it will cause errors like :-
Error executing expression "maincpu.pb@1000FF=frombcd(param)": invalid number of parameters

The error was introduced by 0.140u1 - it works fine in 0.140.
Steps To Reproduce Make a wjammers.xml cheat file containing this:-

<mamecheat version="1">

  <cheat desc="Infinite Set Time">
    <script state="run">
      <action>maincpu.pb@10008D=99</action>
    </script>
  </cheat>

  <cheat desc="Select Points to Win Match"> <comment>Select the score that you would like to play to. The match will end when a player reaches the total or the time is up - so use in conjunction with Infinite Set Time for the Best Effect.</comment>
    <parameter min="6" max="99" step="3"/>
    <script state="run">
      <action>maincpu.pb@1000FF=tobcd(param)</action>
    </script>
  </cheat>

  <cheat desc="Dirty Test of frombcd">
    <parameter min="6" max="99" step="3"/>
    <script state="run">
      <action>maincpu.pb@1000FF=frombcd(param)</action>
    </script>
  </cheat>

</mamecheat>

Activate either of the cheats using tobcd or frombcd and you will see the console window quickly fills up with errors
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems CHEAT.C
Attached Files
  
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.10633
Pugsy
Developer
Apr 27, 2014, 15:56
 Some time between 0.140u1 and 0.152 this has been fixed, all is good.
User avatar
No.10634
Pugsy
Developer
Apr 27, 2014, 16:03
 Works fine in 0.152, don't know when exactly it was fixed however.