C-Beats

There is a Manage Installations section of the context menu within LaunchBox that should let you pick which version you wish to install. I believe we also added that functionality to GameDetails in the Default theme of LaunchBox with a drop down next to the Play/Install button.

I'd verify on the first page of the Edit Platform window you don't have that platform hidden in Big Box platforms view.

Are you still seeing this issue in LaunchBox 13.7? Iff so could you provide an updated error print out from that window?

I'm going to assume not given the description, but are you running Big Box as shell? Is about the only reason I could think of for any difference. LaunchBox and Big Box fire the exact same code when launching a game so there being a difference between the two doesn't make a ton of sense to me.

@RavenDarhk Sounds like you may have had an overzealous AV get in the way of the 13.7 install. First step I'd take is to run the installer again over your existing install (making sure you aren't pointing it to the \\LaunchBox\LaunchBox folder @Retro808 is referring to) and see if that corrects the issue. I'd take a look in the \\LaunchBox\Core\ and make sure that you have both a LaunchBox and BigBox .exe and .dll file. The error reads like one of those 4 files are missing which typically happens when an AV quarantines the files.

Do you have multiple games with the exact same name in MS-DOS?

You need to leave those extra characters in as it tells LaunchBox which of your "Super Mario World" games that image actually belongs to. Without it they will all attempt to use it.

Moved this post from beta thread as it's unrelated and should be it's own post

Thanks for confirming. Bout to give some one an early AM panic attack! lol

Eclipse theme has a lot going on in it regarding plugin use and out of the box solutions. I'd first revert to default theme and see if you still encounter the issue or not. Where the error stack trace is pointing is that something isn't able to load correctly on startup. If you don't already I'd also enable debug logging via LaunchBox's Option menu. Then see if there is anything in that log that would help explain what is going on. COMPLETELY unrelated, but how did you get your error form to look like that?

This should be corrected in the beta already. Are you still seeing this error pop up in the beta build?

LaunchBox doesn't really care about what files you hand it, so should

This is intended behavior at this time. The idea being that we want the app to get you up and running as quick as possible with the artwork actually used in the app by default without bloating out the hard drive space required for a lot of media you may never even see or look at.

Beta should correct this issue for you. To get the app to open correctly open the file \\LaunchBox\Data\Settings.xml in a text editor. Look for a line that starts with "<EnableAutomatedImports>" (without quotes) and set the value to false. Save and close the file, then open LaunchBox.

Could you update to beta and let us know if you are still having the error? It is related to arrange by settings, but no one on the team can replicate. There have been other changes related to similar issues in the beta build and I'm curious if that corrects things for you.

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.