Jason Carr

LaunchBox for Android 1.0-beta-6 is out now with the following: Fix for the selected media not always updating properly after searching Fix for videos potentially playing in the background and never stopping if you navigate inside a platform and back out too quickly Fix for videos not playing immediately after importing (requiring an app restart) Fixes for the issues with Nvidia's broken updates to the Nvidia Shield TV software (still requires Nvidia's latest hotfix, see here: https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481434/shield-experience-upgrade-90-hotfix-image/ ) Per the Nvidia Shield TV issues that have been plaguing folks who updated to the latest Nvidia firmware, we've confirmed that the latest hotfix from Nvidia does fix it. So that, combined with the using the latest beta, should fix the issues that people are seeing. Unfortunately, though, getting Nvidia's hotfix is somewhat convoluted. I'll be posting steps to update and fix the issue in a new thread here shortly.

I will review this before the official release. That is not an issue that I've ever seen before. I suppose it's possible that it was a corrupted download or something similar. Other than that I really don't know why that would be happening. There should be no difference from beta 4 in that regard. Let me know if you can get it working by just trying again. @mosestyle @thewhite You shouldn't have any issues using the exporter in the latest version of LaunchBox for Windows. It should no longer require any XML modifications at all. Those issues were fixed with the latest desktop release. Let me know if you're seeing differently.

Hey all, LaunchBox for Android 1.0-beta-5 is out now with the following: A new "Wheel with 2-Column Details" games view has been added for foreground videos Many video fixes, including fixing video playback while games are running Fixed Citra MMJ to work properly launching games with the new Storage Access version We're getting close to a release, but we do have to add the video support to other views and fix a few remaining issues. These are known issues with beta 5 that need fixed: If you go into a platform and out of it too quickly, the video may start playing and not stop after you leave the platform You may have to fully close LaunchBox and restart the app after downloading videos or the videos might not play correctly Thanks all! Let us know how testing goes, and the device that you're using.

Yes, we have considered CDNs. But considering the amount and total size of the media we serve, as well as the dynamic nature of the games database, it probably wouldn't be easy, nor would it be cheap.

That theme happens to be the "Old Default" theme. You'll need to change themes to the actual "Default" theme to see the changes. The "Old Default" theme is kept around for people who don't want the changes.

It really doesn't matter. Norton is trash and reports more false positives than true viruses. Every release we work hard to get around these ridiculous false positives, but we aren't always successful. I highly recommend uninstalling Norton and never buying or using any third party anti-virus programs ever again. Just use Windows Defender that comes with Windows. It's all you need.

Unfortunately renaming an mp3 to a wav file will just result in a broken wav file. Some apps will ignore this error, but some won't. We're using DirectX to play those files directly, which isn't going to work with mp3s. So that's why the sound pack is broken. You'll need to convert the mp3s to wavs properly. For what it's worth, renaming file extensions like that will often break things lol, so it's generally just not a good idea at all. There's also a setting to turn off navigation sounds while in attract mode, so assuming that you're referring to those navigation sounds, that's probably what's going on.

This is definitely a one-off issue with that machine, and it looks to be a driver issue. See here: https://answers.microsoft.com/en-us/windows/forum/all/computer-restarted-reason-code-0x800000ff/35ce1abc-7000-4ec8-b73f-f3c0816eaaa3?auth=1

Don't really have any idea why your sound pack wouldn't work. I'd have to see the pack.

Look for an "Attract Mode Volume" setting in Big Box. It's either in the Sound section or the Attract Mode section.

Unfortunately this file is just way too big for a single file download here on the forums. It will need split up into several files. I believe the limit is 2 gigs.

Thanks all; I have the translations updated. Not sure if we'll be putting out a beta today, but if not, they'll be in the official release tomorrow. That's the plan.

Unfortunately there's always going to be tradeoffs, unless we have servers all over the world, which would be prohibitively expensive. 5 minutes to download a 250MB update might seem like a long time, but users in the US were sometimes seeing updates take a half hour for that same 250MB file because the servers were in the Netherlands, which was borderline unacceptable. Those deep-sea cables can only transfer so well, apparently, though I would have hoped for better speeds. The speeds may improve in the future, but unfortunately we can only do what we can do.

Thanks guys, I have those two translations in for the next beta, which should be out later today.

It was, thanks. Should be fixed now.

We now finally have our forums server moved over as well. So we're done with server migrations now.

Looks cool, but doesn't really seem to be anything worth switching to, in all honesty.

Sorry for this. I forgot to move something over when I transferred to the new server. The downloads are back and working again.

If the Fire device is on Android 9, then scoped storage isn't even a thing on those devices. Scoped storage wasn't released (or at least not required) until Android 11. We've also fixed the scoped storage issues in Android 11+ in the latest LaunchBox betas. But unfortunately, this issue is unrelated, and is specific to the Fire devices. We have not yet put significant effort into tackling the storage issues on Fire devices, so I don't have any documentation at this point. We've had our hands full with the scoped storage issues, which we just recently fixed.

Hey all, it's that time again. We're hoping to put out the next official release this coming Monday. Thankfully, we have a little bit of extra time for once. Thank you guys very much. @Kondorito @Cauptain @Nyny77 @Opak @dukeemu @cyanjiang @Just001Kim @MajKSA @gamehacker @alexposad @k_kutsugi @Bardock @Soomin papa

@Soomin papa I have the translation updated for the next beta, which should be out later today. Sorry for the delay on that.

Unfortunately we've learned that the Amazon Fire devices are troublesome when it comes to storage. I have no idea why they differ from Android storage everywhere else, but apparently they use different storage security mechanisms. Either that, or they're just broken. As of yet, we have not figured out how to fix the issues with external storage on Fire devices.

What device are you using? What version of Android is it running?

Make sure you've downloaded the cores in RetroArch and you've added any necessary BIOS files. If you're still having trouble, we can help you troubleshoot one platform at a time. It would be wise to start with an easier platform that doesn't require a BIOS, like SNES or Genesis.

To bring this thread back on track, I spoke with Tahlreth, the AetherSX2 developer a few days ago. I was as careful and polite as I could have possibly been, but unfortunately he has no interest in supporting frontends or allowing frontends to launch games in AetherSX2. He ended the conversation with "I might just make the activities private next update", suggesting that he is going to completely disable any chance of frontends launching games at all. So unfortunately that is bad news, but it is his choice if he does not want frontends to be able to launch games in AetherSX2. From what I can tell, his reasoning is that he wants users to use his user interface only, and does not want it to be hidden or bypassed by a frontend. So, for now, we have to give up on supporting AetherSX2.