AstroBob

Hi there, Thanks for the great question. I own a Retroid Pocket 5 and am very happy with it. The screen is beautiful and, at least for me, I don't mind the D-Pad being on top since I play mostly retro games. Regarding LaunchBox for Android, the RP5 works great with it, since you can use the built-in controls for navigation (i.e, the D-Pad, confirm / back buttons, and the dedicated ANdroid back/home buttons make it a breeze to move around the app and launch games). I rarely even need to, but you also have the touch screen if you want to use that for navigation instead. All in all, I'm very happy with it, happy to answer any specific questions you might have with it and LaunchBox.

Please also add your support and follow our feature request for this, to be notified of any updates. 🔗 Support for Linux operating systems

Yes, there have been some updates to the game pages on the database. Expect more details on these to arrive soon, but you should be seeing images load a lot faster, along with some other quality of life improvements. Sorry for the issues there, and let us know if you notice these errors again in the future.

Hi Folks, Just wanted to let you know, today we released a patch version (13.20) which contains a fix for this issue. The DOS importer should now be working properly as expected. You can see the full changelog here. Thanks for bearing with us there. Cheers,

Hi there, Thanks for the report here, there was some maintenance on the database yesterday, which could have contributed to this. Can you confirm If you're continuously seeing these moderation errors today? Cheers,

If you go to Tools > Edit > Platforms, select WiiU and then click on the 3D Model Settings tab, do you have any ovveride set there? Also, does this affect any WiiU games, or just that specific one?

I wouldn't be surprised if it's not treating those shortcuts as game files, hence why it isn't picking anything up to be removed. I've added that to the scoped feature though, since you're right, it shouldn't just be able to scan for added shortcuts but remove them by running the scan for deleted ROMs as well

For sure, it's certainly possible. There are many ways we could go about this, another being using the fbneo core, since a lot of those sets also don't require any dependencies. We're continuing to iterate on the NAS functionality so I wouldn't be surprised if we come back to this in the future, but can't say which approach we would go with.

Hi there, Thanks for the report here. We've actually been hunting down an issue for a while now that sounds similar to this. I tried to run the same repro steps as you but unfortunately, I couldn't reproduce the behaviour. If you can reliably reproduce the issue, would you mind recording a quick screen recording outline so I can ensure I'm following your steps 100%. That, and please let me know what LaunchBox version you're using. Cheers,

Thanks, one thing you could try here is temporarily moving the directory it's referring to outside of LaunchBox to see If it resolves the error. It's possible something in that tmp directory has become corrupted so take a backup of it, remove it and see if that resolves the error.

Hi Folks, Happy to report we finally have an implementation for .RVZ scanning! 🙌 This is available in our latest beta for 13.20 GameCube games in the .RVZ will now be able to scan correctly for achievements, and achievement badges will now show for any matched games. If you're keen to give this a try you can join the latest beta, otherwise you can expect this in 13.20. Cheers,

Hi Folks, Just to let you know this, issue has now been addressed internally and will be available in the next version of LaunchBox (13.20). An early beta is available of this version which contains this fix, which you are welcome to try out below: 🔗 https://forums.launchbox-app.com/topic/89482-launchbox-1320-beta-thread/ Otherwise, you can expect to receive this fix in 13.20. Thanks for bearing with us there, and apologies for any issues due to this.

Hi Folks, Just to let you know this, issue has now been addressed internally and will be available in the next version of LaunchBox (13.20). An early beta is available of this version which contains this fix, which you are welcome to try out below: 🔗 https://forums.launchbox-app.com/topic/89482-launchbox-1320-beta-thread/ Otherwise, you can expect to receive this fix in 13.20. Thanks for bearing with us there, and apologies for any issues due to this.

Hi Folks, Just to let you know this, issue has now been addressed internally and will be available in the next version of LaunchBox (13.20). An early beta is available of this version which contains this fix, which you are welcome to try out below: 🔗 https://forums.launchbox-app.com/topic/89482-launchbox-1320-beta-thread/ Otherwise, you can expect to receive this fix in 13.20. Thanks for bearing with us there, and apologies for any issues due to this.

