AstroBob

No need to re-install, a fresh restart should ensure all instances of the app are closed, though if you continue to see that we have more details on it here: - https://feedback.launchbox-app.com/help/articles/0507346-troubleshooting-another-instance-is-already-running-error

Thanks, this is already fixed and will be in beta-6 Could you elaborate on this, does it happen all the time, or only within certain sections? If you have a screenshot handy showing it that would be very useful. Cheers,

Hi Folks, This may not quite be what you're asking for since it's not for selecting launch screens per-say, but just to call out in the upcoming 13.28 release we're introducing the following feature: Improvement: Improved LaunchBox and Big Box instance detection so separate installs or root folders can run independently without blocking each other You can check it out in the latest beta which is available right now: Would this help in this scenario?

100%, and apologies if it's come across that way, we do our best to keep an eye on the forum but this has got to a point where there's clearly a recurring issue that we want to resolve properly. I can't promise exactly how long this will take but rest assured well do our best to help try and get to the bottom of this. You've already provided a ton of useful info but I'll certainly reach out if we need anything else or have a breakthrough on it. Feel free to DM me if you have any other concerns but we'll keep y'all posted.

Thanks for the reminder. We’ve had a few folks out recently, and we’ve also been heads down working on the upcoming 13.28 beta cycle, which includes a couple of structural changes under the hood. That said, regarding the database work we discussed, we’ve now fleshed out most of the common requests based on everyone’s feedback over on our feature board, which you can access here: https://feedback.launchbox-app.com/?b=679a6bbe1b2011c4928c567b Many of you have already supplied a ton of valuable input, so there’s no need to do anything else. However, if you’d like to, you’re more than welcome to head over there to elaborate on or vote for any existing requests, or submit anything you feel we’ve missed. Of course, simply having the requests listed isn’t enough. However, given the somewhat messy nature of the forum and how easily good information can get lost, we wanted to make sure everything was properly documented there so we can keep future additions well scoped. Outside of that, work is already underway on a fully restructured moderation and guidelines resource over on our new Help Center site, which you can see here: https://feedback.launchbox.gg/help A lot of this is still internal and being drafted right now, since we're looking to release it together rather than as things are ready. But we’re hoping it will provide a much clearer and more structured set of rules, guidelines, and resources for both moderators and submitters. As you rightly mentioned, we do intend to open those up for discussion once we have completed docs ready to share. For full transparency, I don’t have an accurate ETA on when all of this work will be completed or which additions we’ll be making to the Games Database first. As I mentioned, we’re currently very focused on the structural changes coming in the 13.28 release. That said, I’ll do my best to keep you all updated as we’re able to implement these changes and involve the community as much as we can.

Hi Folks, Thanks for the updates on this, and apologies for the delayed follow-up here. We’ve had a few folks out recently, but rest assured we are following these reports closely and doing our best to reproduce the issue on our end. @neosean99 , apologies as I know you’ve submitted multiple detailed reports, which have been very useful. I also want to acknowledge that you’ve already tried the controller-related suggestions multiple times, and I’m sorry if it felt like we weren’t fully hearing that. No need to confirm anything else for now, as we’re using your existing reports to try and nail this down. For everyone else who has been adding info, that has also been very helpful. For full transparency, we have not been able to reproduce this exact behavior consistently yet but we are trying our best to get to the bottom of this. Based on the version range and the behavior being described, we’re continuing to look closely at input handling, especially around controller detection/polling and device state changes. At the same time, we’re keeping an open mind in case there is another contributing factor or interaction we haven’t identified yet. I know this is incredibly frustrating, we're continuing to try and nail this down will share updates as soon as we have something meaningful to report. Really appreciate y'all bearing with us here.

