faeran

It just removes the game entries from inside of LaunchBox. You'll then get another prompt asking if you also want to delete ROMs, and then a third prompt asking if you want to delete media.

While my name is not Amy I'll try to provide any help I can. 😉 There's potentially a number of issues you may be facing. Here's what you can try: I'm guessing the issue started during import. If you can, long press over the Arcade platform and delete it from LaunchBox, making sure not to delete your ROMs and Media when those prompts appear. Then re-run the import, but during the second import page de-select the option: "This is a Full MAME Set". Then run the import. This should help you better import your old set. Then, I'd make sure that you have downloaded the core you want to use inside of RetroArch, and then select that core under LaunchBox's Emulator Settings for the Arcade platform, and see if you have any better luck there. You'll also want to make sure that the emulator setting to extract ROMs is turned off.

The Nvidia Shield was historically one of the devices that was used in development, so it should still work.

Big Box is a Windows only app, where the Shield is an Android device. You could potentially run a streaming app to stream Big Box from a computer to the Nvidia Shield. Natively, you could run LaunchBox for Android, which is free for you to try from here: https://www.launchbox-app.com/android-download

Beta 2 is out with the following changes: Fixed: Turning the Cloud Sync feature off and on again would sometimes cause incorrect changes to local sync data More work has been put into the fix for EA app storefront games using the automatic import feature

Sounds good. This just means you are most likely not on the latest beta. If you want to, you can opt into the beta under Options > Update to Beta Releases.

The current beta has support for the different official Citra apps, and I'm seeing support for the Citra core in RetroArch, so that may have been added some time ago.

SD Card access is very dependent on the flavor of Android that runs on your device. If LaunchBox can see your external storage, it should automatically show up in the root of the file explorer popup in situations when you can choose a folder. You can try formatting the SD card to FAT32 on your computer and seeing if that makes any difference for you. Btw, we got the emulator working in the app and will be including it in the next beta.

If you are referring to the intermittent black screen issue that some users are experiencing, it's not something we covered in this beta and is something we haven't yet looked into. It's on a list to tackle, but no ETA at the moment. If you are ever wondering what's included in a beta or release, the changelog should hint at the areas of the app we've touched 😉

The LaunchBox 13.11 beta thread has been opened, and can be followed here:

Hi everyone, We have a new beta out that fixes a number of issues that have cropped up since releasing 13.10. We are looking at this cycle to be a quick hotfix release so these issues don't linger while we wait for the next set of features to be built out. Below is the full changelog. Beta 1: Improvement: The Bulk Edit Wizard will now skip the welcome page when making additional changes Improvement: The GOG login windows will now explain the steps required to successfully import your games Fixed: EA Storefront games would not launch properly in some situation Fixed: Rare Amazon auto-import error Fixed: Additional documents launched from Big Box using a third party document reader Fixed: Context menus within LaunchBox opened via the keyboard's "Apps" key would instantly close Fixed: Achievements in LaunchBox's Game Details pane would double when popping the pane in and out of its own window Fixed: Storefront Automatic Imports would import installed games in some situations where it shouldn't Beta 2: Fixed: Turning the Cloud Sync feature off and on again would sometimes cause incorrect changes to local sync data More work has been put into the fix for EA app storefront games using the automatic import feature For users that are having issues where EA games are not launching, but instead you get taken to the EA app, we would love to hear from you on whether this beta fixes that particular issue. As always, thanks to everyone who takes the time to help us beta test these releases.

LaunchBox itself already accepts merged romsets. I would expect the emulator to accept them as well.

Not sure. We've internally never experienced these types of crashes over about 15 different devices that we test with. However, the next beta will include a more robust crash reporting system, so when it does crash on your end, we will have more thorough notes as to why, so look out for that beta coming very soon.

I'm not sure about how this emulator has developed over the years. I know there was some controversy over it at one point or another. If you update to the latest LaunchBox beta version it comes with support for Citra's official nightly/canary builds, which will probably be the ones to use moving forward.

So you have a complete arcade MAME 0.234 rom set. The core that probably matches up the best is the mamearcade_libretro.android.so core. It's essentially RetroArch's current MAME core. Just note that a complete arcade MAME set doesn't include some necessary files to run some games, like CHD files.

First thing you'll want to do is make sure that RetroArch itself is playing whatever game you are trying to throw at it. Once you have that sorted out, you'll want to make sure to check a few things in LaunchBox to make sure it's pointing to everything correctly: Check the same game's ROM path and make sure it's pointing to a ROM that exists and you've proven it works inside of RetroArch itself Check the platform's emulator settings and make sure it's pointing to the correct version of RetroArch that you have installed, and that you are choosing the correct core that you've confirmed working inside of RetroArch Make sure you completely close RetroArch before trying to launch a game inside of LaunchBox Once all the things match up, it should launch the game and you should see it load properly.

We will be looking into seeing what it would take to include this emulator in LaunchBox.

We are back at it after the holidays and it should be coming soon. We are targeting the next beta for sometime next week.

This is always related to a core mismatch. The next version of LaunchBox will hopefully try and solve this for users so they aren't trying to guess which core they've installed vs. which one to choose in LaunchBox. For MAME 0.261 you'll need to make sure you have downloaded the mamearcade.libretro.android.so core into the version of RetroArch that you are pointing LaunchBox to. You'll also want to confirm that you don't have the "extract ROMs on launch" setting enabled, but I'm pretty sure it's disabled by default.

Yuzu support came in with version 1.10 at the end of October. You'll find it as a supported emulator under the platform's Emulator Settings. Let me know if the Early Access apk can coexist with their normal apk. If that's the case, we need to add a special entry for the early access version.

Backups are located inside of: LaunchBox\Data\Backups LaunchBox\Data\Platforms\Backups If what you are experiencing is Data corruption related, you can go into there and replace the damaged file with one of the files in there. For theme file corruption you can go into the Manage Themes menu and repair the theme from there. The Grid itself only has a game view, so you would naturally only find it under a game list's Change View menu. There's no platform views in that theme, so you won't find it under a platform list's Change View menu.

You may have to do some remapping of your controls. This would be done inside of RetroArch itself. 8BitDo controllers are usually pretty good, but I've never used the Zero ones. Sometimes those controllers have different modes, you may need to switch which mode you are in if that's the case.

You'll want to reach out to support@unbrokensoftware.com for license related issues.

Thanks, we'll be looking into this error for the next beta. I think it's something to do with an expired Amazon Games authentication token. If you already set EnableAutomatedImports to false, then you can open LaunchBox, go into Tools > Manage > Storefronts, and then set the dropdown for Amazon to None or Installed.

Not sure if this is the case for you, but one common reason metadata seems to randomly change for users is when their data files have been altered outside of LaunchBox (like using third party programs that mess with those files). One way you can check this is by going into your LaunchBox\Data\Platforms folder, and make sure you only see 1 file for each of your platforms.