x4ml

LaunchBox for Android 1.23 Beta thread has opened:

Hi Everyone, A new beta round has begun for Android for version 1.23. The first beta is out and introduces a major RetroAchievements update, improvements to the Boxes Grid games view, better streaming video handling, and additional diagnostics to help us track down startup, launch, and playlist issues. While the changelog is fairly straightforward, we would really appreciate focused testing, especially around the new RetroAchievements features. ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Testers: Things to Focus On Please help us validate the following: RetroAchievements: Log in from the new RetroAchievements main menu section, confirm your profile, stats, recent activity, recently played games, and leaderboard links load correctly. Test supported games to confirm achievement summaries appear on game details pages. Game Achievements Page: Open achievement sets for supported games and test Grid and List views, controller navigation, portrait and landscape layouts, sorting, searching, grouping, and filters such as earned, locked, missable, progression, and win condition achievements. Emulator Credentials: Test configuring RetroAchievements credentials for supported emulators, especially RetroArch, and confirm settings save and work after restarting the app. Achievement Notifications: Launch supported games through supported emulators, earn achievements if possible, then return to LaunchBox and confirm newly earned achievements are detected and shown correctly. Boxes Grid View: Test the Boxes Grid games view with large libraries. Please check scrolling speed, responsiveness, image fit options, spacing options, controller navigation, and touch navigation. Startup, Launch, and Playlist Diagnostics: If you run into slow startup, slow game launches, playlist save issues, missing playlist games, or playlist deletion problems, please report them. This beta includes additional diagnostics to help us track these down. ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Beta 1 Changelog Added a new RetroAchievements section to the main menu. You can now log in, view your RetroAchievements profile, see key stats, recently played games, recent activity, and open the global leaderboard from LaunchBox for Android Added a dynamic RetroAchievements main menu label. The menu can show your selected RetroAchievements stat, such as score, achievements unlocked, games beaten, completed games, or mastered games Added a redesigned game achievements page for RetroAchievements. Game achievement sets now support Grid and List view modes, controller navigation, detailed achievement information, earned and locked badge states, unlock rates, achievement type badges, and responsive portrait and landscape layouts Added filtering, grouping, sorting, and searching to RetroAchievements game achievement sets. You can filter by progression, missable, win condition, earned, locked, and other achievements Added RetroAchievements progress summaries to game details. Supported games can show earned achievements, completion percentage, earned points, and RetroAchievements-provided beat and master time estimates Added an option to show or hide RetroAchievements information on game details pages Added optional LaunchBox achievement notifications. When returning from a supported emulator, LaunchBox can check for newly earned RetroAchievements and open the related achievement page Added support for configuring RetroAchievements credentials for supported emulators, including RetroArch Improved the Boxes Grid games view with faster scrolling, better responsiveness, and new image fit and spacing options Improved streaming video handling and media playback stability Improved startup and launch diagnostics with startup/load tracing, deferred Android startup work, and slow game launch reporting to help identify loading and launch issues in beta builds Improved playlist diagnostics and error reporting to help track down cases where playlist names, games, or deletions do not save correctly Fixed an issue where newly added playlist games could be missing when opening the playlist immediately afterward Fixed an issue with downloading media and logging in to EmuMovies Fixed a possible crash when the LaunchBox Themes folder was missing or inaccessible Fixed a possible crash on older Android versions caused by unsupported media foreground-service behavior Fixed an issue where preview videos could continue playing while launching a game Fixed several controller and touch navigation scroll issues across list and grid views Thank you for helping us refine LaunchBox for Android. Your testing and feedback continue to make the app better with every beta.

It's a known issue that started happening in the latest version. Will be fixed in the next beta that will be published soon 😉

Send it to my email (andriy@unbrokensoftware.com), and I'll check it when I have time

For both these issues, we will add extra logs in 1.23-beta-2 (or maybe 1.23-beta-1) for a better understanding of what's going on.

Thanks for the report. Could you please send us your LaunchBox/Logs folder and your LaunchBox/Data/Playlists folder, including the Backups folder if it exists? Also let me know your device model, Android version, LaunchBox version, where your LaunchBox data folder is stored, and whether the playlist comes back only after restarting LaunchBox. That should give us enough to see whether the playlist changes are failing to save or if old playlist files are being loaded again.

you can enable Debug Logs on the Options page (see screenshot) Then, when you reproduce the issue, you need to go to the LaunchBox folder -> Logs -> sort by newest and send the latest 2-3 log files.

