faeran

Based on the OP, there's a lot of information missing on where he actually is and what theme he's using to really give any kind of conclusion on what's happening there.

This scenario looks to be working as intended. ChunkRock.mp4 has no relation to either the title of the game, nor the ROM file. Here's another example. Staying in the Commodore Amiga realm, let's say you have imported two games: SpellBound! Spell Bound and I download a video and place it in the video folder, and it's called: SpellBound.mp4 Or maybe I called it: Spell Bound.mp4 Which file associates with which game? Basically, as soon as you go too far with fuzzy matching by guessing if a file has spaces or not, or add any other guesses to the mix, it's easy for the whole system to create false positives. Now in saying all of this, this whole system we are talking about is for fallback purposes. It's always recommended to use the LaunchBox standard naming convention, which in your case would be Chunk Rock-01.mp4. Better yet, users should be using the Edit Game window to associate videos to their game, the system will then choose the best performant way of associating that media to the game.

Can you provide the following information from one of the games you feel isn't working as intended. Screenshot of: Edit Game's General page Edit Game's Launching page The location of the image and/or video and its name

Version 13.13 - Released May 13, 2024 Full Changelog: https://www.launchbox-app.com/about/changelog New Feature: LaunchBox can now automatically download and install the Dolphin emulator during the import or auto-import workflows New Feature: PCSX2 emulator can now be automatically downloaded and installed directly within LaunchBox New Feature: Download, update, and reinstall supported emulators (including RetroArch, Dolphin, and PCSX2) conveniently from within their dedicated Add/Edit Emulator window New Feature: A new "Dependency Files" section is now available for supported emulators within their emulator window allowing you to more easily manage these essential files. Supported emulators include: RetroArch, PCSX2 New Feature: You will now receive a prompt, with potential solutions, when you try to play a game that requires missing dependency files Improvement: The Manage Emulator window now displays emulator versions and update availability for supported emulators Improvement: The default Dolphin command line now automatically includes full screen mode and disables exit confirmation prompts Improvement: Microsoft Xbox xbe hard drive files now integrate better with our auto-import feature Improvement: The advanced search functionality has been expanded to include the following new filters: Broken, Complete, Favorite, Hide, Installed, Notes, PlayMode, Portable, Rating, Region, Series Improvement: Several file extensions have been added to the ROM import blacklist, improving accuracy and reducing the chance of including unwanted files Improvement: "View 3D Box Model" option is now available in the game context menu Improvement: Updated the MAME metadata file that's included with LaunchBox Improvement: The ROM Import Wizard now leverages the new dependency files logic Improvement: All Storefront IDs are now accurately displayed in the combine games drop-down window Improvement: The PCSX2 command line now automatically updates the fullscreen switch when pointed to the QT version Fixed: Wiki/Video URLs correctly update when using "Search for Metadata" from the Edit Game window Fixed: Resolved an issue where GOG games already imported were sometimes re-imported as additional applications Fixed: Auto rom scanning now accurately detects folders in some situations Fixed: The custom field sidebar filter now functions correctly in all circumstances Fixed: Big Box memory leaks have been addressed, allowing it to run smoother and for extended periods Fixed: Searching for games with colons (':') should now yield expected results Fixed: Various potential null reference errors that could occur within LaunchBox have been squashed Fixed: The manual scan for added games no longer gets stuck during the initialization process Fixed: Updating MAME now correctly installs the new version to the same folder (introduced in 13.12) Fixed: Import stability improved for scenarios involving merging new and existing games Fixed: An uncommon issue that could occur during Epic Games imports Fixed: An issue where the set media limit wasn't enforced during imports or metadata and media downloads Fixed: The version badge now displays correctly when combining two GOG games Fixed: A bug where images could incorrectly be linked to more than one game with similar names Fixed: The Amazon Games install flag now sets correctly on startup Version 13.14 - Released May 16, 2024 Improvement: Added a final file matching step for loose media files. This will attempt to better match loosely identified media with games without causing incorrect matches. Fixed: Resolved an issue where the last page of the ROM Import wizard would be skipped in certain scenarios Fixed: Addressed an issue where a Dolphin update would install to an unintended folder Fixed: Updated our internal Dependency Files database with various fixes Fixed: Ensured the Dependency files indicator light accurately reflects the status of files within specific subfolders Fixed: Resolved an issue where using the Dependency files feature to browse for a file could lock the file if you tried to select one already in the correct location Fixed: Resolved an issue with an emulator's configuration information under certain conditions when the emulator is first downloaded Fixed: Improved PCSX2's ability to identify the bios folder location in all scenarios Fixed: Addressed a rare occurrence where the Dependency file lookup would fail when users played a game

