C-Beats

Until we add the ability to white/black list extensions for auto-scanning per platform this is unlikely to change. Typically text files like that are supporting files and NOT the ROM. TeknoParrot is an exception to the rule and we don't want to break setups for virtually every other emulator.

What configuration are you using? Could you post a screenshot?

Ah yeah, I did name the wrong file. Glad you got it sorted out though

Should be able to add a left margin on the grid on line 169 of GameDetailsView.xaml to push the search bar to the right some. Something like Margin="48,0,0,0" would move it to the right 48 pixels.

Cool so after you push OK? Do you see the progress bar at the top starting the import process at all or no?

Where in the import process are you all running into this issue? At some point in the import wizard, or after the game list has appeared and you push OK to start the import?

Or they can just message here were we've been tracking it since the day of release. I get your frustrated but needlessly bogging down the team trying to get the issue resolved seems like a pretty tactless use of your time and resources (as well as theirs).

I don't disagree with anything in this statement but just want to add to make sure LaunchBox and all it's processes are CLOSED before you go manually altering your data files. Making a backup first wouldn't hurt either.

Merged your post to this thread so it's easier to get ahold of everyone having this issue at once. For those that have reported in and are using plugins such as the PCSX2 Configurator plugin. Could you please remove those and let me know if you're still having the issue?

I believe there are apps on the app store that will help the app do what you're asking. We had it in the app but it broke functionality with things like Samsung Dex which require the app NOT be a home app to work properly and so it was removed quickly after.

The save feature reads your retroarch.cfg file and uses information in it to determine where you save files should be located for any given game. As long as RetroArch see's your save files the goal is that LB will as well. If you have a scenario where that isn't the case let us know and attach your retroarch.cfg file found in the root of your RetroArch folder.

Yeah, that's what was meant Should work flawlessly. Installer doesn't touch data files or the folders eXo collection puts stuff in so you're safe to run the installer over that build.

This error almost always means that your virus scanner quarantined a file it shouldn't have. Running the install over your install should put it back in place (assuming it doesn't quarantine it again). When doing make sure you point the installer to your LaunchBox folder and not let it point to \\LaunchBox\LaunchBox\ like it likes to do when selecting the LB folder via it's browse tool. If you don't have the installer for the version you're using you can reach out to support@unbrokensoftware.com and ask them for a download link for it.

LaunchBox requirements to run smoothly are higher than MAME is for the most part. Some of the newer CHD games may require more but they are almost all 3D games that I know of. I admit I don't play games that require them ever.

Can you all turn on Debug Logging via Options and get that error to pop and then send the log file generated? Curious if it has more information we can use to track down the cause.

Would be pretty difficult to find something that can't play MAME games (at least without shaders). I have 50USD handhelds that can play MAME... lol

I'll be working tomorrow almost exclusively on this issue. If anyone could provide the following bits of information it'd be very helpful in determining the cause of the issue! 1) Is the location your importing from on the same drive as the LaunchBox install? 2) Is the location your importing from IN the LaunchBox folder? 3) What import method are you using to import your games? Import wizard, drag/drop, something else? 4) What folder is the games folder of the platform you're importing games to? Does that folder actually exist? 5) What platform are you importing for? What is it's scrape as value set as if not a default platform name?

As you've been told several times, this GUID is appended to ensure that images that are for that game in question is assigned to that game in question. If you don't want a GUID to appear in the image files name your files in a way that no two games in the same platform have the same title. Typically to do so you'd append the publisher name in parens. Something like "Game Name (Publisher)" (without quotes). Please stop bringing this feature up or I'll be forced to revoke you post rights entirely.

As you are well aware this is a feature of LaunchBox. If you don't want the GUID combine your games.

Wondering if it wasn't just a games database metadata file issue. New day means the app auto-grabs it which corrected the problem.

Simply copy pasting the entire text of that error window into the beta thread (when on beta) would suffice, maybe give a little insight as to what you were doing when it happened, and whether you can get it to do it EVERY time or if it seems fairly random.

Both of you experienced a new bug in the beta but *check notes* DIDN'T report it, and then *checks notes again* wonder why you're having an issue in full release?

The cookie they give us to use expires pretty quickly which causes issues. We've looked into it in the past and wasn't able to find to anything. If we do we'll move to it. It's definitely annoying.

Tools > Options there is a Game Controller (and Mappings under it) for enabling Game controllers in the LB interface. If that is enabled for that controller by default left stick will make the mouse work the way you're describing.