Jason Carr

@JsARCLIGHT Sorry for the way late response here. I'm not sure if you're still having this issue, but if I recall correctly, it usually happens because of display driver corruption or interference from a poorly written app. Make sure that you don't have Nahimic installed (it's a terrible app that sometimes comes with sound drivers and messes up a bunch of different apps). Also try upgrading your video drivers.

Sorry for the late reply here. Are you still experiencing the same issues with the 12.4 release?

I believe those issues were resolved, but that's over 5 years old, so at this point it's most likely completely irrelevant. What particular issues are you running into?

3DS in LaunchBox for Android is available. The import process should be the same as pretty much any other platform. Here's a tutorial video:

@Shaolinmonk Thanks, all noted. This all depends on the version of RetroArch that you have installed (32-bit, 64-bit, sideloaded, etc.). We've done our best to include every possible option with every recent version of RetroArch. If there really are any cores in the most recent versions of RetroArch that are not listed in LaunchBox, please let me know what they are. We're not aware of any.

@Shaolinmonk @TXH Thanks for the report. We'll look into this.

@slydog43 It looks like all your game titles contain version numbers on them for some reason, which is probably the reason for the issue. What do your imported file names look like?

If you do want to downgrade, just email us at support@unbrokensoftware.com to request a particular version of the app to download. Usually downgrades work just fine, but if you're jumping large version differences you might want to make a backup first just in case of a major change that messes with data.

@pytsharp Without seeing the code and spending some time on it, this might be kind of difficult to figure out. It sounds like you're on the right track though. We resolved many similar issues back when we upgraded to .NET Core, and the fix was mostly just to change to a Nuget package that supports .NET Core. The only thing I can think of beyond that is that maybe you don't have the DLLs in the right places. Remember that you need the System.IO.Ports DLL from the Nuget package deployed with the LaunchBox plugin. You can try placing it next to the plugin file, and/or directly in the LaunchBox\Core folder. Sorry for the trouble here. The .NET Core updates did provide us with a bunch of improvements, and going forward the standard .NET Framework is being discontinued completely, so we never really had a choice whether to upgrade to .NET Core or not (but we definitely don't regret it either).

@klint01 I'm guessing that the issue probably has to do with all of the names of the games having "-1" appended to the end of them. What do the file names that you were importing look like?

@rommel76 LaunchBox for Android does not currently have any "Big Box" mode, though much of the LaunchBox for Android interface does resemble Big Box. Unfortunately, though, we don't have support for video previews in yet. That feature is coming soon.

Hmm, maybe it's having trouble connecting to the games database website. Try turning on debug logging in the settings; then maybe you can post me the most recent log file from the LaunchBox\Logs folder? Make sure you run a media download process or two first.

I am in the process of getting the Android version working natively with GTK on Linux. I think I can safely say that it's going to work at this point, but I do have a lot of work left, so it will still be a while. But it's coming.

For sure, we're definitely continuing to develop it. Do you have Sega Dreamcast games imported? Do they launch?

Good to know; I don't think that would happen often, but maybe we can add a warning for that.

@eonder87 The ones that do not have equivalents can just be copied over as they were. For example, some DOSBox settings (like the ones you're referring to in the screenshot above - plain numbers or titles that cannot be translated) are best to just keep the same as they were. If something can't be translated, then you can always just keep it in English or copy it over. Also, anything that is left blank will just use the English version, so it would also work to just leave blank anything that you're confused about, for now.

@eonder87 @Soomin papa I've added new Turkish and Korean translation packages. They are both available in the first post of this topic. Thank you both for all of your translation efforts; let me know if you run into any issues. Be sure to read the first few posts of this topic in full so that you don't run into any gotchas.

@Soomin papa My apologies for the delay here. I've just been swamped with development work. Thank you very much for offering to translate; I will get a translation package out to you for Korean and a Turkish package for @eonder87 here in the next couple of days. I have some work to do to put them together yet.

Make sure you're on version 12.3, as that should fix any issues like this. We haven't yet found any related issues on 12.3+. Let us know if you're already on 12.3. Regardless, to fix it, you should be able to just remove your RetroArch emulator from LaunchBox and then go to Tools > Manage > RetroArch > Install.

The Android platform should go away if you do the above (per @faeran) and then delete the platform. You can also skip the genre section by changing the secondary filter to none in Options.

Yeah, strange. Usually stuff like this is caused by an anti-virus or anti-malware program. Do you have anything like that installed?

Thanks much. Gonna go ahead with the official 12.3 release.

Yeah, you don't really want that, if possible. Honestly, I don't understand why it would be requiring administrator at all, other than if the file permissions got messed up somehow, or if your system is configured with some really weird group policy settings (such as if it's managed by a company or an organization). What all customizations have you done? Is it a fresh install of Windows and also a fresh install of LaunchBox/Big box?

No, not at all. That could mean that you have it installed to the wrong folder though. What folder did you install it to?

Okay, then most likely there's an issue either with the BIOS file, or with the ROMs. I would first try importing a different platform (an easy one like NES) to see if that works. If so, it's probably just an issue with the ROMs or BIOS file. Also, if you reinstall RetroArch (using the menu item), currently it will remove all BIOS files. So you may need to re-place that BIOS file into the RetroArch system folder.