x4ml

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"