faeran

Thanks for the reports. Both of you guys had different pieces of the puzzle that I was able to use to deduce what exactly might be going on here. I've pinpointed a specific control in the Game Details panel which ended up being something you wouldn't think could be causing this. It's those little quick link buttons that open to a game's LBDB, Steam, GOG, Wikipedia, or Video page. I removed them from the Featherweight theme and uploaded a new version of it on the forums. If either of you guys can confirm you don't see that freeze using that theme now, this would confirm my findings here.

Thanks for the report. Can you be more specific with regards to what system you are trying to import, and the exact steps you used to import?

Look out for a performance FAQ that will be out later today which will educate and explain how users can reliably post feedback about a specific issue and get helpful answers. Outside of that, let's keep this thread specific to the beta changes, as there's some very specific infrastructure changes in this beta that could have affected things we weren't anticipating that we'd love to catch during these beta rounds. Thanks for anyone willing to help test.

Hi everyone, We did deploy a small(ish) update to the database in preparation for a few things. Sharing the changelog here where we can discuss any questions anyone might have regarding the changes. There will be more to come for database changes before the end of the month, so stay tuned. Added support for Poster, Square, and Icon image types for games Fixed issues causing corrupted changes in the moderation queue Fixed a few game locking system issues As far as the new image types are concerned, users have the ability to upload images for these types at the moment to start populating the database, but keep the following things in mind with regards to what they are for: Poster: A 2:3 aspect ratio image representing the main image of the game Square: A 1:1 aspect ratio image representing the main image of the game Icon: A small icon that represents the game in question

Hi everyone, Beta 1 is out now with the following improvements and fixes: Improvement: GOG Import Wizard will now only show games you have yet to import Improvement: GOG Import Wizard is better optimized to show all installed games on your hard drive Improvement: You can now set the auto-import platform per storefront in Tools > Manage > Storefronts Improvement: New comparison types have been added to auto-populate playlist string-based rules which allows for multiple values: Contains Any Value, Doesn't Contain Any Value (ie. Version - Contains Any Value: Rev 1; fr; Brazil) Improvement: Users now have the ability to disable the Save Management Feature under Tools > Options > General > Save Management Improvement: The Game Discovery Center in the Trial Mode of Big Box will now see all curated server-side playlists Improvement: Added support for the following new image types (Poster, Square, Icon) Improvement: A new link binding has been added to the LaunchBox Game Details view for additional apps that point to a website (for theme developers) Fixed: Some advanced search fields with boolean values now work as intended Fixed: The Install Emulator page within the ROM Import Wizard will now better reflect existing emulator installations Fixed: List View better respects column sort order after adding or editing a game Fixed: BIOS detection in the ROM Import wizard now considers RetroArch core changes Fixed: Prevented unintended auto-imports for certain platforms Fixed: LaunchBox Carousel element rendering issues under certain conditions Fixed: Rare crash when loading non-existent images into the image grid Beta 2: Fixed: Issue causing slow loading times of the Game Details Pane on initial startup Fixed: Crash that occurred when attempting to import into a platform without a supported emulator (introduced in beta 1) Beta 3: New Feature: Added the ability to import ROMs from several platforms at once Improvement: Optimized the startup process for slightly faster load times Beta 4: Fixed: Secondary platforms under Associated Platforms will now correctly respect M3U checkbox settings Fixed: A rare issue where specific custom themes could incorrectly sort games when using Arrange By options Thanks to anyone willing to help us test these beta changes and provide feedback about them! We are currently working on a feature for this release that should be out next week that will require lots of testing. Thanks again

Can you open a separate MelonDS thread in the Android section and provide a number of details about your device, along with the exact version of MelonDS you are running, along with whether you downloaded it from the Play Store or from their github.

Looks like the way it currently works is there's a theme specific image prioritization system that will display images in the following priority order: Display Storefront specific screenshots, including: Origin, Amazon, GOG, Epic, Steam Display the Fanart Background group (as determined by user settings) Display the Screenshot - Gameplay image type