What version are you running on? What device do you use? It will also be useful if you enable logs on the Settings page -> reproduce the issue again -> send the log file here. I could investigate it and fix it in the following beta. There is no limit to the number of roms if you have a license

You can find cores and download them for your game, place them somewhere in the LB folder, and select them for a platform/game on the platform/game Emulator Settings

Hello. You might have selected the wrong core. Try using other cores

The Nintendo Switch Pro Controller should work, but LaunchBox itself does not handle controller input once a game is launched. LaunchBox hands the game off to RetroArch, so in-game button recognition is controlled by RetroArch and Android. First, please confirm which RetroArch app LaunchBox is using for your Sega Genesis platform: RetroArch, RetroArch Plus, or a sideloaded RetroArch build. Each one has its own separate controller/config settings. Try opening that exact RetroArch app directly, launch the same Genesis game manually, then go to: Settings > Input > Port 1 Controls > Device Index Make sure the Nintendo Pro Controller is selected for Port 1. Then check: Settings > Input > RetroPad Binds > Port 1 Controls and bind the buttons there. After that, save the RetroArch config and launch the game again from LaunchBox. If the controller does not work in RetroArch directly either, then the issue is with Android/RetroArch seeing the controller, not LaunchBox. If it works directly in RetroArch but not when launched from LaunchBox, let us know which RetroArch version/package LaunchBox is set to use and which Genesis core you selected.

Hello, we know about the issue, and it'll be fixed in the next beta.

Sorry about that, and glad you got it working! Just as a heads-up, replies on the forum can sometimes take a bit longer than on Discord. So if you have an urgent issue or need a quicker response, Discord is usually the better place to ask. Thanks for your patience!

GameHub itself currently does not support external launch arguments, so LaunchBox can’t reliably launch games through it the same way it can with emulators that expose launch parameters. That’s why you’re seeing GameHub Lite / GameNative support instead of full GameHub support. You don’t necessarily have to switch if your setup works for you inside GameHub, but LaunchBox needs a launchable target it can pass a game/app into. Full GameHub doesn’t currently provide that. For 1.22, Steam import is focused on your Steam library/games. It is not scanning GameHub’s internal playable list or detecting separate non-Steam/special PC versions you added into GameHub. So if you have EA/PC versions that only exist inside GameHub and aren’t launchable externally, LaunchBox won’t be able to pick those up and launch them through GameHub automatically.

We know about this issue. Will be fixed in the next beta

No, it's a known bug We are working on it, so we will try to fix it by the next beta

Hi, that's what AI suggested: The physical mouse setup is handled inside RetroArch’s PUAE core. For Dungeon Master, try this: Connect the USB/Bluetooth mouse before launching the game. Launch the game with the PUAE core. Open RetroArch’s Quick Menu. Go to Core Options / Options > Input. Set Physical Mouse to Enabled. Leave Double disabled unless you are on a Linux/raw/udev setup; RetroArch’s PUAE docs say Double requires raw/udev input and proper mouse index setup. Set Mouse Speed to 100 to start. Close and relaunch the game after changing the option. Also, don’t worry if you don’t see “Mouse” as a normal Port 1 / Port 2 controller type. PUAE documents mouse support separately as an “Other controller” that is enabled by default.

Thanks for letting us know. We will investigate it and update you with some details

Welcome to the forums! At the moment, the Android app does not support 3D box images like the desktop version does. It currently uses the standard 2D box/front images. That said, 3D box support is something we could potentially add in the future, since the media does exist in the GamesDB. I’ll pass this along as a feature request.

Glad you got it working, and thanks for posting the fix. That setting tells LaunchBox to send the selected RetroArch core when launching games. Looks like the Shield needs that enabled for RetroArch to launch correctly. We’ll keep this in mind in case we need to make that option clearer or adjust the default.

As a workaround, try to select Custom Emulator (With Code) with these custom arguments "-n io.github.lime3ds.android/org.citra.citra_emu.activities.EmulationActivity -a android.intent.action.VIEW -d {file.uri} --activity-clear-task --activity-clear-top"

Hi, not yet

You must select the Vita3K folder from the left side (it looks like the RetroArch folder on my emulator in the screenshot):

Hi, thanks for letting us know. We will check it and let you know. If it's a real issue, we will try to fix it by the next beta.

Yes, it was added, but not included in the list of available platforms, as there wasn't an emulator that supported it. We will check the emulator you have sent and see if the platform will be added to the list. Thanks for letting us know. P. s. if we add it, it will be available in the following beta release