faeran

It could either be an issue with where you are placing your music files, or an issue with a setting inside of Big Box itself. Hard to say without more information. For your files, if you want general background music, place it in: LaunchBox\Music\Background If you want platform specific background music, place it in: LaunchBox\Music\Background\Platforms\[PlatformName]\ For playlists just swap out the word Platforms for Playlists above.

Thanks for the report. We are currently cataloging all of the crash reports and we'll be patching them all up as quickly as we can.

It's been a while, but you should be able to wrap the index in a viewbox, and you can control its scale via the size of its parent.

Looks like a bad copy/paste job from another theme. I'll have to update that. Sorry for the confusion.

↓

This theme doesn't contain any views with video support unfortunately. It's possible in the future that more view types could be added that were specifically designed to play videos, but the current version of the theme doesn't have any.

Can you post some screenshots of what exactly you are seeing?

First thought was that I don't believe anything with the startup was adjusted, but we will take a look before the official release. You may also want to think about if you made any changes to your library, or to your device (like a device update). One thing to note is that the more games imported into LaunchBox, the longer it will take to load.

Thanks guys, I do feel even for shorter overviews, we could do a better job of displaying that information to make it more readable when trying to moderate overviews. We'll see what we can come up with.

Hi everyone, Beta 4 is out and this is another large update. This update introduces a brand new Dependency Files section within the Emulator window. We have it working for our supported emulators at the moment, which include RetroArch and PCSX2. Essentially, it's a page where you can find out information on potential dependency files (like bios files), so you are better informed as to why a particular platform may not be launching correctly. If we find that a dependency file might be required, and you try and play a game for that platform, you will get a prompt providing you with this information. If you have time to test this system out, that would be highly helpful to us. Changelog for Beta 4: 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 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

Hi Everyone, We've deployed another round of updates to the LaunchBox Games Database. The complete changelog: Enhanced the upload process with PNG and transparency checks for specific image types. A user-friendly interface for advanced search options located next to the search bar has been added. The Changes Status and Moderation pages have been optimized for better readability. Refreshed the look of game lists by providing background images with the box art displayed on top.

Can you post a screenshot of everything inside of your LaunchBox\Data folder and all their subdirectories? It's possible that could help see what's going on with your build.

Sounds like you only had your game files on the SD Card? If so, you could adjust it on a per-platform basis. If you enter into one of your platforms, then open the top-right menu, you'll find an option called Change ROM Folder Paths. You can do this for each one of your platforms to update paths for all of your games.

Would love that too, however Android is much more sandboxed than Windows is, which essentially means that one app cannot monitor or affect another app while it's active.

Beta 3 is out and should have a fix for what you were seeing. If you have time can you check and confirm?

Hi Everyone, Beta 3 is now out with the following: Videos can now be streamed directly from YouTube using the video URL metadata point found under a game's Edit Metadata page. These streamed videos will appear in the same places as local videos would normally be displayed. You can enable this feature via the options menu An option to download and save streamed videos directly from a game's Edit Media page has been added You can now track your Play Time and Play Count on a game's Edit Metadata page, with the option to reset those counts for a fresh start This update introduces the YouTube Streaming feature, which leverages video URLs from the LaunchBox Games Database. Now, any game view that supports background or foreground videos can display YouTube content. A one-time library optimization is required when you first enable this feature, which makes sure your build is ready to stream videos. While we're adding some final touches before release, it is fully functional and ready for testing.

That file is only used if you decide to import MAME games using our ROM Import wizard. It's essentially a fallback file for when we can't use MAME itself to generate the exact information based on the version you are trying to import.

I don't think I've ever heard of this particular issue before. The only Retroid device I have is the Pocket 2 plus, which we test heavily on. I also have a similar setup to you with how I've set up the device. Sorry that I can't tell you more here. If a crash report is generated we would have received them and if so, we can look into what potentially could be causing it.

I think those are images. You can go into the LaunchBox\Themes\CoinOP\Media\Controller folder and swap out the buttons there with ones that better match your cab. Might be because it's late here, but I'm not fully understanding this question. Maybe you can rephrase exactly what you are wanting to accomplish and I'll see if I could help.

The Startup screen feature is the screen that comes up right after you launch a game, which tells you that the game is loading. Fairly certain it's enabled once you apply your license and unlock premium features, so if you are stock, I assume they'd be on. If they aren't, can you turn them on and let me know if you are still experiencing the same issue. In Big Box, it's under Options > Game Startup In LaunchBox, it's under Tools > Options > Gameplay > Game Startup and well as Tools > Manage > Emulators > [emulator] > Startup Screen

Just for some clarity: Are you using LaunchBox or Big Box? Are you using startup screens?

Beta 3 is out with the following changes: 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 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: Fixed an issue that caused an error to sometimes appear when retrieving the version information within the Manage Emulators window Fixed: Improved stability to prevent the app from crashing when canceling an emulator download We have some major Big Box stability improvements in this one, and any help with long term Big Box stability testing would be much appreciated.

Thanks, we can't reproduce that in-house, but we should be able to see that crash happening in our reporting system, so hopefully we'll see what exactly is causing it for you.

I think for this part you maybe are expecting the Region to Prioritize field to do something that it wasn't intended to do. The way media downloads work is that it's solely based on the file you intend to import. It's actually a complex process, but to put it simply if you try and import a Japanese game, we try and match it with Japanese media. This is based on the file name, so if the game is called "Game 1 (Japan)" , that tag indicates that it's a game from Japan, and therefore we should do our best to match it with Japanese media for that game. Can you elaborate on the exact steps you are taking to get the crash? Also, which version of the app are you using?