Hi Everyone, I apologize for this being long overdue, but this update has taken a long time to put together due to the change in framework that we were forced to make with this update. We've switched over from the deprecated Xamarin.Forms framework to the MAUI framework. With that comes under-the-hood changes to almost everything in the entire application. As a user, you will not see much visual differences, however, do know that there's a higher risk with this update than with any others, so please, if you wish to test this update, back up your data files, and your theme files, before running this update. Now that we are on MAUI, all frontend code had to slightly change. This means that the first time you launch the app after the update, you'll see a prompt that informs you of us needing to optimize any custom themes. This process will edit your theme files, which will eliminate custom theme specific errors that we were able to identify. However, do know that while you may not get errors, all custom themes did not some kind of custom code changes to them. At this stage, I believe all themes except the Colorful - Flex theme has had a version bump in the theme manager for users on beta 1, so if you use a specific custom theme, you'll want to head into the Theme Manager to download all updates before providing feedback. For making you wait for this necessary framework change, we also wanted to make sure it was worth it, so we also added a brand new feature that's been long requested, Network Share Support! To give a little context, Android itself has no global network share support within the operating system itself. Where Windows has built-in network support that any application can take advantage of, Android requires each app to create their own support for network shares. Since we are a launcher that sends file paths to other applications, that's becomes a bit problematic, as we'll be sending a file path to a network share that the emulator itself has no idea how to access. Therefore, the way our network share support works is that you first run the import process. You'll notice a new section when choosing a folder path for network drives. Choosing that will allow you to see any publicly available networks. If it's hidden behind a username/password, you'll be asked to authenticate. If your network share is truly open for anonymous users, you'll be able to make it right in. You can import your ROMs in the exact same way as before. Any games in your local "cloud" will be marked as such. They'll get there own little badge that will display on most default views, and you have the ability to filter by them as well. When you play a game that's on a network share, we will download your file into a local location and send the local path to the emulator. We have a few more improvements with this system yet, but it's working good enough for testing at this time. There's more in this update, so check the full changelog, and if you do decide to help us test this update we are very grateful. If you crash on the beta, we've already received the report, but the following information will be helpful for us to recreate the issue: Your device specs The version of Android and API version Description of the issue Can it be reliably reproduced on your end? Reproduction steps You can opt into the beta within LaunchBox for Android by going into Option and turning on the Update to Beta Releases option. If a beta release is available, you will get prompted each time the app opens up. Full Changelog: https://www.launchbox-app.com/android-about/change-log Beta 1: Network Drive Support: Import games directly from your local network drive. When launching a game, they will download locally Local Game Indicator: Games stored on your local network are now easily identified by a cloud icon for all default views New Filter Option: Quickly filter your game library to view only local or non-local games Customizable Screen Timeout: Control your screen timeout independently of Android's system settings Expanded Emulator Support: Added full support for CEMU and Lime3DS emulators (yes, we know) Framework Overhaul: Upgraded to the latest MAUI framework for improved performance and stability Fixed Play Time Sync: Resolved an issue that could cause inaccurate play time tracking Android Game Parsing Fix: Addressed an Android game parsing issue on startup for certain Android based VR headsets Beta 2: Optimized archive extraction logic during game launching Fixed an issue with additional apps not appearing Fixed crashing that was caused by image rendering Fixed a crash during RetroArch/Dolphin emulator installation Cleaned up RetroArch cores including a decommissioned version of mupen64plus and set different default emulators for SNK Neo Geo AES, Arcade, and SNK Neo Geo MVS Fixed a rare black screen issue during navigation Fixed a crash related to LongPressListView scrolling Fixed compatibility issues with certain fonts (for theme developers) Fixed many reported MAUI related crashes

The much easier way to accomplish this would be to use the FlowVideo element. Video Marquees are a standard thing in LaunchBox these days, so you can assign your video marquees directly to the game itself in your library. Then just use the following code in that view and position it where you want using a Grid: <coverFlow:FlowVideo VideoType="Marquee" DataContext="{Binding ActiveGame}" PlayVideo="True" PlayAudio="False" FallbackToDefault="False" /> That should just play a game's video marquee file if one is assigned to it.

When you say LaunchBox's video recording? Do you mean that you set up OBS using the OBS integration options, and you are using that to record video of the game?

It should be as simple as what you did there. Cores don't really need anything special to function. I mean this one does need a bios file, but sounds like you already have that sorted out if the same game is working in RetroArch that isn't working in LaunchBox. A few things you can check. First concentrate on just one game that you've double checked is working in RetroArch, but isn't working in LaunchBox. Edit the game, go to the Launching section and make sure the path to the file is the same as where the file actually is. Confirm what kind of game file types you have for this game. Is it bin/cue, chd, something else? If it's bin/cue, is the file path pointing to the cue file? Still under Edit game, go to the Emulation section. Is the emulator chosen the correct RetroArch emulator you are expecting it to launch in? If it's not, choose it. If it is, Edit the emulator and make sure everything in there looks good with its Details and Associated Platforms section Under the Dependency Files section, choose PS1 from the dropdown, is LaunchBox seeing the right dependency files there? Let us know how this goes. If you are still having issues, zip up your entire LaunchBox\Data folder and PM it to me and I can help sort you out.

