C-Beats

Not sure if you were referring to what Fursphere was talking about regarding the LaunchBox image cache, but our cache isn't "in-memory". We create an on disc cache of image that have been scaled down to the required size to make loading from disc in the future much faster. Most images are cached this way unless the theme requests the raw image. The file does sit in memory while in use though so you're not entirely wrong, just that the image we store in memory isn't the raw image you have in your image folder, but is the cached image we created. If we supported webp realistically it'd be support for the primary image to be in that format, and then use the cache the way it is now. Otherwise I'm fairly certain we'd have to do processing logic to get the file to render in the WPF Image control which would cause a fairly significant load time increase (especially on weaker CPUs). The conversion would still have the potential to save a lot of space though depending on how big your original artwork is and what file type.

You can change the "Arrange By" setting from the top tool bar to do something similar to this. Set it to Genre or Series and you'll get something close to this. We don't have asc/desc drop down per header like that, but there is a header splitting the games in the way your image shows.

Duplicate checks uses hash comparison to determine if it's a duplicate or not. Filename wouldn't work since the OS forces them to be unique anyway. We do also have a tool built into that you can opt into that looks at the image and can detect if they are likely visually the same despite having a different hash (for example if you have a jpg and a png of the same image). We don't list ALL duplicates, just any duplicate after the first file we find. If you have 4 of the same image only 3 will be listed as duplicate, and only if they all were tied to the same game. The tool also takes into account your image type priorities and region logic. If your game is NA and you have NA and Japanese art for a game the Japanese art would never be used by the app and so we mark it as such for deletion. The tool should never clear something that the app would potentially use in any of the automatic lookup stuff. It has no way of knowing if you're running a theme in LB or BB that requires that specific image type or not though. The tool does allow you to quarantine the files which will move them to a different location. You could use that option, then peruse LB/BB to see if anything appears to be missing, and then delete or restore the files depending on your findings.

Yeah. I think one thing we need to decide internally before that could even be tackled is what that field should or shouldn't be used for. For example should the Franchise name the game is a part of be included in the series, even if the game itself isn't a part of a series of games. For example should every LEGO game be labeled with the "LEGO" series, even though it doesn't have any direct predecessors or successors.

I have my metadata files here for systems that I've manually done. It has a link to a plugin JoeViking made that would let you import the field from mine (or anyone else's) data files. You MAY be able to use Skraper but we've had issues in the past with Skraper reeking havoc on users data files and so I'd tread carefully going that route and make sure to back up your data folder before trying it.

This tutorial looks to be using the most recent methods that I've seen to import them:

Just so I'm clear what file format are your titles in? WHDLoad should all be in *.lha files. The files also should have more than just the title. For example 1943's lha file should actually be labeled 1943_v1.3.lha. I admit I'm not 100% sure but was under the impression the file name has to match what the emulator is expecting it to be.

Pause Menu already has support for loading/saving save state. Doesn't have a display like this one does where you pick through multiple save states, or show the state screenshot though.

If you go to Event Viewer and look in the application logs there should be error records in there that would have more information as to why you are crashing. Also if you haven't already I'd run the installer over the directory just to make sure something didn't get corrupted or left behind in the shuffle. Running the installer doesn't overwrite any of your library data and is safe to do. Just make sure the installer isn't pointing to \\LaunchBox\LaunchBox after you click the folder you want it to install to.

All themes have Platform/Game Details reload on item selection. That being said Default does have quite a few transition animations that occur that others don't that would increase the time it takes to load in. Those time are static though and shouldn't be changing with a change of drive.

Go into Tools > Options and I believe in Visuals > Game Details there is a bunch of check boxes to turn items off/on. Make sure videos is checked.

Can already be done via Pause menu

You can enable an option in Tools > Options (I believe the General tab) that allows you to delete the ROM file when deleting the game from LaunchBox. Turn that on and then delete the game in LaunchBox (select the game(s) and press Delete key) and there will be a prompt asking you if you are sure you want to delete the ROM files as well. Say yes to that prompt and LB will delete them.

Error is saying that it tried to add up a bunch of a numbers from one of the fields on your game and ran out of fingers to count on. Typically this happens if you have a playtime or play count number that is far larger than humanly possible for some reason. I'd launch LaunchBox and then select that platform and take a look at the platform details and see if one of the fields displayed there is far too large. If so then use list view or audit to find which game is cranking that number so high and correct it. In the meantime I've left myself a note to take a look at that call and see if we can "give the computer more fingers to count with" in that function.

m3u support was actually added FAR later than multi-disc support. Is there a reason the "Play Version" option isn't sufficient enough? Sounds like you want something similar, just don't want the ability to use "Play" (or have play bring up the version popup)

This looks to be related to a bug that was introduced in I believe 13.6. Simply restart your PC and then without launching LaunchBox delete the folder. What is happening is that in that version a font is installed on startup from a folder in that directory and when LaunchBox closes the font isn't getting uninstalled and so it locks the font file which stops you from deleting it.

Not really seeing the type of error message I'd thought I'd be seeing. The one you posted mentions an error code that would imply a memory access violation. Not entirely sure what would be causing that as we only ever read our own memory allocations. Do you have a \\LaunchBox\Data\Settings file? If so can you open it up and look for an "EnableAutomatedImports" tag and set that value to false, and then let me know if that does anything to the situation?

Do the following: 1. Attempt to start LaunchBox and let it crash. 2. Open Windows Event Viewer 3. Look in the Application Logs page for error logs. There should be a pair that talks about LaunchBox crashing. Type top most entry in the grid typically has the actual error in it. 4. Post the error you find.

Tools > Manage > Storefronts. Turn off automatic imports.

I think you may be misunderstanding how MAME loads the file we pass it. We tell it "tmntu" because you chose to prioritize North American clones. MAME then internally looks in your folder for tmntu file, if you don't have it (because you're running merged set) it then automatically looks in the parents file "tmnt" and uses the files in there to load the tmntu clone files that are nestled inside of it. Typically LaunchBox DOES check if a file exists or not before starting the game, but if you'll notice we don't when MAME is your emulator. This MAME logic is why we don't. Just because the file name you pass MAME doesn't exist, doesn't mean it can't figure it out on it's own.

No need for apologies. Take the time to take care of yourself and get better. Wish ya a speedy recovery!

We've since added more logic into the current beta to help with this. It'd be helpful if you could opt into that version and let us know if you are still experiencing the issue there.

Yeah. I'm seeing the issue creep into my build over the weekend as well. I'll have to see if I can find the cause of this one as well. Basically having issues with the scrollbar not being able to decide if it should appear or not...

Unless I'm misunderstanding you the thing you're requesting is already built into our additional app feature. You can set the disk number on the app. We can build a m3u file for you and pass it to the emulator if you have that option disabled. We also have the ability to change disc in the pause menu when doing so. The only thing NOT asked is what disc you want to load, you do have to pick the disc through the versions menu on either LaunchBox or Big Box

Yeah, I also had issue when the razer software wasn't running that caused similar stutters in applications. THAT could have been a bad driver on my side though as I tend to not update drivers unless I run into issues.