Jason Carr

I see. The multiple high scores tables for a game thing is still a problem, unfortunately. Maybe once we get everything perfected I can revisit.

Hmm, I'm confused why the top and bottom would be cut off. Is part of the screen buried in the cabinet? Unfortunately no. For beta releases, it's important to note that they're betas, so that's one thing that I unfortunately can't change.

Thanks @GreatStone. As long as it makes sense to combine the three Golden Axe tables together, then it should work as-is.

No problem, I removed all those corrupted fshark scores. This has already been fixed in 10.15-beta-1.

Yes, Origin is coming soon.

That's a really good question. It does seem to be a rare occurrence that MAME or the MAME high scores plugin end up botching things, but apparently it does happen. My original solution to this (from way back when we started) was to ignore any name entries that had invalid characters. That did a really good job making sure that no corrupted entries were accepted, but also then refused to accept some valid entries because of so many arcade games that use custom characters, so I had to disable that, unfortunately. Still, that might lead us somehow towards a good solution. We just need a way of somehow generically detecting that the data is corrupted. I know that you have a list of special characters that are valid, though. Would it be possible to check if there are any bogus characters in the names (not including the special characters)? Other than that, I can't think of anything that wouldn't require a different solution for each game.

The first 10.15 beta is out now here:

The different levels of the wheel thing could be the clue that we need in order to fix this. I've tasked @C-Beats with taking a look at it, so hopefully that will lead us in the right direction.

Hey all, the first 10.15 beta is out now with the following: New Feature: An import process for Uplay has been added under Tools > Import > Uplay Games, again working similarly to the latest Steam, GOG, and Epic import processes. Improvement: The Big Box MAME high scores popup should now do a better job of displaying all of the information on screens with smaller resolutions Fixed: Introduced in 10.14, some interface elements were using the system's default language instead of the language defined in the Options Fixed: Rare threading error that could pop up when submitting MAME high scores Fixed: For some reason, Microsoft's DirectInput library fails to load up properly when starting immediately on Windows startup on some systems; we've added a workaround to hopefully prevent crashes in this case Fixed: The Chromium Embedded Framework is apparently refusing to shut down in some cases, which has been causing Big Box to not exit properly on occasion. We're now killing it in that case, which should fix any related Big Box shut down issues.

I'm hoping this is at least improved for the next beta, which should be out later today.

Please see the first post of this thead, @Blitz Mary.

Thanks, I've removed that score. This is another one that we should report to @GreatStone.

I would recommend not deleting anything, and reporting any issues you run into here. If you're having to delete those files in order to get things working correctly, then we have a game-specific bug to fix.

Awesome, that is great to hear @GreatStone. Thank you for diving into that one; I think that's the biggest issue we're currently having. I'm not positive, but it seems to be happening only when no scores are achieved (at least that's when I've seen it). I would prefer if nothing was output in that scenario, because there is no valid data. So either an error or just an empty output would work best for us.

I disabled a small handful of games that were causing problems due to various things, such as the games having multiple high scores tables that can't be lumped together, or using custom high scores values (like times, for example). These were unfortunately disabled because the community high scores leaderboards just won't work well for those games. They may have appeared to work previously, but would have eventually been cause for issues, as the scores were not being properly tracked.

I've seen it several times, including one time myself, but unfortunately that was before we added the extensive logging. I'll keep my eye out for it. If anyone has a log file, please speak up. Looking at the LaunchBox code, it won't read anything from hi2txt unless "Score" is found as a header, so I don't think it's possible for LaunchBox to be running into a read file error like that. That said, I haven't seen a log file either, so that's hard to prove or be 100% certain about without. I'll see if I can't do some more testing to replicate. Thanks @GreatStone.

If you can post us the log file, we can look to see what might have or be happening. Unfortunately we don't have anything to go by without it, so we can't fix anything. The high scores are especially complicated, because there are four layers: LaunchBox, then hi2txt, then the MAME high scores plugin, and then MAME. The log file will help us to identify where the problem occurred. It's most likely a game-specific issue, but we can't say for sure without looking at the log file.

Yes, if you don't add a new score to the in-game high score table, then nothing will upload.

If you change any dip switch settings at all, you risk invalidating your scores for that game. I would recommend not touching them at all if you have high scores uploading turned on.

Yes, please take a look at the first post from the troubleshooting thread above. Post your log files and we can help you troubleshoot.

The more games you "place" in, the higher you'll be on the leaderboards, and of course placing higher up improves your leaderboard position as well. We don't just add up all your scores. We focus on your placement on individual game leaderboards, count them up, and then calculate your position. The high scores were reset (just this once), because the community voted to reset them: