Jason Carr

Not entirely sure yet what all is coming. Keep your eyes peeled. We're all good over here. Lots of closures but nothing that's going to get in the way of LaunchBox. Health and safety are important, but fear has blown everything way out of proportion. My main concern at this point is the economy...

What errors are you seeing? What are the exact error messages?

Hey all, for the most part I think the LaunchBox Games Database has been running smoothly for a very long time now, but I've had an item on my list to step in and make a few changes/fixes for a long time, and I finally did it this morning. They're all minor fixes/changes, but I thought I'd update everyone, regardless. Here's a list of what all I did this morning for the DB: Added an option to clear out your default collection. This was needed because there was previously no way to empty out your default collection, so you couldn't start over (for example, when syncing your local collection to the cloud). You can now do it from the Manage Collections page: https://gamesdb.launchbox-app.com/collection/manage The above Manage Collections page received some minor usability improvements as well Finally removed the little Alpha banner in the top right (lol, about time I'd say) Fixed a few broken links Fixed an issue where occasionally images that were marked for deletion (and approved) didn't end up getting deleted Fixed an issue where occasionally alternate titles that were marked for deletion (and approved) didn't end up getting deleted For both images and alternate titles, any images or titles that were previously approved for deletion but never actually deleted have now all been deleted successfully (so the backlog has been fixed up as well) Please let me know if anyone sees any issues with the above. Thanks as always to everyone contributing to or moderating the DB. It's really grown to be an amazing asset to the community, and I think it's very quickly rising to be the best available resource for game metadata and images (if it isn't there already).

I have not tested exiting the PS3 emulator any time recently, so it's possible that there's an issue with exiting that particular emulator. I don't currently have a PS3 setup to test with. If every other emulator is working properly, than that's probably the issue. You can, however, put in your own AutoHotkey script for it under Tools > Manage Emulators > Exit AutoHotkey Script tab. It doesn't look like there's a default AutoHotkey script for exiting RPCS3, so it may just be that one needs to be written.

Setting up Retroarch specifically as a custom emulator probably isn't possible, because it requires some extra data that is unique to Retroarch. What core is missing for Atari Lynx? What cores do you have in the list?

Thank you @Zengobag, I'll get this fixed shortly.

There's an import process available directly on Android now, so you should be able to just delete that platform from LaunchBox on Android, and then just re-import directly on Android after unzipping them.

My best guess is that maybe a plugin is doing this? Do you have any plugins installed?

I actually did that on purpose for the new theme, because it doesn't exactly scroll smoothly due to the dynamic box sizing. It did work previously, it was just fairly jarring and jumpy. I just prefer it this way to avoid that stuff. I maybe should re-enable it though when dynamic box sizing is off (assuming I don't do that already).

Hmm, that image looks stretched; doesn't look like you're actually using an ultrawide monitor. Is there a reason why you want to use this version of the theme? The images in the background on the right are just the backgrounds for the selected game. It uses the background image priorities. So you can tweak them to display whatever you want there.

This is definitely related to having DirectInput wheels hooked up. They were enabled for the 10.11 release. The first option is to simply uncheck "Use All Controllers", and configure LaunchBox and Big Box to use whatever other controller you have set up. Otherwise, you can configure the wheel to combine the pedals in the Logitech interface. From what I hear, there is a way to do that only for LaunchBox and Big Box.

There are separate controller settings for LaunchBox and BIg Box. It sounds like maybe your Big Box bindings for exiting games aren't set up?

I agree that would be nice, but I don't know of a good way to do it, considering the the variety of clear logos out there. The only thing I can think to do would be to adjust brightness or opacity or something like that, and I don't think that would really be a good thing to do. We could throw a star over top of them somehow, but then we'd inevitably end up with it looking awkward or covering up and important part of the logo. So idk.

Ah, good find. Noted.

Games that are favorited are moved to the beginning of the list in Big Box. Have you confirmed that those games are not at the beginning of the list?

Per the first issue, if things are launching successfully in LaunchBox, but not Big Box, then most likely the issues have to do with the startup screens. The first thing I would try is turning off startup screens in Big Box under Options > Game Startup > Enable Startup Screen. Does that fix it?

Just to make sure, @rickz1222, are you on Windows or Android?

We could do an auto-restore from backup, but I can see that being a confusing thing, so we'd have to prompt about it first.

This is not something I've seen or heard of before, so unfortunately it probably comes down to a misbehaving driver, or something of that nature. I'd try updating all drivers (especially video drivers) to see if that makes any difference.

The problem is that I don't have a G920 to test with currently, so if it does happen, it'll probably be a while. I'm not positive, but I suspect that that issue is specific to that setup.

If you're closing it yourself, it may have just been busy. Did that happen at the end of the process?

Thanks, this should also be fixed in beta 13.

Ugh, so this has been a bit of a nightmare. I blame Microsoft. Beta 13 is out now, with yet another round of hopeful fixes for the various connectivity issues. I was finally able to replicate the issues, and they seem to have gone away now, so hopefully this one will do the trick. I really appreciate all the testing, guys. If you can beat this one up as well, I'd be grateful.

@dustdancer Thanks for the report. I've added some code to the latest beta (now beta 12) that adds some extra logging to this so that we can see exactly what's happening here. Can you download the latest beta, turn on debug logging, and then give it another test? You can turn on debug logging under Tools > Options > Debugging. Then you can just PM me the log file that shows up under LaunchBox\Logs. Thanks!

Thanks to @lockian's log that he sent me, I believe I was able to get the issue with EmuMovies fixed. We were using an old EmuMovies DLL that was compiled against .NET 2.0, which apparently has issues on some systems when using TLS (unless there's a certain Windows update installed). I've integrated the code instead so that it all runs on .NET 4.7.2, which should hopefully fix that particular issue. I do still have a report from @dustdancer, however, that beta 9 broke Steam imports, which I also need to figure out. Details here: