faeran

Get up on the beta and see if that solves your issues with a lot of these, although tbh flycast hasn't had issue in a long time, so I'm kind of wondering what you are doing incorrectly there.

Thanks. Yes, this is a duplicate. The issue is that there's some risk with deleting platforms that have been populated into everyone's local database file and potentially library. So once we feel confident to take the risk to potentially break some things in LB, we'll get to deleting it. For now, GameWave lives on! 😁

Never seen it open in the background before, even on my machine that has 4 different resolution and scaled monitors, but it's good you caught it. For anyone reding this, the only reason this installer would take any time longer than a minute or two is if your computer has WMP uninstalled, but that step would happen after you hit the install button in that screenshot, and would only be needed on Windows N versions where the optional media feature pack wasn't installed, or if you are using some kind of modded version of Windows that removed it. Yes. As an example, if you are wanting to make a playlist for all games with 4 star rating, one thing you can do is click on the filter button and choose the 4 star rating filter option, then click on the filter button again and choose to save the filters to a playlist. If you view the Auto-Populate tab, you'll see the correct rule that you can use in any of your playlists.

Just chiming in with my 2 cents, but seems like you are already on the right track. This is not a bug. Here are some articles that should be helpful: https://feedback.launchbox.gg/help/articles/0459065-launchbox-media-pack-feature-version-1321 https://feedback.launchbox.gg/help/articles/4008205-creating-platform-icons-media-packs-for-launchbox-and-big-box

Sounds good. That makes sense. We will add it to the list to look into. The first thing is to check all PS emulators and see what they require to play the game. If only Duckstation requires a specific bin file, then that could pose problems, so here's hoping it's all standard across the board. This will probably not make it until next release. Those multiple bin track versions are a pain.

Locking this thread, as the beta is over. Anyone with a user specific issue can create a dedicated thread for it in their appropriate section, if you are looking for troubleshooting help. For anyone experiencing a crash, please report it by pasting the entire crash log, along with all relevant context, by clicking on the top header menu, HELP & SUPPORT > REPORT A BUG Thanks for the feedback. This makes sense. While we know that the default will end up being WMP, we didn't want to force k-lite on any user. However, by skipping the recommended course of action, users should expect that some things may not work as intended. All checks in the current rendition of the installer are just that, checks. If a user is deemed to already have something like a .NET dependency, the C++ dependency, or the k-lite dependency, then the installer will bypass it automatically. If a user has all dependencies, then the installer/updater will complete without user action required. This is the first release where we can actually say that, as before there was a mandatory Direct X installer that required UAC action for every update, which is no longer the case. As the warning states in the app when you switch to VLC, that playback engine is in a deprecated state, it's only there until we can find and implement an alternative, and users should expect problems when using it, whether it be performance, crashes, or freezes. If you run into any of those, then we recommend that a user switches back to WMP before asking us for help so this can be ruled out as the issue. Alternatives are being actively looked at. Some are instantly not an option, as the feature set is just not there, but there are other wrappers that have some promise. This process is going to take time, but we are hopeful to have one ready by next release. ScummVMImport.dll is not an official plugin (it was made by a community member), so in order for that to have made it into your plugins folders, it would have been manually downloaded and added by a user.

Seems to be the opposite to what you are saying in our findings. Newer versions no longer needed scoped storage due to a change in the app, but that change required different launching arguments. However, in saying all of that, it's a moot point. Beta 5 now allows you to choose to launch the app in either the frontend supported URIs or the scoped storage URIs for Duckstation, and based on what we've seen, the app accepts both for all of our hardware/software combos. If you do wish to try, report back here with your findings, including all listed in the first post.

Live Stream Starting Now! Thursday, April 24, 2025 - 1:00PM EST LaunchBox, Assemble! It's Live Stream Time! Join Brian/Faeran, Product Manager at LaunchBox, for his weekly live stream. https://www.twitch.tv/launchboxofficial

If you have time, see if beta 5 helps with your situations of launching Duckstation. You should now have the option of setting or clearing Scoped Storage permissions in the emulator settings. You can check both scenarios and see if either work for you. Our testing showed that for all of our devices Duckstation did not need scoped storage, but it might be different on your device.

Beta 5 is out with the following: Introduced an option to clear Scoped Storage permissions on the GameEmulator and PlatformsEmulators settings pages Added Scoped Storage blacklist for emulators incompatible with Scoped Storage access - Currently has Flycast on it Implemented default platform configurations for various libretro cores: mupen64plus_next_gles3_android for Nintendo 64DD picodrive_android for Sega Pico o2em_android for Philips Videopac Plus sameduck_android for Mega Duck b2_android for BBC Microcomputer System virtualjaguar_android for Atari Jaguar CD mamemess_android for Interton VC 4000 scummvm_android for ScummVM Resolved a crash when launching games in the AetherSX2 emulator Addressed a rare crash during game imports Fixed an occasional crash while displaying images Corrected a rare crash when clearing the platform image view Other than a few smaller things, we are at the stage where this represents the majority of version 1.18. Any testing that can be done on emulators and emulator launching would be much appreciated, as the entire system got touched in some way or another to accommodate for all the changes for this release.

What language is your OS in? and what language do you use inside of LaunchBox?

That definitely doesn't look right. I went to figure out why it might be displaying like this for you, but I only found that it didn't seem to be broken in all the tests we could throw at it. Unfortunately, makes it a bit hard to determine why you might be seeing it display this way, especially since both LB and BB use the same "everything" when dealing with 3D Models. You mention that Dreamcast points to a "Box" by default, but actually Sega Dreamcast will use a jewel case model by default, so that kind of points to some kind of user configuration issue, although I'm still not sure why that would be. If you right click your Sega Dreamcast platform and Edit it, can you take the following screenshots: Details Folders 3D Model Settings Also, for this specific game, can you edit it and take a screenshot of what your 3D Model Settings look like.

Looks like by fixing something else with Platform Clear Logo Overrides, this broke down. Should be fixed before release. To answer your question, we are working on a searchable knowledge base. It doesn't have a lot of info on it yet, but are you able to ask it your question and see if it actually gives you the answer you were looking for? https://feedback.launchbox.gg/help

Beta 3 is out with the following: Improvement: MAME High Score logic is now more robust, and the following games are now working/working again thanks to the hard work of our community: Batsugun, Bubble Bobble, Dig Dug, Mushihime-Sama Futari Black Label - Another Ver, Viper Phase 1 Improvement: Some minor visual improvements for the installer, along with the ability to download and install WMP, along with the ability to enable it if turned off Fixed: Playlists with no games were incorrectly appearing in the root of the Platform Categories view Fixed: Improved long term stability in Big Box if using the Related Games feature over many days We have the following known issues: The installer is incorrectly skipping enabling WMP if K-lite is already installed - Will be fixed for release We are in the process of bringing back VLC as a deprecated video playback engine (use at your own risk type of deal), but it's not fully ready yet, but you will see the option has reappeared - Will be fixed for release Some computers are still getting false out of memory prompts after returning from sleep - May be fixed for release, or by beta 1 of the next release

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.