faeran

I'm not seeing this with a basic No-Intro or TOSEC sets. Which import method did you use? Also can you double check the name of those 3 files in your screenshot. let me know the exact file name, including the extension. I'm also not seeing this happen after testing. Can you give me some exact file names that you are seeing this with. Also can you tell me which import method(s) you are using that you see duplicated games on the final page even when Force import duplicate games is unchecked?

Hi everyone, LaunchBox for Android 1.21 beta has started, and we have a number of new features and improvements (with more to come) that we could use help testing. Game Progress Tracking has finally made its way over to Android, complete with manual controls, automation rules, and full customization. We have also added a new NAS Management section for users with networked game libraries, and we are continuing to improve performance and fix bugs across the board. If you are able to test this build, here’s what we would love your feedback on: Game Progress Tracking – Manual Updates From any game's menu, tap Progress to change its progress state. Try selecting one of the default values, then try again after customizing your progress states. You can customize them by going to Options > Game Progress Organization. Try creating a new category or value, assigning it to a game, and restarting the app to confirm it sticks. Game Progress Automation – Rule Behavior Go to Options > Game Progress Automation and test the automation system. There are two default rules: Games played for over 30 minutes move to Active / In Progress Games not played for 30 days move to Active / Paused Try customizing the time values and the target progress states. You can also disable automation entirely and confirm that game progress is no longer updated automatically. NAS Management – IP Repair and Guest Access If you have imported games from a network share (SMB), a new NAS Management page will be nice to test under Options. You can test features like: Scanning for updated IP addresses Manually updating an IP address Adjusting saved credentials or switching to a Guest account Let us know if all your networked games launch correctly after making changes. Loading Page Performance Startup times should now be noticeably faster for large game libraries. For example, a library of 5000 to 8000 games should see about a 60% improvement in startup speed compared to previous versions. Sorting and Filter Behavior Sorting issues should now be resolved. Try different sorting options and filters across multiple views and confirm that games are being sorted correctly in all cases. Beta 1 Changelog Game Progress Tracking has arrived on Android, giving you full control to manually update your game's progress status right from the game menu Added a new Game Progress Automation page that can automatically update a game's progress based on custom rules you define Added a new Game Progress Organization page with drag and drop support to reorder or customize your progress states using defaults or your own values Added a new NAS Management page under Options where you can view your mapped drives, check their connection status, and repair broken links by scanning or updating the IP address Improved performance on the loading page to reduce wait times for large game libraries Fixed an issue where the Banner Filter view could jump or shift when the list was shorter than the device width on newer versions of Android Fixed an issue where sorting games did not always arrange them in the correct order Known Issues Beta 1 You can delete Categories and Values from the Game Progress Organization section right now when you shouldn't. If a game is using one of those values, deletion should not be allowed. This will be fixed in Beta 2 Game Progress Automation for moving games to Active / Paused after a number of days only works under specific conditions. A startup check to apply this more broadly is planned for Beta 2 Thanks all. Every beta tester helps shape the future of LaunchBox for Android. Your testing and feedback make all the difference.

Here's a document that talks about how to add a custom emulator, however, if there is an emulator that we should be added to our long list of emulators, let us know and we'll add it if we can for the next release. https://feedback.launchbox.gg/en/help/articles/7096169

While not specific to the beta, Joe was right in that what you are seeing is you applied the Colorful theme, and that theme does not have a custom view for the Game Discovery Center, and when a custom theme doesn't have a specific view, it falls back to the Default. I'm guessing you'll want to use the system menu to switch to either the Platform or Platform Categories section, as they are the most popular, and Colorful does have a custom theme for those views.

Both are good options. We'll see what we can do for beta 2.

Type in a name first and you should be good.

The good news is that the feedback link url can be changed any time outside of any code changes to LaunchBox, so the test would mostly be that you click the button and it opens a webpage of some kind. Thanks for the feedback.

A new beta round has commenced. LaunchBox 13.25 Beta Thread is now open:

The app itself, since it's inception has been reliant on folders that it needs to be there (for many in-app reasons) to actually be there. Before 13.24 it wouldn't let you edit platforms for that reason. However, we did attempt to loosen that a bit with 13.24 so that when you open the Edit Platform window and that platform is missing a folder path, it still lets you edit things up.

