Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Donkey Kong/Burgertime Highscore(*.hi) file issue  (Read 2399 times)

0 Members and 1 Guest are viewing this topic.

rdangela

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 4
  • Last login:October 31, 2020, 10:46:21 pm
Donkey Kong/Burgertime Highscore(*.hi) file issue
« on: February 27, 2011, 09:01:03 am »
I did a quick search and didn't find anything on this

I have been playing a lot of Donkey Kong/Burgertime using Mame 1.39(tried mamext same issue) with highcore support and save state, I am having an issue with burger time and donkey Kong scores. After loading the games and playing, on exit the first time Mame will save state and write a *.hi file used by hyperspin to display on the screen. This high score file(*.hi) for those two games will not update again no matter how many times the games are played. All the new high scores do stay within the game because of the save state, but i was hoping to display them on hyperspin. I have used Mame in hyperspin and alone and both times no luck on having it update the score file, if i delete the state then it will update the *.hi file. I am not sure whats causing this or is it normal for those games? Marble madness works perfectly fine, the highscore file is update on exit of the game. Any help would be great

WhereEaglesDare

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1536
  • Last login:March 24, 2014, 08:47:08 pm
  • Shut Off All The Compactors on the Detention Level
    • My HomePage
Re: Donkey Kong/Burgertime Highscore(*.hi) file issue
« Reply #1 on: February 27, 2011, 10:53:48 am »
Have you tried to delete the dkong.hi file and trying again?

dna disturber

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 154
  • Last login:August 03, 2014, 01:01:22 pm
  • Michael J. was my 1st experiment,cut me some slack
    • Cabinet "Monster Arcade" & Bartop "Futurama"
Re: Donkey Kong/Burgertime Highscore(*.hi) file issue
« Reply #2 on: February 27, 2011, 10:56:28 am »
Highscore support and savestate don't really mix.......

I would suggest just using highscore support....
You don't miss out on anything (just the credits perhaps that you already put in in a previous game but the scores are kept).
Plus it's more stable (as there are sometimes changes in the savestate on a mame-version and after upgrading the savestate couldn't work anymore)

Dna Disturber  :cheers:
Author of PINemHi..
Decipher-dude for the HiToText project..


HiToText 2010.11.4  Vs.  Mame 0.140  ::)
-------------------------------------------------------------------
Percentage of original games in HiToText :  8.09 %
Percentage of original + clone games in HiToText : 10.57 %
-------------------------------------------------------------------

rdangela

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 4
  • Last login:October 31, 2020, 10:46:21 pm
Re: Donkey Kong/Burgertime Highscore(*.hi) file issue
« Reply #3 on: February 27, 2011, 11:22:19 am »
Highscore support and savestate don't really mix.......

I would suggest just using highscore support....
You don't miss out on anything (just the credits perhaps that you already put in in a previous game but the scores are kept).
Plus it's more stable (as there are sometimes changes in the savestate on a mame-version and after upgrading the savestate couldn't work anymore)

Dna Disturber  :cheers:

Thanks for the help, that solved it, I think for some reason in my mind I needed both for the highscore support to work, works great now :)