C-Beats

As far as I remember the plugin eXo packages with his collection sets the installed flag which drives what you are seeing. @TimberlAndRE may be able to confirm. If that's the case he'd maybe be able to walk you through why the collection doesn't think the item in question is installed.

@SqHd I was able to confirm we did indeed have a "View Achievement Profile" input binding before that had not been restored. I have corrected it internally and it will be restored in the next release.

This is already done by Default themes but there are bindings that make it possible for theme devs NOT to use it. Big Box performance can swing pretty wildly based on which theme you're using to be honest. We've given the theme devs enough options that it IS possible that some of them aren't using the most performant options. This is made even more clear when older themes aren't using newer controls we've built for that purpose in mind. I'd swap to Default for a bit and see if you still have the same performance issues there or not. If not then it's probably because of the how the theme was created. We do our best to ensure all themes run as well as possible, but there are enough options provided to the theme devs to make the themes the way they want it's just not possible for us to cover every possibility.

I've never ran into an issue where x360ce doesn't work in a PC game. You could alternatively use Steam's controller logic which does something similar.

You can either use an LB plugin to read the controller information on the game, or you can do what we did to populate that data and read the mame.xml file that MAME generates with the information you are requesting.

We are certainly aware there is room for improvement in regard to performance. Just because we don't respond to every post doesn't mean we don't see them. We've spent quite a bit of time in the past implementing performance improvements (even devoting entire release cycles to it), and I'm sure we will be doing more in the future. We've identified some potential places to increase performance but as @zugswang eluded, some of these changes aren't small and require altering a very large section of the codebase. Altering such a large chunk of code opens us up to a lot of potential to introduce new bugs, and also stops progression anywhere else in the app so it's a bit of a balancing act between making these changes and improving the software in other ways. As of right now I'm the sole individual developing on the PC apps and so we can only do so much with such a limited resource so I'd ask for a bit of patience to any requested changes. If that's not possible and you need to find an alternate solution then we understand. It's obviously not something we WANT to happen, but if our product isn't delivering where you need it to then we respect that you need to do what's best for you.

I'll have to review the code changes. If it was there before we should definitely have it added back in. I'll review before final release and see about getting it squeezed in.

My apologies I had assumed most of you all were following this thread and got the notification that way.

Was able to confirm we have an issue with this. Goal is to get it corrected and then release another beta soon that resolves this and a few other issues we found internally.

Hey all, just letting everyone know that the final string edits are in for 13.9 and so all those willing to translate the new strings should be able to. Let us know if you run into any issues!

The latest beta turns this functionality back on. Please review and let us know in the beta thread if you run into any issues with it. You WILL need to update your RetroAchievement credentials in options as well as potentially rescan your games for achievements.

I believe most of the time it's because dip switches are different than default. The LaunchBox debug log should tell you if a score was uploaded or not (and why if it wasnt).

I mean inside of LaunchBox what exactly are you seeing that would lead you to believe the process isn't working?

I just ran an import without issue. What makes you think it's not working?

You'll need to reach out to support@unbrokensoftware.com about a potential refund. If you'd instead like to work through your issue you can create a new forum thread or bug report explaining your issue and we can try to help.

Sounds like both versions got imported but they were combined into the same game title. You can go to the one you do see in your library and then right click and edit the game. Are there multiple items in the Additional Apps section? If so this is what happened. If that's the case you can right click the game and expand it so that each version becomes it's own game entry and then do what you want from there.

Which emulator? I know if you are using RetroArch some shaders like HyperSpaceMadness cause a pretty significant increase to game load times.

Thanks, I'll make sure to post any findings I have when I review the API changes in the app

Go to Tools > Manage > Storefronts and turn off the automatic imports

Thanks for letting us know @WCopeland I'll have to review the code and ensure all the calls we were making still work, is there a channel you'd prefer I reach out to you or the RA team if I run into anything and need to ask a question, or raise a suggestion? Feel free to PM with the reply if you'd prefer.

Yeah, those are the files I'm referring to.

Inside of LaunchBox in the Options menu (found in tools) you can enable updating to beta releases. Then go to the Help menu and select "Check for Updates"

If you're on 13.8 this a known issue caused by changes M$ made to their backend recently. You'll want to update to the beta track to be able to run the wizard again.

If it's talking about Xbox or Epic you can turn off the auto import via the settings with LB closed to get around that.

Help > Check for updates. If you've opted in for beta updates it'll detect it and install it