Jason Carr

Enable logs then in LaunchBox under Tools > Options > Debugging. Then give it a try and see what shows in the log file under LaunchBox\Logs. You can search for "MameHighScore" to find any errors.

Do you have autosave enabled in your MAME configuration? Do you have a digdug.hi file in your MAME\hi directory?

I have noticed that some games refuse to track or upload scores if autosave is enabled, but that doesn't always seem to be the case.

Beta 3 is out now, and it now prioritizes the .hi file if it exists, and ignores the nvram folder. There are also a few other fixes for games like Rampage, that weren't working previously.

I'm seeing that now too. Apparently if a high score file is present, then the nvram shouldn't be trusted. Got another beta uploading. I also caught a few other issues with certain games.

So I've confirmed that autosave (MAME setting) does indeed get in the way of updating high scores for certain games (such as Ms. Pacman). Just FYI.

Search your MAME folder for all files named plugin.ini, and either delete them or make 100% sure that cheats are not enabled in each file.

Beta 2 is out now, which now scans the MAME nvram as well as the hiscore file. This appears to make everything work with autosave enabled in MAME, and loads up additional previous scores.

Not positive on that, but yes, that is certainly possible. Just depends on if we see any obvious cheaters in the mean time.

That's because 28,000 is the default top high score for BurgerTime. Unfortunately there's no good way to recognize what's a default high score, and what is user-achieved. I realize that's annoying, but once we get some decent traffic it shouldn't matter much, since high scores that are less than the default shouldn't be near the top of the list anyways.

I think the nvram change I'm uploading for beta 2 should fix that. I'm not positive though. However, we may add more anti-cheat stuff in the future, which may make it so that only newly achieved records are tracked. If we do that, then old records won't ever go up.

Oic. This stuff is different than the plugin. But yes, LaunchBox themes will need to be modified. I haven't added anything into Big Box yet. That's coming.

Cheats need to be disabled in the plugin.ini file. This brings up a good point though...how do we remove old records if someone goes and disables cheats? Not sure what you mean by a theme. Yes, two PCs can both connect to the database at the same time. Only the highest score will be listed on leaderboards.

Per multiple PCs, it's connected with your LaunchBox Games Database account. Nothing is submitted unless you have an account connected. So no duplicates will be submitted unless you have multiple accounts for some reason.

I actually just realized that you can pull scores from nvram as well. It will pull previous high scores currently, but only if you previously had the hi scores plugin enabled (I think). I'm currently making some tweaks to pull them from nvram as well, which I *think* should actually make it compatible with autosave as well. Testing all that.

Congrats on Donkey Kong!

Hey all, 10.12-beta-1 is out here:

Hey all, the first 10.12 beta is out now with the following: New Feature: A new MAME community high scores system has been built that allows you to share your high scores for MAME arcade games to compete with the community! You can enable uploading your high scores under Tools > Options > Integrations > MAME in LaunchBox; your high scores will then show up in the game details sidebar. Improvement: All third-party folders that used to be in the root of the LaunchBox folder have been moved to a new LaunchBox\ThirdParty folder, just to keep things clean and tidy. These folders will be moved to their new locations on first startup of the new version. Improvement: Custom theme game images will now optionally use the Database ID field when matching up file names (for Big Box theme developers) Here's a visual example of the new MAME community high scores feature in the LaunchBox side bar: Please note that the community leaderboards will show up by default, but high scores will not be submitted until you check the box to upload them from the Options page here: Please be sure to read all the text on this page, as there are some very important notes here to get you set up. Eventually we'll add a troubleshooting forum post and link it from here, but for now of course we can do any troubleshooting here. The process to set up MAME high scores is somewhat involved, but I've done my best to automate it and do everything that's necessary in the background, if you check the Upload box. If you're trying to test and/or submit high scores, please be aware that in order for anything to be submitted, or display in the list, you have to actually succeed in achieving a high score on the game's high scores list. Some games have a high barrier to entry with their default leaderboards, and nothing will show up or be submitted until you beat at least the bottom score. One easy way to troubleshoot is to check to see if there is a .hi file that matches the name of the MAME ROM in the "hi" subfolder of the MAME emulator directory. If nothing is showing up there, then LaunchBox won't have anything to sync, and the issue is likely with MAME. Finally, I've put lots of debugging information in the log files, so if you're having trouble, make sure you enable logging under Tools > Options > Debugging, and then take a look at the logs. Also, be sure to include the log files when reporting issues here. I think this MAME high score stuff will be awesome once we get it going in the community. Looking forward to using it myself. Oh, one more thing, there are lots of other related features coming, such as support for displaying the leaderboards in Big Box. Feel free to make requests, however.

I see. Sometimes emulators have weird quirks that cause certain scripts to behave differently in LaunchBox vs. Big Box. I'll see if @C-Beats can replicate.

Just for clarification here, the Backups folder shouldn't affect anything in this situation. But yes, deleting the platform file from the Data\Platforms folder should do the trick. There are some rare circumstances where unexpected or corrupted data can cause issues like this. If you still have that platform file @javi363636, I can take a look to see why the platform was not going away.

Not a bad idea @duerra. I'll put it on the list of items for the next poll.

@Jakatsu Thanks. Will review here shortly.

@Wastedgoat Is that screenshot what you were running into?

@ExtraCredit If you could turn on debug logging on the machine that it's not working on, try it, and then send us the logs, we can troubleshoot this further.

Yes, we all work remotely from home. Always been that way.