Jason Carr

Force quitting LaunchBox can and will cause you to lose any and all data changes; it can even just straight up corrupt your data. That's the nature of a force quit. You've somehow got all kinds of issues on that machine, most of which I have never seen before. At this point I'm wondering if there's something fishy going on with the system somehow. I have your data to do some further testing, so I'll see if I have any issues. So far though I haven't run into any issues with your data.

We added a check on additional apps. It didn't do that previously.

You do have a LOT of arcade platforms lol. If it's asking you to confirm, then it means that you have some games or additional applications that are not set to MAME.

Thanks, good to know. I could be wrong, but the above log file doesn't look right either. Let me know if you can reproduce it with a definite log file. I suppose it's possible that a log file isn't created when that happens. You can look at the date/time on the file to know if it's new or not though.

I see. We fixed an issue related to controllers that happens only when first starting up Windows (Windows glitch). I'm guessing it's fixed in the betas. Can you update to the betas and test?

Just read that these issues are happening with 10.14. We have specific fixes in place for issues closing in the 10.15 betas. Please, if you post in the beta thread and aren't using the latest beta, please note that in every post. Otherwise, it's too easy to get confused as to what's going on. It would be really helpful if you could update to the betas to confirm whether or not you still have these issues @mcfilmmakers.

You mean not closing and staying open in Task Manager? This baffles me, because I've never seen anything like that, unless it's a new issue with recent betas. Guess we better do some further testing on that to confirm. Did you have any issues like that with 10.14? I see. This is starting to make slightly more sense. Perhaps we're not always saving a platform properly when moving it into another category. Is that the *only* thing that you've seen not being saved? The other possibility is that there's somehow an issue with your data that is preventing certain platform XMLs from being saved. Can you zip up and PM me your data folder?

That's a new issue that I've never heard of. The log file you posted though shows that LaunchBox loaded up the main window and was running it, so it doesn't look like it's the correct log file for that instance. It would be good to see the correct log file if you have it. Have you ever run into this issue again? If LaunchBox eventually disappeared on its own, that means that most likely it was still saving things in the background. Unless Windows magically killed it, idk, but I've never seen that happen. What changes did you make that didn't save?

Sorry, yes, I misspoke. If you delete the ThirdParty/7-Zip folder, you have to reinstall over top in order to re-create it. I don't think anyone will need to delete that folder after all. Yes, we can add that before the official release. This is probably because the Scrape As value is being used. It's still using the platform name, though it uses the Scrape As value if it's populated. Got it, thanks. I'll put that on the list. What theme are you running? It sounds like I'm going to have to do some further testing on this issue. I haven't seen it since I made the changes in the beta, but I have seen it reported a few times since.

The reason why we use the game's region is for correctness, really. Most No-Intro ROMs these days have the region listed in the file names, so we can accurately follow the region in during import. If you import European ROMs, you should get European boxes if they are available. To be honest, I don't think we'll be changing that, but I suppose we could add an option to override that eventually. Regardless, yes, you can always either change or empty out the Region field on the games, or just move the media. But honestly, at that point, you're technically making things less correct/accurate.

