C-Beats

As you've been told several times, most of the delay you're complaining about isn't the program being slow, it's a UI animation in play put there by the theme designer. Changing the theme would drastically change your experience. Not saying there isn't room for improvement in either application, but a lot of what you've complained about in the past you already have ways of opting out of.

EA may have changed their launch URI. I'll take a look and see if I can replicate. I know they've pushed similar changes in the past so it's a very real possibility.

Are you referring to hard drive space, or memory (RAM)?

Subtitle text by default is dependent on what your arrange by setting is. To get platform to display under there I believe you have to be arranging by Platform. You could of course do as @Retro808 stated and just change the theme to hardcode the platform value in that line though.

We get games lists from the Steam API, not any local library files so things manually added into Steam will not appear in the import process or be automatically imported.

If you close LaunchBox in full screen it should open in full screen since it remembers size/location.

This is almost always caused by one of the following: You have a file sync app locking the file we are trying to change on close and so the save event fails You have "-backup" files in your data folder put there by Skraper Some other unforeseen issue saving the file out If you haven't already turn on debug logs and go through the process again and then look to see if there is anything in the logs generated. You'd want to look in the 2nd most recent log (since the newest is you opening the app).

Error message tells you the issue. Your drive is full and we can't write the file out because of it. Remove some of the files on the drive to make room, or move LaunchBox to a drive that isn't full.

It's done when the image is requested. The WPF control sees you want a game image, and then we check if the cache exists, if so we use it, if not we build it and then use it. It's why Big Box seems a bit sluggish when you first start using it compared to how it behaves several sessions later. It's because those cache images have been built then and so the extra step isn't required. Yeah, same principle applies to other frameworks (such as WPF). Much faster to use a 100x300 image than a 1000x3000 one.

Fairly certain OP is referring to the website, not the in app index like you're ticket is talking about.

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)