The standard way media file matching has worked is by matching the title of the game and switching special characters to underscores and adding numbers at the end. So Bonk's Adventure would turn into Bonk_s Adventure-01.mp4 and if you had a second video for that game it would be Bonk_s Adventure-02.mp4. Whenever in doubt, it's always recommended to use our in-app tools to associate your media files, like through the Edit Game window. We also have fallback logic where you can match it to your ROM filename. So if your ROM file is Bonk's Adventure (Europe).zip, then you could have your video file named Bonk's Adventure (Europe).mp4. It's a bit less performant but does the job. We fixed a bug that was being overly aggressive, more so than its original intent (which was file name matching), which was causing media to associate with games it shouldn't have been. The side-effect of that was for people that might have been loose with their naming of their media, there was a possibility you saw a benefit of media also matching with the correct game (when it shouldn't have based on the logic). We are evaluating if there's a 3rd step that we could add that would help in these situations that would hopefully not re-introduce false matches. In saying that, it is highly recommended to use our in-app tools to rename your media to our standard if you can, as it provides the best association with the best performance. The Edit Game window or the Image Pack importer are good ways to do this. Thanks., We were able to reproduce this, and should hopefully have a fix in the next update. Basically what you are seeing is how the matching system works. There are homebrew games coming out all the time (one of the ones you mentioned is from 2023), which eventually makes their way to ROM sets, but haven't quite made their way to our database. Once they are in the database, and the metadata file gets updated to include them, they will end up matching better. We found a potential issue that I think you may have fallen into, which deals with specifically configured PCSX2's when using our updater. This will be fixed in the next update. Thanks. We fixed all the parts that we could. A lot of what we started with was RetroArch's information, and then built on top of that to try and fill in the gaps that they were missing. The good news is that since we did that (instead of just parsing RetroArch's data), it was easy for us to correct a lot of these, which will be included in the next update. At first glace, these potentially look like user configuration type issues. I would open new threads for troubleshooting.

Would be pretty simple to create a custom view with the data points you would want to see. This video should still be relevant for helping with that.

It would be any folder between your drive letter and the LaunchBox folder. Something like this: D:\Games & Emulators\LaunchBox

The issue of importing ROMs that are already imported should be fixed in beta 7. Are you able to confirm you are seeing this fixed on your end?

Beta 7 is out with the following: Fixed: The Dependency Files page in the ROM Import Wizard now only appears when necessary Fixed: In rare cases, the auto-import wizard could import duplicate files into a user's library. This issue has been resolved Fixed: A potential crash in the ROM Import Wizard has been addressed

👋 Hey LaunchBox Community! We’re exploring the idea of adding a part-time role to our team to help us create various content, from organizing awesome events to crafting engaging emails and articles. Here's what we're thinking: Role: You would be helping to manage community interactions, organizing community events, and producing engaging content. Skills Needed: S-tier writing and communication skills, a solid understanding of community dynamics especially in gaming and emulation, and the ability to wear multiple creative hats. Perks: Enjoy flexible hours, remote work, competitive pay, and the opportunity to help shape the voice of LaunchBox. 🌟 Interested? Send your resume and portfolio (or any relevant examples of your work) to support@unbrokensoftware.com. Tell us a bit about your experience and why you're exited about this role. On behalf of the entire LaunchBox team, thanks for being a part of the community!

Within the application, click the Hamburger menu on the top left. You'll find a license section there that has an apply license option you can use to navigate to your License.xml file.

For each of your platforms, can you use the "Download All Missing media" tool, and then afterwards let us know if you are still crashing.

For anyone that was experiencing longer startup times in 1.13, we just released the first beta for version 1.14. If you can, it would be nice to load up the beta and report back in that thread on how it's performing for you:

Beta thread for version 1.14 has opened:

