C-Beats

I've never heard of our app doing anything like this to a user's machine. The mouse stutter thing I've heard before, the rest is new. For the mouse stutter what usually is affecting it is having the "Use All Controllers" option when you don't have one plugged in. To disable that in LaunchBox go to Tools > Options. Scroll the left list all the way to the bottom and select "Game Controllers". There is a "Use All Attached Controllers" option. Make sure that's turned off.

If you go to LaunchBox and go to that platform, what is your Image Type set to? I'd assume it's screenshots instead of Boxes. If you change it to Boxes then go back to BB does it correct it?

I'll review the Ediit Game window code, we shouldn't be allowing you to save a game entry with a blank platform value. All the codebase assumes that the platform HAS a value in it and so not adding one can cause a lot of unforeseen issues. I've jotted it down as something to look into.

That temp folder isn't the one we create. Ours is in \\LaunchBox\Metadata\Temp. You probably have a third party app or plugin in use doing it.

In LaunchBox, go to Tools > Manage > Emulators. Select MAME and press Edit. In the window that appears is a text box labeled command line, in it remove the "-artwork_crop" (without quotes) bit and then press OK to save.

Scanning should update the auto-pop playlist appropriately.

Yeah, best bet is to just search for the term and delete what shows up. Another good word to search for is "shanghai". There is a series of mahjong games by that name that spans several consoles. Would be another way to narrow it down.

The Platform Category hierarchy is determined by the data in \\LaunchBox\Data\Parents.xml

IF you're referring to MAME I believe they all have the genre of "Tabletop / Mahjong". You could filter by that and then delete them all. You could do the same just searching for the string "mahjong" and deleting the search results.

Means that the Portable checkbox in the Edit Game window has been checked for that game. This field isn't used by the app at all really, but I believe the initial intent was to allow people to mark which games were portable (meaning they could be moved with the LB install) and which weren't.

You can scan your entire library by going to the Tools > Achievements > Scan for all games.

To manage the Windows related auto-scan you'd want to go to Tools > Manage > Storefronts... and you can turn off/on certain storefronts there. Deleting a game auto-imported by that system SHOULD blacklist titles though, so unsure why'd you see them return.

Yeah, CHD should play nicer with it. Be far easier to manage all your game files that way as well.

Not at this time. The feature is still pretty new and so isn't as in-depth as some of our others. Always trying to keep an eye and ear out for ways to improve it though.

Thanks for report @RIKUSYO, I got some time during lunch to test this out and there does appear to be some unintended scaling when using a spine image we'll have to take a look at. Thanks for helping us track the issue down!

You can disable this feature by going to Tools > Options > General > Automated Imports

You'll need to contact support@unbrokensoftware.com and see if they can help you. You will need to provide the license files so they can vet out why they were banned. Locking the thread since no on here can really do much about it.

Which? There are two. One for storefronts, another for ROMs. If both are can you tell me what game/system you're seeing come back?

Do you have automated imports turned on? If so they may be reimporting a game that is in your folder but not in your LaunchBox collection.

Sounds like you have something taking focus away from MAME and putting it on the LB processes which is how we detect that the screen is required.

Apologies. I meant with the override options now working. Like in English if you check the box to manually set the size, does the model appear different when changing the size?

Again, this could already be happening by the OS. That "optimization" is just shunting the memory of the app into the page file so the OS doesn't have to later, or forcing an OS level garbage collection that wasn't really required yet by the OS (or a combination of the two). Only way to drop the actual memory footprint like that when playing a game would be to dispose all media and dump all cached data from memory. To do so would mean that once you got BACK to LaunchBox or Big Box we'd have to then load it all back up before you could use the interface again which would take several seconds or more. This is also assuming you aren't running any background tasks at the time that requires that information. Then we'd have to pause those processes as well. Most of this would require us to write temp data to a drive that is also now being read from by what ever application you just started which could bottleneck both applications.

Would you be willing @RIKUSYO to change the language to English and then see if it works the way you're expecting. We've had issues in the past with bugs related to certain languages and how they alter numerals. I'm curious if it's possible that's what is going on here.

To be blunt, it's 2024. 1GB is no longer "a lot", especially for a media intensive application like LaunchBox. You're actively showing another app using almost 6GB ;D. Secondly just because a task shows memory in use in task manager doesn't mean its actually using that full amount on actual RAM. The operating system will push some of the more stagnant bits of data to your page file automatically when the app is in the background and the memory in use is needed. That being said if you really want to try and reduce the memory footprint you can switch to list view, which should save memory since we aren't loading images. Can also try different themes, as they can display things in a way that takes even more RAM or just has more stuff displayed. You can also hide the game details. Also if trying to pinch RAM Big Box operates far more lean since it doesn't have to load DB definition files that LaunchBox uses and so tends to operate at quite a bit lower usage.

What import did you use and what is the file extension of the files you're using? I know we added support for Amiga lha files to parse those files names better on import which should have made a large part of that unnecessary.