faeran

First thing you'll want to do go into the Options and turn off the following options: Automatically Download Missing Media When Needed - This will use background processes to download media while you are browsing, which costs performance modern devices can easily spare. Cheaper handheld devices would want to turn this off and download media using the manual process. Enable Video Streaming - Although downloading and watching videos are nice, cheaper handhelds may struggle to constantly be streaming video, so having this off would be beneficial. You'll also want to use a view that requires minimal media. In total LaunchBox for Android can download and display a total of 5 different types of media per game, which can be a lot for a small device. Using a custom theme like Pure, which only needs 1 image per game, could help your situation out a lot. Go into Manage Themes, download that theme, open the Global Theme View Options and switch the game view to this, and see if that helps. Not sure it will solve all your issues, a low powered device will always be a low powered device, but at least there are some things you can turn off and be mindful of that could help that device out a bit.

You don't need to mess with the CTC. Find the other banners in the theme's file structure and just place it along with the rest, just make sure the name of the banner is exactly the same name as your platform. You may or may not need to refresh your image cache after you do this inside of Big Box.

At least for your first issue, after app startup, if you simply change from one sidebar filter to another, does that kick in the badges?

I have a feeling this theme doesn't include a PS Vita banner, so it fell back to the generic banner that's included with LaunchBox. You could create a banner or see if someone has already done so, and include it with your version of the theme and that should fix it up for you.

Just to give you guys a bit of an update with this specific error. We think we found out what the issue is. This seems to be happening when user-submitted content that lacks necessary metadata enters the queue. From the moderator side, you see the next change on the list attempt to load, but the game lacks essential metadata and cannot be loaded. What we have done: We reviewed the queue and deleted all changes that lack the necessary metadata, so things should be running smoother now What are we doing: We need to identify all the ways changes can be submitted incorrectly and plug those holes We need to continue to review the queue for any new changes that users submit that have the required information missing and remove them At least for right now (until it happens again), the queue should be running smoothly. We are prioritizing the rest and will have it in place as soon as possible.

Unfortunately, things are more isolated on Android. If the Android app has an exit button, that would be the easiest way to get back to LaunchBox. Most emulators have something like this built in, but each app would need to individually support some kind of exit button.

If you were to tell LaunchBox to utilize the 64-bit version, this version has no code in place to send a core to it, so I'm not sure where the breakdown i, but sounds more like you have a configuration issue inside of LaunchBox at this point. Our integration is designed to always utilize the latest stable release of both RetroArch and its cores. If you are wanting to not use the stable release, but use something more custom, you'll want to use either the standalone 32-bit of 64-bit releases which does not utilize our automated RetroArch app/core download processes.

Beta 4 is out with the following fixes: Fixed: LaunchBox now handles Amazon Storefront scans without encountering unexpected termination Fixed: Keyboard shortcuts now function within the Audit window, providing easy access to context menu options Optimistically, we are hoping for the official release to come out next week. Thanks all.

Since that's a RetroArch settings that's supposed to lock the core you are using, not much we can do on our side. What you'll want to try is go directly to the RetroArch's website, download the x64 version of the app and install the apk and get the emulator set up the way you would like. Inside of LaunchBox for Android, go into the platform's Emulator settings and switch to RetroArch 64-bit sideloaded version. This version specifically doesn't have any of the auto-core logic. My best guess, without testing your specific device, is that the red magic 8 is not providing data about itself properly, so it's possible that we ask red magic 8 "hey tell us about your device so we know which core type to send", and it returns an incorrect value.

I'd be curious to know what device you have and what version of RetroArch you are running. Both the actual version and the apk version (which apk you installed). However, to answer your question, in RetroArch, Load Core, then enter into Information > Core Information, then scroll down until you see the option to Lock Installed Core. Once that's on, the core can't be altered.

The old option was replaced and standardized so that more emulators can now be updated in this fashion, with more to come.

Beta 3 is out with the following: New Feature: Added option to prevent emulator update checks by right-clicking and selecting "Don't check for updates" while in the Manage Emulator window Improvement: Translations have been updated Fixed: LaunchBox now correctly handles clicking on the LaunchBox or Big Box exe files while its minimized to the system tray (introduced in beta 1) Fixed: A crash related to using the new game save quick filters (introduced in beta 2)

The issue you are having is that you are trying to use the clear logo image type for an image that's not a clear logo, which is why you are seeing it show up in the spot that you are. To use your example, this is a clear logo. This is a fanart background: Here's what those 2 look like in the playlist details:

The only reason I've ever seen for the play button to not exist is if the ROM file the game is pointing to is inaccessible. If this is the case though, the button gets replaced with text that should read something like "unavailable".

After setting the button, restart LaunchBox, and see if that makes it work.

Go into Tools > Manage > Emulators Find your RetroArch emulator and edit it. Click the Update button.

If a ROM is multi-regioned, you should be able to see that in the list and make your own decisions on what to do for that specific ROM.

Just curious. This thread was about Android specific imports. Since this post a number of features were included to help situations like the OP out.

Based on the limited info, I'm going to guess this is unrelated to beta and potentially user data related. If you'd like, zip up your Data folder and PM it over to me and I can take a look. Based on what you said so far, we've been unable to recreate this. Send me a PM and we could try and troubleshoot this with you.

This is by design due to MAME's unique case of needing matching versions between the emulator and romset. The MAME plugin contains all the logic we already had within the program, and therefore in order to download MAME you need to use the MAME Arcade Full Set wizard. Nothing has changed in that respect. The primary benefit of decoupling existing code into a plugin is the idea that we can fix the program in-between major updates, and allow legacy versions of LaunchBox to have better support in the long run.

Thanks for the report, we'll look into this. This is most likely specific to your data files. It's possible one of your platform's game folders is pointing to a location that no longer exists. If you go to Tools > Manage > Plugins, what Dolphin plugin version are you on? If there are any updates, definitely download them.

Well, glad you figured it out. I'm not seeing any of that happening on my Samsung Phone, but I do believe my phone is a bunch of years newer than the Note 9, so there's possible software differences there.

You made it to the right place, no need to move. In your options, find the one called: Hide Bottom Navigation Bar. That should get rid of it for you. At least it just did on my Samsung device.

Hi all, Beta 2 is out with the following: New Feature: LaunchBox now offers save management capabilities (In Early Access). Automatically track and organize your saved games and save states, starting with RetroArch support and expanding to more emulators in the future. Import multiple save files for the same game and back them up locally to the Vault, all conveniently within the game's edit window New Feature: Quickly identify games with save files using new badges. Distinguish between saved games and save states at a glance New Feature: Create custom playlists effortlessly with enhanced auto-population options. Filter by saved games or save states to build tailored playlists New Feature: Efficiently find games with save files using new on-the-fly filters. Quickly browse through your collection based on saved game and save state availability Improved: Visual elements were added into Big Box trial mode (introduced in beta 1) Fixed: Custom fields visual issue has been fixed (introduced in beta 1)

Thanks for letting us know. It should be fixed now. Let us know if that's not the case on your end.