stensgaard
-
Posts
12 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by stensgaard
-
-
BigBox needs to be restarted to update a "recently played" playlist I made .. pretty sure this has not always been the case?
everywhere else in BigBox the recent list are working fine
also in the last beta my clock was showing as 24H format, and now it back to am/pm ...
-
found a dipswitch setting called "Ranking Save" that make the game save the highscores!
but now launchbox says " Aborting MameHighScores.Prepare: Dip switches were tampered with."is there a way to toggle the dipswitch called "Ranking Save" without triggering the tampering thing?
hope someone can help?
-
anyone know if there is a way to get your hiscore manually if the auto sync thing failed?
I have a .log file, the nvram file, the hiscore file and a personal record, that was just not uploaded :,( -
14 hours ago, TrailerVert said:
I also had cloud sync turned off or unchecked.
isn't Cloud Sync supposed to be turned on?
-
just to add to the post above, I had the exact same problem with dig-dug ... and the solution was the same!
if I delete the hiscore and nvram files for the game, AND then uses an old version of mame (in this case .239) it all works again .. and the hiscores are uploaded!can anyone else please check if they can upload dig dug hiscores with .260 or never?
-
Batsugun:
anyone have a suggestion as to how to fix this?
TRACE: structure definition 10109e:04:00:00101166:70:00:001011b5:01:15:15 does NOT match hiscore.dat definition 10109e:04:00:00101166:50:00:151011b6:20:00:001010de:30:98:fb
ERROR: unable to find a structure from the xml definition that matches size and hiscore.dat definition' for game 'batsugun'is there anything I can do, or is this just something I need to wait for someone else to fix?
----update---
the above in with mame .260..
I just tried it with mame .239 and everything worked just fine ...??
-
On 5/19/2023 at 6:40 AM, kajunpoon said:
i found that it's someting wrong with the game Blazing star. Other games are fine for MAME High Scores, but only blazing star has problem. the hiscore of this game is store in nvram, but it couldnt update nvram, no matter run by launchbox or run directly by mame. Theoretically, it will not upload any scores to the leaderboard, but it did one time. And you can check the leaderboard, so many guys' records are the same: 250000. Is it a bug of this game? Mame and romset 0.254
i tried many times to run the game by mame directly, and found that it can update the nvram of blazing star occasionally, but it doesnt most of the time. It is irrelvant to bios.
Just played Blazing Star 2 times .. and the first time I scored 305.310.. but that score was put on the scoreboard as 250.000??
then I played the game again, and this time I only scored 256.690, and this was correctly put on the score board ...Looking at the score screen in the game, it says some thing like
ALL = 305.310
1 = 256.690
2 = 48620
3 = -------and so on .. so I'm guessing the score app gets confused by the ALL part??
I have attached the .log if that helps
-
is there any way to figure out why some games don't send hi-scores to the Community Leaderboard?
(like is there a log file where I can search for errors?)I just tried setting a hi-score on Eyes (US set 1) which is the version listed as supported.. the game saved my score, so that I could see it the next time I booted it up .. but my score did not show up on the weekly Leaderboard, which is empty at the moment, there are lots of scores in the yearly, and since not a lot of people play this (brilliant) game, my sad score should have been in the top10..
I know the score uploading works since I uploaded a (not very impressive) score from muchi muchi pork a few hours earlier
So if anyone know how to track down this issue, please help...PS i just installed launchbox yesterday, and upgraded to this beta right away, so I don't know if this is a new problem or an old one?
LaunchBox 13.13 - Beta Thread
in Beta Testing
Posted
this also happens for Mame games with the latest beta .. never seen this problem before!