faeran

Wait for next beta (which should be out next week), and you'll need to let us know if it helps for you.

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

Live Stream Starting Now! Tuesday, April 1, 2025 - 1:00PM EST Live Stream starting now! Join Josh/MysterNybble as he works on an unreleased feature! Ask your burning questions, and learn about upcoming updates in this week's developer live stream. https://www.twitch.tv/launchboxofficial

All hand coded, so no CTC files unfortunately, but if you are looking to do something specific in the code, PM me and I can help you.

This will actually be working in the next update. The issues with this emulator are stated in a few places around this forum, so I won't go too much into detail here. The gist is that it doesn't have to do with whether an emulator is working, but whether a frontend has the ability to send a file path to it that the emulator can read (which is harder said than done on Android). There are two solutions to this, one that an emulator dev can implement, the other that we can implement (via scoped storage). The emulator dev solution is more user friendly, while scoped storage is less user friendly. In saying that, we are in the process of implementing scored storage, as well as going through a giant list of emulators, including Duckstation, and making sure they can launch via one of the two ways. This will be a culmination of a few months of blurry eyed work here, so yeah, we are looking into this 😉

Thanks, we'll look into what we can do about this. I believe it's simply a database change we'll need to make, but something might surprise me. Sounds like we may need a dedicated thread for this type of this in the future.

Thanks. We've managed to recreate the screenshot issue and it will be fixed in the second beta. Would love to hear if Big Box is still freezing in this beta. The goal is to weed out different issues that people have lumped into one issue, and then move forward in beta 2. Potentially the same issue. The issue is the different levels of sleep that Windows machines can go into. Do you know how long your computer was asleep for before you woke it up and ran into this issue. Do you also know what settings you have for which type of sleep your computer goes into. Also, are you running this on a laptop or desktop? Thanks. Was able to recreate this issue and we'll have it fixed in beta 2. A limitation to those sets. If a set doesn't have a logo created for it, it will default back to the default set. Hey, if someone wants to create versions of those categories, I can add them to the sets! We'll look into if this is possible for WMP to support. I really hope so. Not seeing this on any of our test builds. Which option are you changing, or does it matter? If you restart your computer, is it still happening? Is anyone else seeing this happen or not seeing this happen in their builds? Just for a quick update to the Big Box freezing issue. Beta 1 did remove the option to switch to VLC. The goal was to see if this would actually solve the freezing issue for users. So far, from our reports here and other places it seems like it may have removed the freezing for the majority of users that were facing that issue, which does confirm our suspicion. Step 2 is what we are going to do about WMP playing nicer in the situations you guys are bringing up here. We already are in the process of working towards this goal, and beta 2 will have some of those solutions in there for you guys to test. At this point, we burned about 2 weeks on looking at VLC and trying to figure out what the issue may be with it. It's not an issue with what we are doing with VLC, and it's not an issue with VLC itself. Our findings show that the issue seems to be lying in the third party dependency that we use, which wraps up VLC into something usable in WPF applications. The wrapper hasn't been updated in forever, and we'd be beholden to the author to either provide an update to it, or we'd need to start from scratch and find another solution that can wrap VLC up into something usable in a WPF application. We haven't given up, but the time it would take (and risks involved) would be very significant, especially for what we have investigated so far, and if we are looking to build something up from scratch, then it might be a good time to dig deeper and find a more robust solution than we've ever had.

This reads that you have a broken plugin. Possibly the Archive Cache Manager. Remove it from your plugins folder and let us know if that solves it for you.

It's always included there, you just didn't notice before 😉

LaunchBox 13.21 beta thread is now open here:

Hi everyone, LaunchBox 13.21 beta 1 is out now for all willing to help test this release. Thanks to all who help test these beta versions. Don't forget to include the following information in your feedback to help us out with tracking down with any issues you may face with these betas: Your Windows version Description of the issue Can it be reliably reproduced on your end? Reproduction steps You can opt into the beta within LaunchBox by going to Tools > Options > General > Updates and turning on Update to Beta Releases. If a beta release is available, you will get prompted each time the app opens up, or you can manually check using Menu > Help > Check for Updates. Beta 1 includes the following: New Premium Feature: A new section has been introduced under Tools > Manage > LaunchBox Themes & Media, providing users with the ability to browse and download Media Packs. These growing list of packs, created by both the LaunchBox team and the community, include Platform Clear Logos, Badges, Platform Icons, and Controller Input Graphics Packs. The packs are non-destructive, allowing users to seamlessly switch between them on the fly, and can be applied to both LaunchBox and Big Box independently. New packs will be regularly added, and applying or swapping between them is now just a simple click away. New Feature: Content Creators now have the ability to upload Media Packs for community access through the following page: https://www.launchbox-app.com/media New Feature: A new Xemu Integration Plugin has been added, allowing users to download and set up the Xemu emulator directly from LaunchBox Fixed: The freezing issue experienced by some users in Big Box has been resolved Fixed: The false out-of-memory error that appeared when a computer awoke from sleep has been addressed Fixed: The minimize/maximize game launch feature now functions correctly with additional applications Fixed: Game files containing more than one space in a row now launch as expected Fixed: The Nintendo 64DD now displays the required dependency files for supported RetroArch cores Fixed: Long-term stability in Big Box has been improved Fixed: Searching for a game while in certain areas of Big Box would display no results Fixed: Corrupted images cause fewer issues when loading in both LaunchBox and Big Box There's a few things that are in need of testing: The Media management changes: heavy changes were made to the 4 media types in order to accommodate this new non-destructive media pack world we now live in. Things to test would be the LaunchBox Themes and media manager, as well as building your own packs under your LaunchBox\Images\Media Packs\ folder and seeing how they work. Check out Platform Clear Logos and see how they work now, especially if you are used to the old way of how things work. If you were having freezes in Big Box, do some overnight tests and see how you fair now. If you ran into issues with your computer showing an out of memory issue after it goes into a deep sleep, let us know how this fairs now. Beta 2 will come out next week and will contain a few more items that will complete the media management system, along with any further fixes that we are looking to put into this release. Thanks for testing guys.

