faeran

Live Stream Starting Now! Thursday, April 17, 2025 - 1:00PM EST Time to go behind-the-scenes here at LaunchBox, plan out feature releases, and AMA. Join Brian/Faeran, Product Manager at LaunchBox, for his weekly live stream. https://www.twitch.tv/launchboxofficial

Yeah, can definitely see that. We probably could do something like that, keep it restricted to just a background pic, but let's say that happens, the pic used would either have to work well in a multitude of aspect ratios / orientations, or you'd have to provide multiple images that would be used in different aspect ratios / orientations. A great landscape image might not be great in portrait mode. I'm sure something could be worked out though. If you haven't already, get something into our feature request system here: https://feedback.launchbox.gg

Can you be more specific about a few things: Version of Duckstation Type of files you are trying to launch The actual file under the game's metadata that is being used to launch the game Version of Android you are on, and API level (if you can find it) Device that you have

Surprisingly hard to do, but if you take this view file and replace the one under the LBThemes\Big Details\Views folder it should do what you want. GameDetailsView.xaml

Unfortunately, the startup background is not themeable. It's possible in the future we could allow it to be themeable, although if one were to use a theme that has broken code, you'd essentially stop yourself from opening the app. So, there's some risk there that would have to be mitigated. Unfortunately both the original sized image, and the thumb images are used throughout LaunchBox for Android. The thumb is used inside of lists and other places where performance is key. The normal sized images are used in places where quality is preferred and where it doesn't impact performance of the app. If you were to remove either of those folders you'd probably end up with blank spots throughout the app in places you didn't realize. We have talked internally about changing this up to be more device specific, while moving sizing off to our server and having the user download an optimized size based on their device. When that happens, it's possible we could move to a situation where images would not have to be cached for performance reasons. We are probably a ways off from that reality though.

Do you have a Windows N version of Windows? Either way, see what happens if you follow this link to install the Media Feature Pack: https://support.microsoft.com/en-us/windows/media-feature-pack-for-windows-n-8622b390-4ce6-43c9-9b42-549e5328e407

If it doesn't show again, it means that it believes that you were able to install k-lite during the first time. WMP (Legacy) is baked into Windows (even the latest versions of Windows 11), but there are some computers where it comes disabled. The installer simply runs the command to enable it. It's always possible that Windows thinks you have it enabled, but at some point WMP was corrupted in some way. That would explain why videos would show up black when you attempt to play them in LaunchBox. To check this, open your start menu and type in "Windows features" and hit enter. In the window that opens, look for Media Features > Windows Media Player. If it's disabled, check it and hit OK. If it's enabled, disable it, hit OK, then after it does its thing, open the window again and enable it. You may want to restart your computer after you do all of this. That should rule out WMP as being the thing causing your issue.

Thanks. Not an issue with the app, but it does look like our scheduled task to build new copies of the local metadata file turned itself off last week. Seems like this game was added after that happened so it never made its way to user's computers. This should be fixed now and you should be able to run a Tools > Downloads > Force Update Games Database Metadata... , then it should appear in your search.

Are you able to try the update again, when you get to the k-lite install screen, click on this invisible button to open the log file location, then try and install k-lite. If it fails again, open the log file and paste it here. It's not about the controller itself, but it's about your controller mappings, so as long as you have a mapping for "Select", then it will appear in Big Box. Having keyboard mappings sounds like a good idea in general, so I wouldn't rule that out for a future update. That theme will need to be updated to utilize these new bindings.

The way it works has nothing to do to whether a user uses a specific piece of hardware, but has to do with what your settings are under your controller mappings section of Big Box. For example, looks like you have Button 1 mapped to Select, and you have the Xbox controller input graphics pack (which is the default) selected, and Button 1 on an Xbox controller is the A button, so it shows you the A button image from the pack. Let's say you are using an arcade cabinet, and your arcade cabinet buttons are named, you can create your own pack that look like your buttons, then when you select it in LaunchBox/Big Box, they would automatically show you the correct buttons in the default theme there, which dynamically change based on your Big Box controller mappings.

It's specific to if you run LaunchBox from a network drive. It was a number of different issues, but the main one that the user could control had to do if you are on Computer A, running LaunchBox from Computer/NAS B. If you were to try and import games from a mapped network drive that's mapped on Computer A, the file path was showing in a way that wouldn't work. We believe this was due to a security change in .NET 9 to how it handles UNC paths. This specific issue wouldn't have been a problem if you don't map network drives and instead just use the straight UNC path.

It's the images on the bottom right side of the default theme. They will now adhere to whatever pack a user chooses. It goes hand-in-hand with the media pack feature that was introduced in beta 1. Under Tools > Manage > LaunchBox Themes & Media, there's some different packs in there that you can download and apply to Big Box themes that utilize the dynamic controller graphics code. Once the packs are downloaded, you could also set which pack you want to use inside of Big Box under Options > Images > Controller Input Image Type

Beta 2 is out with the following changes: New Feature: The Big Box Default theme now dynamically displays Controller Input graphics based on the currently selected media pack Improvement: MAME Gambling games are now marked as Casino games allowing you to easily filter them out during imports Improvement: Star Rating functionality has been updated so that each star rating grouping uses the raw value instead of massaged values. For example 3.8 star games now appear in the 3 star grouping instead of 4 star as they did previously Improvement: The Star Rating Arrange By functionality now sorts games by star rating within each grouping Improvement: Enhanced installer/updater to install K-Lite Codec Pack Basic, streamline runtime and DirectX checks, and enable Windows Media Player only when needed Fixed: Several improvements regarding file paths when launching from or pointing to a network location Fixed: Several stability improvements for Big Box to stop the application from freezing after running for extended periods Fixed: Bezels for vertical MAME games being applied with a horizontal layout file The main things to make sure, for people willing to test, is that Big Box is running fine after the update for you, video playback is working, and navigating around Big Box poses no issues. For users that like to have Attract Mode going for days at a time, this would be a good time to make sure beta 2 is running well for you guys. For users that were in a position where you were running LaunchBox directly off of a network drive location, we'll love to hear feedback from you as well as to how this version handles for you. We've spent some time on any remaining "out of memory" issues that some users have seen, but have been unable to reproduce this on any of our machines after our initial fix. We'll keep working on it when we can but without actually being able to see it happen makes it hard to try and find a fix for it. If this is happening to your, turn on logging under Tools > Options > General > Debugging, then when it happens look under the folder LaunchBox\Logs, and either post them here, or send me a PM if you are uncomfortable with posting them here.

Would love to hear what is causing you to take the action to scrub WMP from your computer. But right now the plan is to use WPF's default media element which utilizes WMP behind the scenes, as through extensive testing we've realized it's the most stable option at the moment. K-lite will be an optional pack that we highly recommend if a user finds themselves in a situation where certain videos are not playing back properly due to unsupported codecs. The new installer will provide a choice to users to install k-lite codec pack, which we highly recommend to do so users don't have to think about whether they'll have a video playback problem in the future.