Hey everyone, We are kicking off another beta round with version 13.25 Beta 1. Thank you to everyone who continues to jump in, test, and share feedback with us each release. Your help makes a huge difference as we polish and prepare for the next full update. Testers - Things to focus on: Platform Documents: Try adding, reordering, and opening platform documents from the Edit Platform window, the details pane, and the sidebar context menu. Check that the order stays consistent everywhere and that the correct document opens. Beta Spotlight Window: Make sure the new Beta Spotlight window appears only once per beta round and replaces the Welcome screen during beta testing. It can also be opened anytime from Menu > Help > Beta Spotlight. Test that the feedback button works as expected. Metadata Search Improvements: In the Add and Edit Game windows, type part of a word to test the new partial search feature. It should still prioritize exact matches and limit results to the correct platform. 3D Model Rotation Lock: Right click any 3D Model and test the Free Rotation, Lock Horizontal, and Lock Vertical options. Verify that each works correctly and that your choice is remembered after restarting LaunchBox and Big Box. Screensaver Flash Fix: In Big Box enable screensavers and test all your different view types and confirm that game transitions happen smoothly without flashing between games. Full Changelog: New Premium Feature: Platform Documents let users attach and organize manual or document entries for each platform. Documents appear in the platform details panel and sidebar context menu and follow the order you set New Feature: A new Beta Spotlight window appears during beta rounds to highlight new testing areas and features. It replaces the Welcome screen for beta users, shows once per beta round, and can be accessed anytime under Menu > Help > Beta Spotlight. Includes a quick action button for feedback Improvement: Add and Edit Game metadata searches now support partial word matching. Typing part of a title will show results containing that text while still prioritizing exact matches and filtering by platform Improvement: The 3D Model viewer adds a new rotation lock menu with Free Rotation, Lock Horizontal, and Lock Vertical options. Settings are saved across both LaunchBox and Big Box Fixed: Screensavers no longer flash a game in-between the previous and next game during transitions. Game changes are now seamless, with smooth audio and consistent performance Thank you again to everyone helping with testing and reporting back. While the features above are the main focus, some changes can have unexpected effects elsewhere in the app, so please let us know if you notice anything unusual, however please be open to the possibility that a change you believe happened due to a LaunchBox coding change may end up being user error, or external environmental issues. Your input helps us catch issues early and make each release even better.

Thanks for the request. The issue really lies in how we know a file is RetroAchievement compatible. RetroAchievements releases an official hashing program which is used to scan game files to grab the correct hash, which is then compared to an online database of hashes to find a match. The issue is that the program is not compatible on Android. There are ways around this but each have their issues. That would be one of the main pieces holding a feature like this back. Also note that LaunchBox for Android doesn't have a concept of badges like the Windows versions does, so we'd be more looking at filters and theme specific bindings.

Best to open up a separate troubleshooting thread for this type of stuff, but my best guess is that if you did not check off the import duplicate games option, then during the metadata matching process it would have deemed Project Zero the same game as Fatal Frame and then stopped importing it. You are listing a different kind of work flow that probably also requires you to check off the import duplicate games option, but you should open up your own troubleshooting section where you can provide a detail breakdown of your steps that you are taking so that the community can properly help you.

Thanks for taking the time to share all this. You clearly have some experience in this field so we can skip past the 'bugs and regressions are frustrating' bit and jump straight to - we agree. Our QA process has evolved over the last 4 to 5 years and, if anything, is stronger and more capable than it used to be. LaunchBox is a very open ended app and even just looking at a single feature, like game import, we have around 7 different import methods, each with many options, you are easily looking at 150+ different combinations, not to mention the fun that is OS and devices and the gazillion different ways people have their collections set up we really do try our best to hit the likely problem areas. We, admittedly, have been caught by a few larger issues that have really pushed us hard this year. The conflicts of video playback and platform changes (OS, .NET, and hardware). Since you're asking, we can easily share our QA process We test everything manually, in many different configurations (including new builds and existing builds) on many different pieces of hardware, including many computers, controllers, monitor setups, other popular toys (my messy desk speaks for itself), and many third party programs, tools, plugins, and themes that many users love to use in their setup (this always takes longer than the dev cycle by quite a far margin) We do structured/informed regression testing We do not have the pleasure of much automated testing for a variety of good (and some less good) reasons, so manual testing is where we get most value Every feature is released through the beta channel excepting those things we put into immediate hotfix from a recent public release Manual testing + a beta will never give us 100% confidence, nor can it. But it's the same but improved process every cycle we go through, with all the learnings we build. Bugs will definitely slip through and we'll definitely try to learn from those that do. The community, as it always has been, is invaluable to our process and we couldn't do this without you and we appreciate beyond measure this piece of it. Your thoughtful post definitely is a part of this. P.S. help us beta test if you don't already. A new beta will come out within the coming week(s) which you will find the thread here: https://forums.launchbox-app.com/forum/83-beta-testing/

Thanks for the thorough reports here. It does look like there was a change that was unintended that essentially forces the MAME parsing logic when using Arcade as the scrape as value. We'll have to fixed up before the hotfix. A workaround for people that don't want to wait would be to not select Arcade as the scrape as value during an import, then set it after the fact, and run a download metadata and media import.