Jason Carr

Yeah, that makes sense. I think we're playing forum tag lol. Check my response just above.

I see. The problem with this is that we have zero visibility in the importer as to whether the ROMs that you have contain those clones, so we only import the ROMs that we see. Of course if you check the box to import a full MAME set, it will import all of the clones. LaunchBox on the desktop works the same way. I suppose in the future we could add an option to specify what type of set that you have, but I'm not sure what further types of metadata we would need for that, etc.

There is a thread here on this topic, and it looks like at least one person is successfully running MAME 2003 Plus without any issues: So most likely, if you're running into issues, the problem is either with Retroarch or the ROM set.

@Vader We've been back and forth with the MAME metadata importer many times, and in theory, none of it has changed in years, so there really shouldn't be anything wrong with it (unless an Android-specific bug was introduced back when it was based on the desktop code). There are usually good reasons for the way things are structured, even when things appear to be anomalies. That said, the full MAME ROM set options are not relevant at all if you don't provide a full set. I'm having trouble following all of the above, so if you still want to troubleshoot specific issues with it, let's take it one thing at a time, and I can look into reasons or fixes for that specific issue.

So we decided to bite the bullet and make this the big 12.0 release. Therefore, this new beta is now called 12.0-beta-1. The big change for this beta is that we've introduced a new dark theme for all of the popup dialogs in LaunchBox, and premium users can now customize all popup dialog colors: Colors can all be customized under Tools > Options > Visuals > Dialog Theme. Lastly, FYI, there are still a few dialogs that have yet to be upgraded from the old Windows Forms approach to WPF, such as Add/Edit Additional Apps, etc. We're currently working on getting these converted over to WPF so that they can take advantage of the new themes.

Sorry for the delay here @intoshadows. From what I can tell, this is some kind of weird device-specific issue. I wish I had better news, but I don't really know why that specific device would be refusing those permissions. Unfortunately some of those Chinese devices have some fairly screwed up/non-standard configurations. I put this on the list, but I'm not sure if I'll have any luck fixing the issue without owning the device. In the mean time, if you purchased it and would like a refund, please just email us at support@unbrokensoftware.com and we can certainly get one for you.

@eonder87 If you're interested in translating, please let me know. Details on how it all works and translation packages are in this thread here:

Sorry for the delay here, guys. I've had my head down in the desktop app for a bit, but I'm headed back to Android development next week, back to working on the next major release. No betas have been released since the last official release (largely because I'm working on some larger features). I'll look into Dreamcast here soon to see if I can replicate any issues. I'll add that to my list of emulators to look into. That might be one of those problematic emulators though that doesn't properly work with frontends, if my shaky memory is correct. Regardless, I'll check to confirm. You can delete games, yes. There's no automatic duplicate scanning currently, though. How did you overcome them? Thanks, yup, all that is on the list here.

Oh lovely. Well if that's the case, then there is no solution currently. If either of our apps upgraded to the very broken storage access framework, it would ruin the possibility of communication between the frontend (us) and the emulator (Retroarch). Unfortunately the storage access framework is so poorly designed that it doesn't even provide an option (or at least not a documented one) for being able to properly share files between apps. So that of course ruins the possibility of a frontend. If anyone knows otherwise or has documentation that shows how it can be done, please let me know. Currently, I don't believe it can.

@intoshadows This is not an issue that we've seen elsewhere, as of yet. What device are you using?

Okay, good to know. I'll look into it.

Indeed, yes it does. You should be good to go.

Yes, that's probably why. If Android isn't telling us what it is from retrieving all of the storage devices, it'll probably be difficult to find it. I'll be on this soon.

Thank you @wooshaq, sounds great. Unfortunately I don't think I ever received any half-completed files from @wirtual82 (let me know if I'm wrong @wirtual82). You would need to get the files from him in order to resume his work. Otherwise, you'd basically be starting from the beginning (which is fine, but of course would be more work). If you read the first few posts at the beginning of this topic, it has full instructions as far as how to get started. Once you're done, you can upload the translation files here, and then I will compile them into a release.

Well, it sounds like this thread is unrelated to that, so it would be best to create another thread to troubleshoot. I've not heard of anything like that for the 11.17 release. It could be theme-related, however.

Yes, that helps, thanks. Might not be obvious what's going on, but it's definitely a step in the right direction. I'll look into it.

Okay, well that's interesting. If Retroarch can't see the ROM files, then most likely we won't be able to launch Retroarch regardless. But I'll still dive in and see what I can figure out.

@MDamian Hmm, well this one is likely to be difficult to solve without having that specific hardware for testing. It might help though to enable debug logging in the options, then maybe we'll see some errors in there if you can share a crashed debug log with us. The logs are in Logs subfolder of your LaunchBox folder, once you enable it.

I haven't tested with dongles so far, so perhaps that's the issue. The curious thing though is that we're using the built-in storage mechanisms, so they should show up, but Android doesn't always do things the way they should, sigh. I'll see if I can grab a dongle and/or a USB drive to test with.

You might need to grab the sideloaded version of Retroarch, but I think Retroarch Plus should have it. If mamearcade_libretro_android isn't there, it might be called mame_libretro_android.

What Retroarch core are you using @eggrally? I have Neo Geo games working fine using the mamearcade_libretro_android core, but they're in my Arcade platform with my modern MAME ROM set.

@santaclaw Looking into this, but I don't have a MAME 2003 Plus ROM set. I assume you're using a ROM set specific for MAME 2003 Plus? I'm getting a black screen with that core as well, but I have a modern MAME ROM set, so it's not likely to work anyways. Regardless, unfortunately, since the other arcade cores are working, most likely it's a bug with that core in Retroarch. Have you tested any other frontends to see if they work with that core?

Somehow we'll need to pin it down in order to figure it out. Obviously it's not affecting everyone, so it's probably either a specific hardware configuration or a setting in iCUE, or something like that. It doesn't come up often enough for it be a major issue, so I doubt everyone who is running iCUE is affected. With issues like these, generally, there's not much we can do, as the fault almost always lies with the OS and/or the faulty software that is causing the issues. Usually it's caused by interference with .NET apps in general, which means that it would affect a large number of apps. That said, just because it's happening on the one system doesn't mean it's necessarily being caused by iCUE. What anti-virus and/or anti-malware software are you running?

Thanks @RapsterUK. Added to the list.

@abattrick @neil9000 It sounds like the issue is related to the Corsair software conflict known issue (per information found in another thread). What specific Corsair product are you using?