faeran

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.

LaunchBox itself doesn't really have an upgrade path with MAME. If you do change to a different version of MAME, you'd have to manually copy over your config files into that new version. As long as MAME didn't majorly change the way they handle those files between the versions you are switching to, it should be that easy. As far as favorites, if you have enabled game cloud statistics syncing, they should get automatically reapplied to your games after import.

The game itself would have to support Steam offline mode, other than that you should be good. You can also drag and drop any file onto LaunchBox to import it.

A long while back RetroAchievement's changed their API so that the score received is your hardcore score (as opposed to your softcore score). If you are seeing 0 points it's possible all of your points you earned are softcore points.

Microsoft changed their stuff and broke Xbox integration, which was then fixed in LaunchBox 13.9. You can look for the threads on the subject to point you in the right direction, if you are having trouble updating. For troubleshooting, I'd open up a separate thread in the troubleshooting section of the forums.

There's no Viveport or Oculus import, but if you had shortcuts to all the games somewhere that you wanted to import, you could simply drag all of them all at the same time and bulk import them.

You can simply drag and drop any game exe file into LaunchBox and follow the prompt.

LaunchBox 13.10 has been released. It is a minor release that addresses some issues that were reported with 13.9. Full Changelog: Fixed: The Game Discovery Center was not notifying plugins that the selected item had changed Fixed: The Platforms list in the Game Discovery Center wasn't adhering to settings that would hide platforms or show playlists appropriately Fixed: Sometimes when leaving the Game Discovery Center music and/or video audio would keep playing in the background Fixed: The Test button on the RetroAchievements options menu would always say the credentials were valid, even when they weren't Fixed: A rare error that occurs when trying to load an image in the LaunchBox grid view for a box that is no longer in view Fixed: The selected items on some lists in the Game Discovery Center could be slightly cropped if the user's display was 150% scaling or higher Fixed: Game music wasn't playing correctly within the Game Discovery Center

The above theme is for Big Box, so I assume you'd have to look inside of Big Box and follow the instructions.

One way you could do this is to disable startup screens on an emulator basis. For example, if you have Startup Screens enabled in your Options menu, you can then go into Tools > Manage > Emulators. Enter into all the emulators you don't want to see startup screens for, and under the startup screens section you can disable them.

You do this from the controller mappings section. The input system will then convert whatever button you use there to a filename and then check that folder for the necessary file. If you don't know what your buttons are being registered with in Windows, open a start menu and type out "controllers". Open up the game controllers window, select your controller and look at its properties.

We've recently looked into the latest release of DuckStation and at the moment it's not possible to get it to launch games if you are running newer versions of Android (something like Android 11 or 12 and above). Based on what we currently know, one of 2 things will end up happening before this emulator becomes launchable: The emulator dev releases a new build with dedicated frontend support, or we build a scoped storage solution that will force users to navigate with a touch screen in order to provide the necessary permissions to get around this limitation.

I don't believe there's a screenshot grid type view, but nothing would stop someone from creating a theme with it.

Are you able to open a separate thread for troubleshooting purposes. Remember to include the device you are using, the Android version you are on, and any other pieces of info that could help narrow down what you are seeing, like what happens if you launch the game directly from Citra MMJ (Storage Access Version), and what exactly is happening when you are launching from LaunchBox.

As Jason stated in the other thread, this was an unintended side-effect of third party libraries we were forced to update. We will update the website accordingly to match our most recent version.

At the moment we made sure to make this completely themeable, but that does mean in order to get your own custom buttons, you would need to make a copy of the default theme and then swap out the images that are under LaunchBox\themes\[theme name]\images\Controller

Thanks! ScummVM is one of those things that always gets pushed down the list, but we do have it on the list to tackle at some point! While there's technical limitations here, we are always looking for ways to increase performance and stability. I would open up your own thread with as many details about your computer and your LaunchBox build as you can think of. Thanks. We'll look into this one.