Hi Folks, Thanks for all the continued reports here. We wanted to provide an update on where we’re at with this beta. First, we want to acknowledge the rocky start to beta-2. We really appreciate all the reports, but apologies that many more folks than usual seem to be having issues, particularly around performance. This beta updated some of our core services under the hood, but a lot of issues appear to be largely stem from our new grid implementation. For some context, we completely rebuilt the grid view for this beta with a focus on much snappier responses when quickly scrolling through incredibly large libraries. To get to this point, we had to make the decision to use a fixed grid size (which you can adjust on a per-section basis). While our performance tests have been largely positive compared to the old grid, we are seeing reports of unintended side effects, particularly around images loading into the grid and issues with surrounding elements like badges, which gives the perception of decreased performance. We know that’s not the only related issue, but we initially had trouble reproducing it internally on one of our many builds, as it appeared to be largely library-dependent. That said, after much trial and error, we’ve now managed to recreate a build exhibiting similar issues and already have several fixes in place to help mitigate them. We also want to acknowledge other issues such as the large number of reports around controller issues in Big Box, which have also been fixed internally. We know this only scratches the surface of what people have been reporting, and we’ve been following your feedback closely. Beta-3 includes a number of changes aimed at addressing the biggest issues we’ve seen so far. We may not have fixed everything just yet, but we’re hopeful it will eliminate the major pain points so we can focus on what’s left. Thank you all for helping us test this. We know this beta has been a bit rockier than usual given the scope of the changes, but your reports have been invaluable in helping us identify and address the biggest performance issues, along with a variety of other fixes. We’re hoping to have beta-3 available as soon as possible so you can probably halt with the beta-2 reports for now, but we’d love to hear whether those who experienced issues with beta-2 notice improvements. We’ll keep you all posted once it’s ready.

