C-Beats

If the M3U is just for the files you are already importing having the M3U imported is a waste of time on your part. LaunchBox will automatically create a m3u for you if the option is enabled in your emulator settings. There is never a reason to have both in your collection at this point afaik.

Tools > Scan > Scan for Removed ROMs

After review I think I know what is occurring. This is related to beta changes. The code we use to get the version of PCSX2 to display in the version column is causing the app to throw this message. We'll see if we can find a way to handle this a bit better.

This tends to happen when you're passing old PCSX2 command line arguments to new QT version. In the new QT version the switches are single hyphen instead of the old double hyphen "-fullscreen" instead of "--fullscreen" for example (without quotes)

Check your command line for MAME in Tools > Manage > Emulators... and see if you have the following command being passed "-artwork_crop" (without quotes) and if so remove it. This command line ensures the game takes up the most real estate it can on your monitor and so if you have artwork that wraps around the play area it could get cut off with this command line argument.

The multiple disc badge checks apps and if you have more than one app with the disc number filled it marks it as having multiple badges The multiple version badge checks apps and if you have more than one app that is a likely version (use emulator if base does, isn't auto before/after, obvious document file type, etc) that either DOESN'T have a disc value or has a value of 1 it is then displayed. I'd take a look at the apps listed in game details again and see with the above information if it becomes clear why you're seeing both. If you can't get it let us know and maybe I can take some time to look through your data file to see if I can't sniff out the reason.

Even null can be set in bulk edit. It sounds like @The Papaw is questioning why we don't set the flag for him like we do with storefronts, but the question was how to bulk edit them which is what this tool DOES and so I guess if that doesn't answer the question it may be worth restating the question to be a bit clearer on what the end goal is.

awesome, glad to hear

What I'm confused by is why the tool that does exactly what you're asking to do isn't acceptable to you. Also to make it null you simply remove that line in the data file entirely.

You can change themes in Options, no need to use the Manage Themes window. I've marked down to look into it though.

So select the 900 press CTRL+E, select the install field from the drop down, then in the check box check it until it's an empty square (for false) and then press ok.

Process is done, should be able to force download the new definitions and be good to go.

Several changes have been pushed today to the production server to help correct this matter both now and moving forward. The process that generates the new metadata.xml file has been started but DOES take some time to complete. Within the next hour you should be able to force update your Games DB files in your LaunchBox install and have this work.

Just copy the platforms/playlists from one build to the other. Files you are looking for are in \\LaunchBox\Data\Platforms and \\LaunchBox\Data\Playlists. I'd ensure you have that folder backed up before doing so.

Can you try to go to Tools > Download > Force update games database (or something similar, don't have app open atm). This should grab the newest metadata file and hopefully correct.

You can use bulk edit to change the installed field on all of them at once.

I'm willing to accept this as potentially valid excuse, but let's see to it that this is where your blasphemy around here comes to a screeching halt! NOW... where were we? lol

Should have shown those drive letters some respect and allowed them to stay retired! They paved the roads we now travel with their blood, sweat, and tears and you let some new thang come in and give it their title.... Have you no shame!

COMPLETELY off topic but MAN is it weird to see a B: drive... Even weirder that it isn't a floppy drive... lol

Typically we recommend C:\LaunchBox, but anywhere that isn't on the desktop, isn't the literal root of a drive should, or a location that requires admin rights to write/edit/delete work fine.

I'm not entirely sure what you're trying to accomplish if I'm honest. You mean the ability to automatically save on exit and load on startup? Save states? Game setting overrides?

That user hasn't been around in a long time. As long as the control loading the image is a FlowImage and UseImageCache is true (default value IS true) then it'll do this automatically.

If you look at the grid it's easy to see which games are ports since there are several games in a row with the same name and box art.

If a game has a Steam ID the only search that ever happens is for a DB record with that same Steam ID which I believe is causing what you are seeing. You can do the following to get around this and manually match your game to a DB record. Open the Edit Game Window Go to the Launching Tab Cut (CTRL+X) the application path value Go to the Metadata page Search for Metadata (changing the title if required) Select the DB record you want to match to Return to the Launching Tab Paste (CTRL+V) the application path back into that field Press OK to save the changes.