HI there, Thanks for the report here. I'm looking into a potential issue where .chd files don't appear to be getting recognised by the importer. Could you please walk me through your exactly import steps (including what files you have in the directory you're trying to import). If it's easier, you can also share a screen recording, but I'm most curious to see what is the structure of the directory your trying to import, and which import steps your following to get them into LaunchBox. Please let me know and we'll try to get you sorted. Cheers,

Hi there, I've split this out into its own topic since that thread was specifically with Big Box, and if you're not using Big Box it would be good to keep this separate. To investigate further, could you please confirm the following? Steps to reproduce: Please describe the full steps you took to encounter this error. Consistency: Are you able to reproduce this error reliably, or does it occur sporadically? Error details: Are any errors shown, and if so please attach to this thread When did the issue start? Let us know when you first noticed this issue occurring. Screen recording: If possible, providing a screen recording of the issue in action would greatly help our team narrow down the cause. Let us know, and we’ll work on getting this resolved for you.

Hi there, Thanks for the report here. It's hard to tell without the full error log, but for any issues with 13.19, please first check out this post to ensure there aren't any issues with incompatible plugins: If it's not that, there are references to mapped drives there. May I confirm, do you have any data (games, media etc), that is stored on a drive different to your LaunchBox install, and that wasn't connected at the time of this report? There are some known issues where LaunchBox will complain in certain places if a mapped drive is not connected, however this shouldn't have any impact during startup. I'd also be keen to understand if this was a one-off issue, or if it continues to be slow to startup. Finally, just to confirm I assume you're referring to 13.19 and 13.18, but can you confirm exactly which version you are using? Cheers,

Hi there, Thanks for reaching out and reporting this error. To investigate further, could you please confirm the following? Consistency: Are you able to reproduce this error reliably, or does it occur sporadically? Error details: Is any error displayed when LaunchBox closes? If so, please ensure that the full content of the error message is visible in your response or pasted into this thread Screen recording: If possible, providing a screen recording of the issue in action would greatly help our team narrow down the cause. Let us know, and we’ll work on getting this resolved for you.

Thanks for the additional context! You both make some great points, and the fact is that the Scan for Added ROMs functionality wasn’t originally intended for Windows shortcuts, so there’s definitely room for improvement in this area. I’ve gone ahead and scoped out a proper feature request based on your feedback. You can view and upvote it here: 🔗 https://feedback.launchbox.gg/p/support-for-windows-shortcuts-in-scan-for-added-roms Thanks for bringing this to our attention! While I wasn’t able to confirm that this behavior has changed in recent versions (as far as I know, it’s always been this way), I believe these reports may have been mixed up with the drag-and-drop issue in LaunchBox, which was an actual bug that has since been fixed. However, if you’re certain it behaved differently in a previous version, please let me know which version that was, and I’ll do my best to track it down.

Hi there, Thanks for the report! Would you be able to paste the full output of the error here? Unfortunately, it’s cut off in the screenshot, so we can’t see the entire message. From what we can see, it looks like the issue is related to a specific file being unreadable. Could you confirm which file is mentioned in the first line of the error? Also, since the file is on the E: drive, is that a removable drive? If so, please check that it’s properly connected and that other files on the drive are accessible. If you can share the full error log, we’ll do our best to advise further.

Hi Folks, We're still investigating to understand the cause here, as we're not able to fully reproduce this yet. That said, please see the update and description of the known issue report here 🔗https://feedback.launchbox.gg/p/known-issue-big-box-freezes-after-being-left-idle-on Right now, while I realise some people have reported this hasn't helped, others have said that switching the video playback engine from VLC to Windows Media player has helped with this. For those who haven't, it would be worth making that change to see if it has any effect. I'd also suggest following that known issue so that you can see any updates we post. Will update this thread as soon as we know more. Apologies for the issues here. Cheers,

HI Folks, We're still investigating to understand the cause here, as we're not able to fully reproduce this yet. That said, please see the update and description of the known issue report here 🔗https://feedback.launchbox.gg/p/known-issue-big-box-freezes-after-being-left-idle-on Right now, while I realise some people have reported this hasn't helped, others have said that switching the video playback engine from VLC to Windows Media player has helped with this. For those who haven't, it would be worth making that change to see if it has any effect. I'd also suggest following that known issue so that you can see any updates we post. Will update this thread as soon as we know more. Apologies for the issues here. Cheers,

Livestream starting soon! Wednesday, February 19, 2025 - 5:00PM EST Looking to supercharge your LaunchBox and Big Box experience? Join AstroBob for a performance-focused livestream where we’ll be fine-tuning, optimizing, and making sure your build and games are running buttery smooth! 🧈 Here’s what’s on the agenda: ✅ Exploring the latest improvements in LaunchBox 13.19 – What’s new and how it enhances performance ✅ Optimizing your LaunchBox & Big Box setup – Best practices for smooth navigation & snappy UI ✅ Dialing in emulation performance – Ensuring your games run as flawlessly as they should Whether you’re a LaunchBox pro or just starting out, this stream is packed with tips, tricks, and fixes to help you get the best possible experience. As a certain blue hedgehog might say… gotta go fast! 🦔💨

Thanks for the update! The bug fix in 13.19 specifically addressed users who were dragging and dropping shortcuts into the LaunchBox interface and following the wizard that specified applications, that were being incorrectly set as ROMs. However, based on how you’re currently handling this, it turns out this behaviour is actually expected. The Scan for Added ROMs function, as the name suggests, is designed specifically for ROM files, which is why anything detected during this process ends up with the Use Emulator checkbox enabled. That said, I totally get why this feels counterintuitive—especially for platforms like Windows, where applications aren’t traditional ROMs. At its core, the function simply doesn’t have a way to distinguish between a ROM and an application, which is why it’s treating them the same way. I’m curious about your workflow—what’s the reason for relying on shortcuts rather than using the storefront importers? I can understand if it’s for non-storefront games that might be installed in different locations, but you also mentioned Steam games are included. Just wondering if there’s a specific use case we’re not currently accommodating that we could improve. You also mentioned that this “used to work.” I checked back to 13.17 (since the initial report was for 13.18), but even in that version, it looks like shortcuts weren’t being recognized correctly at all. I definitely think there’s room for improvement when it comes to Windows imports and a better way to handle non-storefront games. If you can share a bit more about your specific setup, I’d love to scope out a possible feature improvement and get it logged for you. Looking forward to hearing your thoughts!

Hi there, Thanks for the update, we've seen quite a few people who have this plugin installed have the same issue and also have one of the extreme home arcade builds. Unfortunately, we don't really know what it does, since it doesn't appear to be hosted on our forums, and if you've purchased a build from another source it's likely something that came from that seller. Chances are, if you're unaware of what it does and if removing it doesn't have any impact on your usual LaunchBox workflows that it can be safely removed. Hopefully, other users who use this plugin may be able to chime in on its usage here, but glad to hear you found the culprit. Cheers,