Hey all, sorry for the delay and issues following up on this, it sounds like enough people are having this issue but we're having a hard time reproducing this on our end. Based on the version cutoff you’re describing, this may be related to controller input handling changes that started around 13.24, especially DirectInput controller polling. It may also be affected by video/audio playback in some setups, so we’d like to try and gather a bit more detail. We'd love it if you can try the following (I know some of you already have, but for those who haven't) In LaunchBox, go to Tools > Options > Game Controllers. Uncheck Enable Game Controllers. Restart LaunchBox completely. Test whether mouse movement, mouse clicks, and keyboard typing return to normal. Please also test Big Box separately: Open Big Box. Go to Options > Controller. Disable controller support there as well. Restart Big Box. Test whether the delay still happens. When replying, please include: Which LaunchBox version works normally for you, and which version first shows the issue. Whether disabling Enable Game Controllers fixes it after a full restart. Whether you use any controller-related software, such as Steam Input, DS4Windows, reWASD, vJoy, ViGEm, JoyToKey, Xpadder, or similar. What controllers or input devices are connected, including wheels, pedals, flight sticks, fight sticks, Bluetooth controllers, or virtual controllers. Whether the issue happens with all controllers unplugged. Whether the issue happens in LaunchBox, Big Box, or both. Whether you have auto-play videos or auto-play music enabled. Which video playback engine you’re using, if you know. If disabling game controllers fully resolves it, that is very useful information and points us toward the controller polling/input path. If it still happens with controller support disabled and all controllers unplugged, please mention that clearly, because that would push us more toward the video/audio playback side instead. Please let us know and we'll try and narrow this down.

Hi Folks, thanks for all the reports, we're digging in to the issues reported with beta-2 and apologies for the issues here. In addition to @faeran 's request for those experiencing performance issues, one of the biggest things that will help when it comes to reported sluggish performance would be a screen recording of the issue should the impacted performance (even better if you have downgraded, to show how it compares to the previous beta or 13.27). If you aren't comfortable sharing screen recordings here, feel free to ping a DM to me (@AstroBob) & @faeran. Thanks all for helping to test these, we're working to get out beta-3 which addresses some of these immediate issues.

Correct, you can use the Image Height (Section Override) to adjust the spacing for not just specific platforms, but individual categories & playlists too.

Not yet, but this is a, interesting idea. It would have to stay performant and would probably need to be a uniform image type to remain consistent (possibly a good use for the icon image type), but I scoped it out here if you want to upvote it: - https://feedback.launchbox.gg/p/optional-image-column-in-list-view

Version 1.22 - Released May 28th 2026 Release Summary Release Summary: https://feedback.launchbox.gg/changelog/launchbox-for-android-122 Full Changelog: https://www.launchbox-app.com/android-about/change-log Release Video: 👇 New Features: Steam game importing for the new Windows platform. This lets you bring your Steam library into LaunchBox for Android and launch supported games through compatible Android Windows launchers Steam media support. Steam games can now use Steam artwork and trailers, including box fronts, clear logos, backgrounds, and videos, giving imported Steam games better media coverage out of the box Steam library update support. LaunchBox can now compare your Windows/Steam platform against your Steam library to add newly owned games and optionally remove games you no longer own, including a Refresh Games option in Manage Steam Options to customize Steam imports. You can choose exactly which Steam games to import, whether to include family shared games, search the LaunchBox Games Database, prioritize Steam metadata, prioritize Steam media, or allow duplicate imports A new Security system that lets you lock down platform and game management features behind a PIN, with extensive configuration options available under Options > Security Platforms: Windows, Arduboy, Sega Model 3, Uzebox, WASM-4, and Microsoft Xbox Emulators: GameHub Lite, GameNative, Pizza Boy SC Pro, Azahar (Vanilla), Linkboy, Lynx.Emu, PICO-8: Android, PICO-8: Picpic, Aethersx2 (Turnip), SkyEmu, MelonDualDS, YabaSanshiro Pro, Vita3k (ikhoeyZX), Super3, X1 Box, aPS3e, and eka2l1 RetroArch core mappings for Arduboy, Uzebox, and WASM-4. These platforms should now be easier to import and launch when using RetroArch A visual update indicator for themes, showing a green badge on the Manage Themes menu item and next to individual themes when updates are available Improvements: Steam account management with Steam Guard approval handling, cancel support while waiting for approval, a safer logout confirmation, and more reliable saved sessions Steam media and trailer loading during imports, making Steam artwork and videos more reliable when importing larger libraries Streaming video support. LaunchBox now handles more streaming video formats, including HLS streams, which helps Steam trailers and other online videos play more reliably Updated Optimize Library behavior so star ratings across your entire library now refresh automatically when running an Update Library scan Fixed: Fixed Local and Cloud filters so games appear in the correct place. Games with local files now show under Local, while Cloud only shows games that exist only on a configured network/cloud location Fixed a possible crash when returning to LaunchBox. This could happen if notification or data services were not available yet when the app resumed Fixed Security settings so PIN changes are saved immediately, clearing a PIN disables Security, and protected menu actions use the correct PIN requirements Fixed an issue that prevented setting a Scoped Storage path when the app was running as a homescreen launcher Fixed possible image resize conflicts during media downloads. This could prevent media from failing or becoming inconsistent when multiple images were being processed at the same time Fixed the Add to Playlist popup so playlist items are scrollable and accessible Fixed Browse Steam Image capitalization and allowed the Steam image browser to go back from loading and error states Fixed numeric password input handling in the Steam credential login popup Fixed scoped-storage handling for additional applications. Launching alternate versions or additional apps should now use the correct file path or URI Fixed scoped-storage lookup to use the selected application path. This helps when launching an additional app or alternate version instead of the main game file Fixed the built-in Vita3k Android emulator launch command

Heya, thanks for the suggestion. Just to confirm, I'm assuming this is referring specifically to the Auto Save Backup features, since that is the only thing that will take up space on disk if you have this enabled. Let me know and we'll get this written up on our feature board. Cheers,

Thanks folks, confirmed this indeed an issue that we'll get fixed up. Can follow along with this post here to get notified of any updates to it: - https://feedback.launchbox.gg/p/game-details-pop-out-window-opening-behind-launchbox Cheers,

Hey @SolarisSpell sorry for the issue here, you're not alone in that we have seen instances where the local stats and cloud stats can get out of whack, which unfortunately means why you try to hook them up again, the cloud stats constantly take president, which is sounds like what is happening here. We don't have a great user-facing workaround for this at the moment, though do have a request to allow users to clear their own cloud stats, and esentially start with a fresh sync from their local data. - https://feedback.launchbox.gg/p/reset-clear-cloud-game-statistics In the meantime though, if you want to DM me with your games DB account email, we can try clearing the cloud stats on your account from our end, which should allow you to do a fresh sync. Drop me a DM if you want to give that a try