You scared me for a bit there, but after some testing there's nothing different between how version 13.17 and 13.16 handles N64 games and they work the same in both versions. I'm unsure what is happening with your setup, but I just thought I'd mention this just in case anyone else was reading this post. If you ever want to troubleshoot the reasons why your setup seems to have issues with N64 games, we can always troubleshoot with you here.

We think we found this issue and we'll have it in the upcoming beta for you guys to test.

Sega CD runs well with RetroArch using the genesis_plus_gx_libretro core. You just need to make sure you have the correct bios file within RetroArch's system folder in order for this platform to work. PS2, your best bet is to look up the NetherSX2 patch project and see if you can get that up and running.

I assume you have one of those old monitors that even if you turn it off, Windows still sees it. If you unplug the monitor completely, then I assume MAME adjusts accordingly and displays on your TV?

One thing that stood out in what you said was you were trying to match what MAME's display outputs were with what Windows says. Unfortunately, for whatever reason, Windows and MAME do their own thing and those numbers don't match. Looks like newer version of MAME they tried to mess with those display options a bit and it made things a bit more complicated than before. Are you using MAME to display something on your marquee screen or are you using LaunchBox to display something on your marquee screen. If you are using LaunchBox, then you'll want to tell MAME only to display 1 screen, and not 2. In your mame.ini under OSD VIDEO OPTIONS, switch numscreens to 1 to stop MAME from using more than 1 monitor, and put all the screens back to auto. Then adjust the screen value. Switch that to \\.\DISPLAY1 and launch MAME to see which monitor it opens up on, then switch to \\.\DISPLAY2 and see which monitor it opens up on. Pick the one that works for you and save out.

It sounds like a limitation to the auto-import storefront feature. I'll add it to the list for us to take a look at. There are some challenges there, as there's nothing stopping a user from importing multiple platforms where the scrape as value is set to "Windows" making it a question of now where do the new games go?

It's in Big Box under Options > General > Require Holding Back to Navigate to System Menu

Unfortunately, I don't believe this is currently possible. Big Box is designed to pause when another windows is active (ie. a game starts playing).

This would depend on which version of RetroArch you've installed on your device. LaunchBox has support for many different kinds of RetroArch, and it sounds like whatever version you have installed is not the version you are telling LaunchBox to launch into. Go into your platform, click on the top-right menu and enter into Emulator Settings. Choose the version of RetroArch you believe you have installed, and click the verify button to make sure it's the correct one. Make sure you have the correct core selected that you've downloaded within RetroArch as well. Now try and launch your game and see if it works. There are some benefits for using the version of RetroArch that LaunchBox installs, like RetroArch updates and core downloads and such, but follow the steps above and it's easy enough to bypass all of it.

I'm not entirely sure why you are seeing what you are seeing, but I can tell you what LaunchBox and Big Box does after you close it. It first moves any Data related changes from memory and saves them into your Data folder, then it backs up your Data folder, creates an archive and saves that to your Backups folder. Then it closes the LaunchBox or Big Box background process. The larger your library and the more playlists you have, the longer that backup process could take. You could see if Backups is related to what you seeing by disabling them in the settings under Tools > Options > Data > Backups , then seeing if that solves what you are seeing.

Try this: Go to Tools > Import > Steam Run through this import and when you get to the last page, see if your game appears in this list. If it does, finish the import. Deleting a Storefront game in the manner that you did, adds it to an auto-import blacklist. In this way you can delete what you don't want and not have it import again. Then you can use the manual import process to bring games back if you made an oopsie, like you did.

My guess then is that even though the option is off, we must still do some kind of parsing of Android apps. We've marked it on the list to look at to see if we can better help with the Quest.

We haven't heard of this crashing Android in a long time. Some older versions did have an issue with importing a full MAME set. I just ran a test on the latest version but all seems well, however the test involved an external SD card on a phone, and not an external HDD using the Nvidia Shield. I'm guessing you are on the latest version of LaunchBox for Android. There are a few different settings you can play around with during import. Maybe try and toggle on/off the "This is a Full MAME set" option and see if that changes anything for you. It would also be nice to know exactly where in the process it's crashing for you. If you could map that out for us, that could be helpful. We will also check our reporting system to see if we see the crash and if there's anything we can do about it for future releases (after the beta that we have queued up for sometime soon).