Live Stream Starting Now! Thursday March 27, 2025 - 1:00PM EST Live Stream starting now! Discussing features, feedback, community hot topics, theming, and answering all of your burning questions about LaunchBox. Join Brian/Faeran, Product Manager at LaunchBox, for his weekly live stream. https://www.twitch.tv/launchboxofficial

Thanks. The known issue that we are currently tracking is that for certain devices touch screen controls do not work on the page where you choose a new database image. We've confirmed that controllers seem to work, and we've also confirmed that certain device the touch screen controls do work on this page. If this is not what you are seeing, please let us know.

Which platform were you trying to use the mamemess core with? Also, were you apply the core via the Emulator Settings menu on a platform level, or using a game override?

Live Stream Starting Now! Thursday March 20, 2025 - 1:00PM EST Sneak peak to some unreleased features. Discussing features, feedback, community hot topics, theming, and answering all of your burning questions about LaunchBox. Join Brian/Faeran, Product Manager at LaunchBox, for his weekly live stream. https://www.twitch.tv/launchboxofficial

Hey all, Beta 3 is now out. For users stuck in that startup crash due to the crash reporting system issue, we'd love for you to test this release to see if this release fixes it for you. If you have downgraded to 1.17, you can simply run the beta update from within the app. If you need a copy of the beta 3 apk, you can get it from here: https://drive.google.com/file/d/1XVFtzBfY9DSdgCfuEeNtJ0yVtLFJxUl9/view?usp=sharing *There's the potential that after you install this apk, you may need to restart your phone. This release includes: The beginning of Scoped Storage support has been implemented. It's in an incomplete state, with more work to come for the next beta Additional Apps on a Network Share should once again download and play Users stuck in a startup crash loop should now be unstuck (introduced in beta 2) Thanks again for the help with all the beta testing.

We have it on our list to look into adding before next release, if possible.

That means the version you installed on your device is not the one you are choosing inside of LaunchBox. Sometimes it could be hard to know, as there's just so many different variants of RetroArch. Which version did you install? and which version are you choosing inside of LaunchBox for that platform?

Can we just call it a win? I've also heard a simple restart of the device fixed a crashing on startup problem a user was having.

Go into the platform in question, click on the top right menu option, enter into Emulator Settings. You'll see a drop down list of a bunch of different RetroArch versions. You'll want to pick the one you installed. I assume if you installed directly from their website you would know whether you downloaded and installed either the x86 or x64 version. Then you'll need to select the exact core you downloaded inside of RetroArch yourself. Sometimes this can be a bit tricky, as we list them out as what their files are called, but RetroArch lists them out as a name that may differ. After that, as long as things match up, you should be good to go. In saying all of that, which version of RetroArch did you end up downloading and installing?

The support mailbox is the only place to get help with license information. If you haven't received a response and it's been over 24-48 hours, I'd send another email just in case your first email got lost or sent to spam for whatever reason. Locking this up, as there's nothing anyone could help you with here, but I'm sure you'll get sorted as soon as possible.

Live Stream Starting Now! Tuesday, March 18, 2025 - 1:00PM EST Join Josh/MysterNybble in the LaunchBox development discussion! Ask your burning questions, and learn about upcoming updates in this week's developer live stream. https://www.twitch.tv/launchboxofficial

Thanks yes. This seems to be a much smaller issue that a lot less people seem to be having, but if you submitted it into our system it's been tracked

We've looked into the issue where the app will suddenly stop opening during startup, which looks like it would have started on beta 1. Essentially, what's happening is that when a user hits a hard crash, our crash reporting system attempts to send that report into our system. Instead of sending the report, the crash reporting system crashes again. If you find yourself in this situation you'll need to downgrade to 1.17 and wait for beta 3, which should be out in the next day or so. Sorry for the headache here.

If you mean the Exit mapping, you can disable that by removing the mapping under Options > Keybard/Controller Mappings