@natedog Very cool, and good to hear. I don't really have a solution for the issue of it re-downloading artwork that you don't want, other than to just uncheck those categories so new media doesn't download for those categories. In theory, you can just put your default image into the XAML directly, and then if the image is available it can just put it over top. That might have some issues though with the transitions. Otherwise, there are some more complicated solutions, but I don't have the XAML for them readily available (I'd have to hunt through all the themes on the forums).

It appears that there are some slower-than-normal speeds going on for some reason, yes. @C-Beats has also been experiencing slow speeds yesterday and today. Hopefully it's just because something went down somewhere in the Internet infrastructure and so things are taking an alternate route for some people. I've got full speeds, but apparently not everyone does. But first off, sorry for the trouble. It is unfortunately not true that downloading things from the games database will always max out every connection from everyone in the world. Sadly, that's impossible. We don't control every node from the servers to everyone's PC. We've never moved to a distributed system, no. We're just not that full of cash, unfortunately. Building a distributed system across the world is crazy expensive. Amsterdam is the *only* node. In the past, we've been able to fix some speed issues by tracing routes and contacting our host. But it is an extensive process and requires running a bunch of tests on the destination network. However, I have a hunch that this is only a temporary issue. We can contact our host and pursue this further though if it doesn't resolve itself soon.

Beta 9 is out now with the following: Fixed the Retro Score in the Game Details Sidebar not hiding if unchecked Fixed a potential null reference error when playing games Audit should now be up to par and ready to go (various things fixed and added) Fixed the 7-zip wrong version issue (but it's not force-updated for this version so you may need to delete the LaunchBox\ThirdParty\7-Zip folder in order to fix)

I believe that popup depends on the platform name for the game. What platform is it? Not really sure what would be causing it then, but it does sound like it's somehow performance related. Any chance it's still populating the cache in the background when this happens? How long have you waited for it to update? I'll review the CEF closing thing again then to see if there's anything further I can do.

This looks to be the same issue that should have been resolved in the betas, caused by the Chromium Embedded Framework refusing to shut down. Are you running 10.14 or the betas? I'm wondering if this is somehow a driver issue or something weird like that. If anything, it's probably related to video drivers. I know that doesn't likely help, but I haven't been able to reproduce it so I don't really know how to solve it. Do you feel like it's a new issue in recent versions? Can you go back and test an old version to see if it's only the new versions?

So apparently we included the "7za" version of 7-Zip, which apparently doesn't extract as many formats as the normal version. That was my mistake; thanks for bringing that to my attention before the official release. I'll get that fixed for the next beta. Version is available currently in the Arrange By drop down, but I see that it's not currently available in the filters side bar. Is that what you mean?

To be honest, I think that's a glitch. I checked to make sure that no pending items were left before I archived them. I'll have to look into why that's not updating.

So the gaussian blur process that blurs the backgrounds does require some heavy processing, but I've never seen it cause severe performance issues. Are you using a USB drive or anything with slow disk access? It does write a new temporary image file to the drive to do it. It also uses multi-threading to attempt to do it quickly, but it should only use the number of cores available on your CPU. Still, I suppose older CPUs could be more affected by it.

The media is almost always the biggest cause of performance issues, of course. Media-heavy things aren't always easy to do quickly. That's odd, but it's a good path forward. I know that the blurred backgrounds aren't causing much lag on the systems I've seen and tested, so I'm guessing something funky is going on with them on your system somehow. Certainly strange. It almost feels like you're using a broken/old blurring mechanism. Are you using the LaunchBox default theme? Any chance you're using a custom theme that might be causing the lag? Thanks, sounds good.

I missed the ThirdParty folder when I typed that out. Do you have this folder?: LaunchBox\ThirdParty\7-zip\x64 It's the x64 folder I'm curious about specifically. Also, are you on a 32-bit or 64-bit system? I just tested installing the latest beta to a new folder in the default location, and I'm still not seeing any issues. My only thought is maybe you're on a 32-bit system and the 32-bit version isn't working?

You can update to beta releases by going to Tools > Options > Legacy > General > Updates in LaunchBox and checking the box to update to beta releases. Then you can force an update check by going to Help > Check for Updates.

I'm not 100% sure that it has to do with media. One thing you could try doing temporarily though is renaming your media folders so that there's no media in LaunchBox to see if you still get the issue. Make sure you take a backup of your Data folder first though (but that's automatic unless you've turned off automatic backups).

Per jumping back to the top on delete, you can stop that from happening if you disable dynamic box sizing. Dynamic box sizing affects a lot of things like that. It's worked the same since we added it.

Well, it doesn't appear to be a data issue because I still can't replicate it on my machine with your data. I suspect that it's probably primarily a performance issue. It could be somehow caused by media though, since I didn't have any of your media to test with. I'm not sure about a fix for it though, since I haven't been able to replicate it, unfortunately.

We have replicated this ourselves and already fixed it for the next beta. No need for further confirmations of this.