Hi everyone, We are hoping this will be a quick hotfix type of release that will address a few issues that were lingering since 1.13. To that effort, we just released beta 1 which contained a number of fixes including an optimized startup process, aiming to bring load times back to pre-1.13 levels for users experiencing slow launches. If you were affected in 1.13, please let us know if your startup times have improved! 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: Optimized navigation sounds initialization for faster startup Fixed rare crash encountered when entering an empty game list Fixed unexpected crash occurring when navigating away from a settings page with no menu items Fixed device-specific crash related to internet connectivity detection Beta 2: Improved video handling for Custom Themes that remove the background or foreground video elements, automatically playing a video regardless of the user's View setting The media download process has been optimized for smoother performance, helping devices with limited resources Streaming videos will now automatically pause when your internet connection drops Added media indicators to all default views, so you'll always know when images or videos are being downloaded behind the scenes For Theme Developers: We've added new bindings that will give you more control over showing users when background media downloads are happening. Head over to the Documentation.pdf file in your Themes folder to learn more about these new bindings. Fixed a potential crash while downloading game media, especially on devices with lower resources Fixed crashes relating to the platform saving process Fixed an issue where a screenshot may not have displayed under certain conditions Fixed rare issue where where downloaded images on the games page wouldn't always display correctly until the view was refreshed Fixed an issue where a video's audio might play unexpectedly Beta 3: Improved stability when navigating game lists while game statistics syncing is enabled and while downloading game media Resolved issue preventing touch interactions on some game views (introduced in beta 2) Beta 4: The automatic media download feature will now download media for games that are visible on your screen Fixed the media download indicator appearing incorrectly in some situations Fixed potential crashes in filter sections like "Recently Played"

Do you remember which folder you added your games into within the LaunchBox\Games folder? By default, the system will not import any arcade based systems, so I'm curious how that happened for you. If you have any backups saved under LaunchBox\Backups, it might be best for you to load one of those up using Tools > File Management > Restore Data Backup

I'll reach back out in this thread once we have a beta to see if it improves the time on your devices.

We looked into this. As you know, LaunchBox has a feature designed to help display media files from external sources based on matching filenames. Unfortunately, we discovered a bug in this code that caused unintended consequences. This bug sometimes linked media to the wrong games, or even multiple incorrect games at once. The bug also allowed this association even if the filenames didn't perfectly match the game files, which sounds like what you have going in your library. The bad really outweighted the good here, so we fixed the bug to ensure accurate media association, which then also broke the association for any external media that only loosely matched the game's file name. We will continue to support media from outside sources in the way it was intended, but really for optimal functionality throughout LaunchBox, we strongly recommend using the in-app media tools.

Beta 6 just came out with a few more small changes: Improvement: "Sort Title" on a Platform is now factored in the order when arranging games by platform Fixed: The parent indicator now updates accurately alongside its child elements on the Dependency File sections Fixed: The keyboard shortcut for viewing the 3D box model has been updated to CTRL+ALT+M At this point we are gearing up for the release, which we are hopefully will come sometime next week. Thanks to everyone willing to test this round.

Check your LaunchBox\Updates folder for an older version. You would first need to delete LaunchBox off of your device, and then install the older apk. And just to update, we investigated what has changed and the only thing that has changed during the startup is a check for the new navigation sounds. Not sure why that would take a lot of time on low powered devices (we test for as low as the Retroid Pocket 2+ and haven't seen any slowdowns), but we are looking at potentially a better way at handling that check.

Beta 5 is out with the following changes: Improvement: The ROM Import Wizard now leverages the new dependency files logic Improvement: All Storefront IDs are now accurately displayed in the combine games drop-down window Improvement: The PCSX2 command line now automatically updates the fullscreen switch when pointed to the QT version Fixed: Wiki/Video URLs correctly update when using "Search for Metadata" from the Edit Game window Fixed: Resolved an issue where GOG games already imported were sometimes re-imported as additional applications Fixed: Auto rom scanning now accurately detects folders in some situations Fixed: The custom field sidebar filter now functions correctly in all circumstances Fixed: Legacy versions of PCSX2 will no longer cause the application to open during version lookups on the Manage Emulator and Edit Emulator windows

I see, that makes sense, thanks for following up.

Sorry to hear. This is definitely not the normal experience, we even test on a very similar device. Can you zip up your Data folder from your phone and PM it to me. We can at least take a look at it for you. Thanks for the report. We don't see this happening, but we'll take a closer look and see if anything funny is going on with your example.

Not exactly the way you are wanting to do this, but to identify multiple versions you can audit your games and sort by the Additional Apps column. Other badges do have various ways to either filter or arrange by them. Would be curious to know which ones you feel are missing outside of multiple versions/discs.

Like Retro is mentioning, if you have a specific example where you have an image file named after a ROM you have imported into LaunchBox, that could help track down what is going on with your library. We'd need the name of the image file that isn't linking, along with the launching section of a game's edit window showing the name of the ROM file.