Jason Carr

Sorry for the super late reply here. I haven't experienced those performance issues with AllNightLong, but it makes sense that it might require heavier hardware than the default theme. We've overhauled a ton with the latest betas, so it's possible that they may fix some thing as well.

@Pixelpiper It makes sense that images you scraped with an external scraper app will result in duplicates. We use CRC checksums to look for duplicate images, and also the rough image matching as an option. If you turn the rough image matching on, it'll probably catch a lot of those duplicates, I would think.

I see. Unfortunately I don't think it'll currently be possible to force LaunchBox to use the tweaked version of the XML. The problem is that it tries to create that file and use it all in one step. So I don't think there's a way to override it. So I think the best option would be to temporarily disable devreorder and try again.

@TzTok-Jeffy Sorry for the late reply here. That makes sense as to what's going on, though. That said, I don't think LaunchBox is doing that to the folders, so I think it must be being caused by an outside app. Are you using any third-party file syncing tools or services or anything of that nature?

It's hard to tell 100% since I've never used that software, but yes, it sounds like you're on the right track with what the issue is there. If MAME is giving you an error when we're trying to run that command line, then that error will need to be resolved before MAME will work in the importer.

@Zombeaver Will need to fix this issue with C64 Dreams. Apparently he mistakenly distributed it with his games database account connected to it. Thanks; I've removed that score.

We've fixed a ton of stability issues in recent betas, so yes, it's possible that it was fixed. We also have a new beta coming out today that has some additional fixes.

@Kiinkyfoxx I just tried everything with the latest version of MAME (and the LaunchBox beta) and didn't have any issues. Is it possible that there might have just been a bug in MAME 229? The version I just used was a newer version. What error are you seeing in the INI file?

This should be fixed for beta 8, I believe, which should be out later today.

Sorry for the late reply @Darkrys. This may be because of the email address that you're using. What are you entering into the various fields for registration? You can PM me instead for privacy reasons if needed.

Very late reply, but make sure you mark your main monitor as the primary monitor in the Windows display settings. Most likely, that should fix any issues like this.

Thank you @Cauptain. @cyanjiang @Bardock @MajKSA @gamehacker @Kondorito @Nyny77 @alexposad @k_kutsugi We have until this coming Monday to get the final translations in.

What email are you using? You can PM me the email address. I sent it to the email that you used to register here on the forums. I'm guessing you're just using a different email.

Beta 7 is out now with a bunch of fixes and stability improvements. We've been going to town so we didn't keep track of them all. Please let us know if you run into any issues with this beta. We'll be going back through this thread here shortly as well to make sure that everything is covered.

We're always working on improving performance. That said, yes, using a slow USB hard drive is not a recipe for a quick setup, and it will never be. If you need portability and better performance, use a file syncing tool like FreeFileSync (highly recommended), and sync over a network between SSDs. That will improve not only load times, but the performance of the entire experience. There's no need to store large ROM files on an SSD (they can be stored anywhere really), but the media files really need to be on an SSD for the best performance. The rest of the complaints I've addressed about 1,000 times over on the forums, so feel free to just search for my responses elsewhere. I've learned that answering the same stuff over and over again just gets in the way of progress.

Thank you all. I have these translations updated for the next beta (beta 7), which should be out either today or tomorrow.

Hey all, it's that time again; we're looking to get translations in for this upcoming release. We're hoping to release on Tuesday next week. Thank you all so much for your ongoing help. @Opak @cyanjiang @Bardock @MajKSA @gamehacker @Kondorito @Nyny77 @alexposad @k_kutsugi @dukeemu @Just001Kim @Cauptain @Cauptain Apologies, but I missed getting your translation into this beta. I'll get it into the next one.

Beta 6 is out now with the following: Improvement: LaunchBox now utilizes a newer SSO form for the Epic Games login which should fix the issue with endless CAPCHAs Improvement: LaunchBox now has the ability to log out of Epic Games in the Options menu Fixed: Corrected an issue where LaunchBox would throw errors looking for an Epic Games Launcher installation Fixed: Potential error when trying to use a FlowImage in a platform view Improvement: Improved logic regarding when and how resources are released We're still hoping to put out the official release next week, but we're still in the process of tracking down a stability issue that was introduced in the previous changes.

Beta 5 is out now with the following: Improved endless navigation in the new wall views Improved scrolling performance with the new wall views Corrected error when quickly scrolling through the search index Corrected error when returning to Big Box after launching a game through the wall views Improved the disposing of the FlowImage and FlowVideo controls Improved image caching logic and performance Fixed an issue where the FlowContext and FlowImage combination wasn't working correctly in platform wheel views Fixed an issue with scrolling when viewing manuals in Big Box We're doing more performance and memory testing with the upgraded wheels, CoverFlow and new wall views. Planning on spending this week focusing on bugfixes and performance improvements, and then hopefully we can put the official release out next week.

Hmm, the 7-zip consoles still running is not normal and is probably the clue as far as what's going on. I haven't seen that happen myself, at least not recently. I can't think of any reason why they should still be running after the app closes. It's also possible that they could be the cause of the app not closing. But of course we need to pinpoint why they're not closing. Can you try unchecking this check box? That's something that you'll definitely want to keep checked in the long run, but it would good to know if that process is the one causing the issue.

I see, interesting. I guess it's the first time I've really heard of that. What are the apps that require admin rights? Just to make sure it's not the issue, it would probably be good to test without admin rights to see if it happens to resolve the issue. It's a weird enough issue that it's not out of the question that it would be caused by the admin rights thing. No need to send us a bunch of log files again; we just need to know if you're still getting the issue without admin rights.

@LiL fleX Thanks for all that troubleshooting. One important thing to note first: it is never a good idea to run LaunchBox or Big Box as admin, and it should never be required. My first recommendation would be to stop running them as admin. We've seen some weird issues with that, so who knows, that could even be the stability problem. Why are you running it as admin in the first place?

Hi @DevarionArias, LaunchBox works on saving all the data after it closes. So sometimes killing it like that can actually cause data issues. If lots of changes were made, sometimes it can take a bit to finish saving them. How long are you waiting for LaunchBox to properly close?

In theory, Big Box supports "active marquees" with no issues if a theme developer built a theme that did it. We'll probably put something similar on the next poll. We do not plan to integrate Hyper Marquee (not much point in that), but we are interested in improving the Big Box marquee support.

@JoeViking245 Yes, much appreciated. It's good to know that 0.162 is the earliest version supported. I am curious if we could alter the code a tiny bit to support "game" as well; that might be worth doing if it's easy and it allows earlier versions to work without any other issues.