x4ml

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

Can you also make sure that the path to the LaunchBox files is not changed? Maybe you have recently installed an SD card..

Can you make sure that you have the "Show Android Apps" option disabled? Also, what do you use as a Default Root Filter? And how about the "Start with Platform Categories" option? Is it enabled or disabled? All these options you can find on the Options page

Hello! If you still need your help, would you describe the issue in more detail?

Thanks. We will fix it in the next beta version!

Hello, we will try to investigate this issue and fix it by the next beta version. Thanks for letting us know

Hi You can enable the "Recently Played" filter on the Options page

I didn't find any information that the RPCSX3 emulator can be launched from storefronts. If you want, I could search for launch arguments for the aPS3e emulator.

Thanks for letting us know. We will add it to the list of things to check (and probably fix).

Hi! Actually, yes. Playlists show all games added to them. But when you enter a playlist, you can filter it by platforms.

Hi! What do you mean by "created the PS3 platform"? If you want to import PS3 games, select the platform folder on the Import Games page (from the Hamburger (left) menu) and go through the whole importing process. The only way to launch PS3 games is to use Custom Emulator (With Code) using Launch Arguments. We haven't added "ready emulators" for that Platform (I hope we will do it in the next versions) yet.