Jason Carr

Thanks guys, @scree is right; let me know if there's a specific item you want to hide that can't be hidden.

Ah, great idea Nathan. I really like that; I'll add it to the list.

Awesome, thanks @SqHd. It's been really quiet since the 5.4 release, so I'm hoping that's a good thing. :)

I appreciate all the support from you guys, especially in situations like this.

Thanks kamyk. I just put in a safeguard, so that if it does happen, it recovers gracefully (fixes it) instead of crashing. Still not sure how it happened but I've confirmed that things work properly now even when loading the broken file. So I think we're ready for release.

Was that XML file before or after you renamed "Emulators" to "Frontends"?

The file in the zip file crashed for me immediately on load, before I even did anything at all.

Okay, so I see what the problem is. For some reason there are two platform elements in the XML file with the same name, which is what is causing the error. I have no idea how that could have ever happened to begin with though, that's the trouble. Still researching...

There are instances where a LaunchBox crash (a hard crash/freeze) can cause XML corruption, which is one of the reasons for the backups. I'm guessing what happened is that a glitch with 4.3 caused a freeze and resulted in a corrupt LaunchBox.xml file. It doesn't happen often but it does happen. I do have an idea to fix it that is on my list. Are you able to get it to happen again?

Thank you Clive! No worries; I'll be putting out a new official very quickly because of a glitch in 4.3, so I'll get these notes in.

Sorry, I missed part of your post. I will play with the batch edit to see if the images disappear.

That error I've hopefully fixed with the latest beta. However, the error should be completely unrelated to disappearing images; really that shouldn't even be possible, so I'm baffled as to why the images are disappearing. However, I'm wondering if the cache is getting messed up.

Hmm...have you tried refreshing the cache with Tools > Refresh All Images?

Just put out one more beta. Hopefully this one fixes all of the issues. I'll be back on late tonight to put out the official if all is clear.

Thanks @scree. That's the bug I'm hoping I've fixed in the beta I just put out. Can you test? :)

The first thing to try I guess is restoring backup XML files from your Backups folder. Also, if you would, zip up your Backups folder and email it to me at jasondavidcarr at gmail dot com and I'll look at it to see if I can figure out what happened.

Hi @kamyk2000, that's pretty scary. Doesn't make much sense. The images are all stored only on disk, so the only way they would disappear is if somehow they all got deleted. Did you do an image cleanup or anything like that? There are backups of your LaunchBox.xml in the Backups folder, assuming they haven't all gotten corrupted. I'm sure if the new version is this busted, we'll be getting reports left and right. I have been getting reports of a painting bug but it's not corrupting installations. Not to blame your hardware, but it is possible that this could be a data corruption issue with your hard drive, though I can't say for sure.

Thanks @scree. I'm getting reports of errors relating to the sidebar painting though. I just put out a new beta that I'm hoping fixes it. Let me know if anyone sees the error in the 5.3 or the new 5.4 beta 1.

Hi @Talantyyr, the notes in the blog post are not meant to be the end all. The in-app change log typically has much more information; it does for this release. Documentation takes away from development, so it's always a hard line to walk.

Thanks guys. I think it's finally time to throw caution to the wind and just put out the actual release. Here goes nothing.

Hi @Badhoagie91, in the 4.3 betas (and in the official that should be out tomorrow) there's a new AutoHotkey tab for each emulator that will allow you to add custom scripts for each emulator to deal with closing them out, among other things. We are working to populate these scripts for each emulator. I'll see if I can't get those three emulators working.

Users by default can't edit posts after a time limit. I just moved you to a more permissive group so you should be good to go now. :)

Sounds awesome, @nathanddrews. I'll look forward to following this. Per the subforum, I do think this is the best place. Maybe I should rename it "Collections and Builds"?

Thank you so much for your interest in purchasing LaunchBox Premium. PayPal has unfortunately decided that they do not want LaunchBox business simply because LaunchBox works with console emulators. As ridiculous as it may sound, it seems that PayPal is unable to recognize the differences between piracy and emulation, and they've demanded that we remove the PayPal purchase buttons from our website. If possible, we would encourage you to use the checkout process on our LaunchBox Premium page, as it is just as secure as PayPal. Your credit card data stays with Stripe, which is a highly trusted payment provider. We still never receive and do not store your credit card information ourselves. However, if you have no choice but to use PayPal, simply send $20 USD to <redacted>, and you will automatically receive a license. We are still able to send and receive money, but we are not allowed to put the PayPal buttons up on our website. Update: As of December 8, 2015, PayPal has permanently closed LaunchBox's account and will no longer allow us to take any payments. PayPal's policies are ridiculous and infuriating, but unfortunately all we can do is encourage people not to use PayPal because of their ridiculous policies. If we had had any significant amount of money in our PayPal account at this point, they would have held the money captive for 180 days, as they've stated on the website and in the email we received. Thankfully, we did not have a significant amount of money in the account. Good riddance, PayPal. Thanks and happy gaming! Jason One more update (January 4, 2016): If you're sticking with PayPal for security reasons, we do have to share that PayPal is full of outdated and insecure practices, and cannot be trusted to keep your money or your information safe. See here: http://krebsonsecurity.com/2015/12/2016-reality-lazy-authentication-still-the-norm/

Thank you @Wattoo. :)