C-Beats

The install check looks at local files/registry (depending on the storefront). It's possible something didn't get cleaned up correctly after you uninstalled the game. Do you have an example of a game and what storefront it is? I can take a look at the code and find out where we are looking so you can check.

If on current version PS3 import should already look for eboot.bin file. You can also just go to the root folder in File Explorer and search (in File explorer) for "eboot.bin" (without quotes) and then drag the results to LB to import them.

I'd be curious to know what version you are running that you DON'T see controller metadata as we have it for most platforms. Also we DON'T ever check the "portable" box so something isn't quite adding up.

This theme has been updated to v1.16! This version finally corrects the issue with the Platform and Game Details sidebar spazzing in and out while it decides if it needs a scrollbar or not...

@goin3d @Beforedeth @Vader Can you update to the latest beta and let us know if you're stilling having the issue with your options window not opening correctly? We believe it to be resolved in this latest push and would love to have confirmation as such from some users who were experiencing the issue.

Looks like a setting regarding the GameDetails size may be broken for some reason. I'd hide and unhide Game Details (press Ctrl+T twice) and see if that corrects.

We haven't reached back out to SteamGridDB because we were told they'd prefer us NOT to integrate them until after their 3.0 API release which hasn't yet happened (at least from I can tell via their Discord). Until we get the green light from them I'm not sure we'd officially integrate them into LaunchBox.

I've not ran into any of the reported issues but planned on rebuilding my Odin's collection for other reasons anyway. Maybe I'll just look at doing so sooner so I can see if I can replicate on mine. What firmware version are you running on the Odin Pro (those reporting with one)? I know some of AYN firmware has been a bit more finnicky than others and want to ensure I'm on the same version before continuing.

Is a bug in 13.6 related to some changes RetroArch made to their build bot process. Should be able to grab the most recent beta release and download it successfully.

Probably aren't getting any replies because this report REALLY doesn't make too much sense. Launching logic is literally the same exact call from LaunchBox or Big Box and so I'm not sure how something like that would happen. Are you running any plugins? If so I'd remove them and try again and see if you run into the issue. I know in the past we've had a few community plugins cause unforeseen issues launching games.

Moved your post to a more appropriate section. You should be able to do either of the following: Tell the import wizard NOT to search in subdirectories Drag drop the files you want to LaunchBox and then run the import wizard from there

This is related to a feature pushed in 13.6 that allows for more accurate Steam Id matching. DB Games now can have Steam ID assigned to them by a backend process automatically and LaunchBox uses that ID for matching ONLY with Steam titles. The backend process is still being worked on to improve that id matching though and so there are a few holes that need filled in. The current workaround is to do the following: Open Edit Game Go to Launching page Cut the "Application Path" from it's text box Go to Metadata page Search the Database Select the match you want to associate to Go back to Launching Page Paste Application Path back in Save changes

I'm pretty sure those playlists are all auto-populate playlists and use the platform name as one of the credentials. When you changed it from Arcade to MAME it broke the connection. Options would be either rename the MAME platform BACK to Arcade, or edit each playlist and change it to look in MAME platform instead of Arcade

You're going to want to reach out to eXo and his community on his discord. They'd be far better suited to answer questions about why the bat file isn't doing what you expect it to.

Sounds like some of this is caused by your current settings. You can start a game with two presses of the "Select" button if your settings are set correctly. One to pick the platform, and another the game.

I'd have to look. I haven't touched this theme since the day I made it, and I typically don't even use the GameDetails screen so it wouldn't surprise me that it isn't working as well as it probably should.

You can launch the game directly. You don't have to use GOG Galaxy to play a GOG game (unless the game itself requires it).

The issue has been identified and we have code change in place to correct that will be in the next version. At the moment the issue is that RetroArch added a new item to their build bot directory. This combined with the fact that their GitHub has a newer release than the build bot is causing several compounding issues. At the moment there is no work around and you'll need to install Retroarch yourself.

I understand what you're reporting (or believe I do) but cannot replicate. I can't even right click on the toolbar item without it stopping the video. How long have you been experiencing this? Also can you go to Tools > Options > General > Video Playback and let me know if you are using VLC or WMP? If you change the option do you still run into the issue?

This is a bug in 13.6 and is corrected in the beta that is currently available.

Can you PM your \\LaunchBox\Data\Settings.xml file? Be interested to see if I can use them to replicate the error. I believe it's related to how you have Game Details configured but haven't been able to replicate on my end to find the cause.

Just so I'm clear are you reporting that you have two platforms where you should only have one, or that the view is different in one platform vs the other?

At this time Android does not track game time played. From what I recall Android was a bit harder to figure out which process had priority so we could tell that you were actually playing the game. Last I knew we were still at the phase where we are collecting data to find how best to get this feature added to Android. Jason can chime in if I'm incorrect in that assessment though.

Right, which isn't an option if you told the importer to only bring in the parent. If you leave the import options as default you'd definitely have the clones listed.

RetroAchievements have once again brought their entire API down. Any features that were working are once again going to cease to function correctly in app.