C-Beats

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.

When you do so, can you successfully restart Big Box or do you have to restart the computer first?

Yeah, it's a thing we keep a pretty active eye on. Unfortunately there are a lot of variables that affect stability and it's not always a straight line to the solution.

What theme are you running? We test in default and last round of testing both Jason and Faeran were able to keep machines running for a week without issue after the latest round of changes.

If you're not already, use VLC as the media player. WMP is fairly unstable comparatively. Also what version are you on? I know we had code changes fairly recently to help with stability.

Not been a part of this entire conversation to see what the pinch point you all are running into but this is already possible using %romfile% in your command line. So if you wanted "ares.exe c:\Path\To\Rom.file --fullscreen" (without quotes) it'd be "%romfile% --fullscreen" (without quotes). For that to work you'd probably want to leave quotes on and then you'd want "Remove file extension and path" to be unchecked. Both those check boxes affect what that variable outputs. %romlocation% doesn't unfortunately but it'd be interesting to look into if we could change that without breaking anything for users.

It's in arcades. Local Dave and Busters has it. It's basically the Magic Tile mobile apps turned arcade game. You get like a minute or two to see how many keys you can press correctly. Missing a key takes 10s off your time. As of last time I was there I told the top 3 places in the leaderboard on the machine. PLEASE hold your applause....

Should have turn it into something that played this game! WAY more fitting!

Inside of LaunchBox, if you go to Tools > Download > Force Download Games Database (or something similar) does it correct the issue?

If you're referring to Big Box it's Options > Video > Use Game Background Video (or Platform if you want those to display like that as well). That being said themes MAY not respect this setting depending on how they are built.

Think something may have happened with your post @kurzih, unsure why it showing you quoting something not said. May have hit the quote and then overwritten it with your own question.

Can use the data from my collection as a starting point. Can read more here

I'd take a look at where the second install actually installed. The installer when ran manually adds "\LaunchBox" (without quotes) to whatever folder you select. It's possible you created a LaunchBox folder WITHIN your LaunchBox folder and installed there on accident. When you run the installer manually, select your LaunchBox folder and then remove that last "\LaunchBox" (without quotes) so the path IS the folder in question and then run the installer and all should be well.