Jason Carr

@Zombeaver By chance, is the platform for the additional app different than the platform for the original game? Currently, it always uses the platform for the original game since there isn't a platform field on the additional apps. I just tested though and it does seem to be working fine using the proper command line parameters for the platform listed on the game.

Oic, I looked at your screenshot lol. You might want to run chkdsk on that drive, as it's possible that more is corrupt than just that folder. Generally corrupted files and/or folders are a sign of either a bad drive or file system issues (can also be caused by removing an external drive without ejecting it properly).

Wow, interesting. How was it corrupted? File system errors?

Ah! I just figured out you're from Bitbucket. Yes, that's the error. What folder on your hard drive do you have LaunchBox installed to?

What is the specific error you are getting @Old School?

Oh crap, you know what, I forgot that the export process has to run on the server first. That will run tonight and then I expect that it should finally work properly. Sorry for sending you on a wild goose hunt @Pacman56.

Still planned, but not in yet guys.

Hi @Pacman56, this was caused by incorrect metadata from the LaunchBox Games Database. We fixed the metadata in the live stream this morning, but LaunchBox only downloads it once a day. You can force a new metadata download by removing the LastMetadataUpdate line from the Settings.xml file; that should fix it.

That is a pretty cool idea, @ckp. Can't jump on it right away though. We should definitely add a ticket for it.

Alright all, beta 16 is released. Basically just fixed minor bugs found from Bitbucket, the automatic reporting, and this thread. I am planning for this to be the release candidate unless something major comes up. Hopefully we can put the release out tomorrow.

Thanks guys, by chance, could it be happening on imports? Have you been importing any new games or using any of the new merging tools?

Also just fixed using folder names on imports; however, manual combines and expands and consolidations won't work properly when using folder names currently, unfortunately. We'll have to address this after the official release.

@Pacman56 Just fixed those issues in the live stream; thanks for all the details. Take note that you will need to make sure that you download updated metadata from the LaunchBox Games Database for the entire fix. This will be out in the coming beta later today.

Thanks for going through all that trouble, @Izegod, I know Bitcoin can be a royal pain. Unfortunately PayPal is pretty much scum of the earth, and they wouldn't let us use them even if we wanted to. Details are here: Glad you're all set.

No problem @CliveBarker; always understandable! We'll most likely go through with the release tonight or tomorrow.

Hi @adu, please create a ticket for it using Issues/Requests in the header. I do have to focus on the most popular requests first, but we will get to it in time.

Possibly, though I need you to test.

Thank you @Bardock! I have the latest translation integrated for the next beta, which should be out later today. @CliveBarker @cyanjiang Planning to put the official release out tomorrow morning; let me know if you guys are still working on the translations.

Yup, please do @porterballs! It's appreciated!

Planning to go ahead with the official release tomorrow (Monday) guys. It looks like the music null reference bug has indeed finally been fixed (praise the Lord) as it hasn't come up since beta 15 came out yesterday. Hooray! I'm expecting that this should fix any remaining stability issues in LaunchBox and Big Box; let me know if anyone sees any additional issues.

A genius indeed! You've out-programmed me @Grila!

Again guys, back on topic please. I don't see that kind of discussion as productive. @MerlinArcade You might be on to something with the cron job thing; truthfully I hadn't thought of that. Let's discuss it in a different thread though if you want to continue the discussion.

Hi guys, I appreciate the discussion here, but let's keep new features discussion outside of the beta testing threads (at least new features that don't apply to what's being worked on currently). @MerlinArcade That is a feature I've always wanted to add, but it isn't quite that simple, as sometimes adding games with media and everything else can take a significant amount of time, and there are a number of options available as well. I just put out beta 15 now guys; the last two betas were to add more details to the errors to try and catch that blasted music null reference bug. Thankfully I finally have it down to the method that disposes the previous music player and media that was last played. I have a possible fix in there as well, so we'll see how this one fares. Also, for what it's worth, @MerlinArcade's been doing his best to figure out how to do all this legally, and came to me early on to ask how to get a hold of legitimate licenses to LaunchBox, so no issues there.

In the latest beta, guys, is the new multiple ROM versions stuff. What you *could* do is just put in two different additional apps for the game, each with a different emulator. This stuff is new in the latest beta, but that should allow you to do exactly what you're looking for, though there's no way to set it up automatically in batch.

Beta 13 is out now guys. Unfortunately we did not, in fact, fix that music null reference bug, so I've added some more logging into the music code to see if we can figure it out further. Unfortunately at this point I'm wondering if it's a bug with VLC itself, much like we've run into in the past. I'm tempted to do something extreme like throw all the music code into a separate process so that it can't affect LaunchBox or Big Box if it goes haywire, but that's not exactly a good solution either. To clarify for anyone who hasn't been following this issue, this happens both in LaunchBox and Big Box only when using music in one way or another. Sometimes it causes a random crash, sometimes it causes a NullReferenceException error with no stack trace, and sometimes both. I have been able to replicate it myself, but it happens so rarely that it's been really hard pin down. So anyways, this is the last thing to resolve before we're ready for a release, but I refuse to put it out until we finally lay this to rest. This bug is gonna die, one way or another.