faeran

This does look to be a bug with the downloaded core option. We'll look into it and fix it in the next beta.

Technically, it should work using custom emulator (with code), and some hacky methods (like creating dummy files). However, Vita3k is a fairly unique case and it's next release where we want to develop a very unique import/launching situation specifically for it.

Live Stream Starting Now! Thursday, May 8, 2025 - 1:00PM EST Join Brian/Faeran, Product Manager at LaunchBox, for his weekly live stream. https://www.twitch.tv/launchboxofficial

Beta 6 is out and has the following: We've streamlined the behind-the-scenes process for launching files into emulators, improving compatibility and flexibility, especially for smaller standalone emulators Because of the work above, launching into DuckStation should now work for a wider range of ROM types, located across different storage mediums Reverse Landscape and Reverse Portrait was added to the orientation lock option The import process will now ignore the extracted games folder, if one exists Resolved a minor issue affecting search results Beta 6 will be the final beta of this round. Thanks everyone for helping with this release cycle. Expect a release very soon. We've already begun working on the next release cycle and can't wait to share what we have in store.

Awesome, good to know. Thanks for the feedback. Beta 6 just came out that should address most of what you were seeing. Unfortunately, when we tested Citra MMJ it was having issues. However, it probably makes more sense these days to use something like Azahar.

Live Stream Starting Now! Thursday, May 1, 2025 - 1:00PM EST Let's talk about Arcade! MAME anyone? Join Brian/Faeran, Product Manager at LaunchBox, for his weekly live stream. https://www.twitch.tv/launchboxofficial

Should be back working. Btw, for those that don't know, at the bottom of the page there's a "Themes" button, and there's 4 different options there. The only one that was broken was the Invaders one, which is of course our default. However, the other 3 were just fine.

Okay, we ran a bunch of tests and what's actually happening isn't what you guys were theorizing here. What is actually happening is some limitation with DuckStation when dealing with multiple files (like bin/cue). If you are using CHD files, DuckStation can accept a normal file path and understand its location just fine. No issues. What is happening when you are using bin/cue files, is that it accepts the cue file, then the cue file is essentially referencing all other bin files required to run the game, so DuckStation goes on the hunt to find the bin files and fails due to its own app requiring scoped storage permissions. This is different than an app like RetroArch, which can understand the location of the bin files just fine and you'll see it work without issue. This means in order to use bin/cue files, you'll need to set scoped storage permissions inside of LaunchBox, and set scoped storage permissions inside of DuckStation, both to the specific location of your games. However, right now in beta 5, let's say you give scoped storage permissions to your PS1 bin/cue file folder. This should work, but currently does not. This is where we have a bug that we will shore up before release. There's also another issue with DuckStation and scoped storage permissions when your games are located on an SD Card. That will be fixed up as well before release. This basically means that if your PS1 games are just 1 file, then scoped storage is not required, but if they are more than 1 file, then multiple permissions steps will end up being required if using DuckStation. This will also complicate the use of the network share feature. We'll try to make it work as best as we can, but if you find yourself in a situation where your games are bin/cue, and your games are on a network share, and you really want to use DuckStation, then both DuckStation and LaunchBox would need to be pointed to the LaunchBox\GameCache\Sony Playstation folder in order to function. btw, I would not recommend switching your games to run specifically the bin file. Anyway, we are still working on all of this stuff, but we'll make sure it's working before release even if we have to push it back a little.

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