Jason Carr

Yes, that is expected. LaunchBox can't run without the necessary libraries.

Ah, so a multi-binding is probably causing issues. You can try resetting it by deleting the LaunchBox\Data\InputBindings.xml file. That should reset it to what it was before the update. If that doesn't work, you can actually modify that file in a text editor if you need to.

Can you explain? Are they reset back to defaults after you restart Big Box? What do you mean by not saving? Do they work in LaunchBox?

Hi zombie, try going to your controller settings. Does it work to map things under controller mappings? What does the Tankstick show up as in the controller settings?

Most likely there's an app conflicting or something. There are a lot of things that can try and hijack that guide button, so try closing down any other running apps.

Lol, it's so confusing. Yes, apparently you need a non-merged set in order to pick and choose files, which results in a lot more space being used for the whole set.

No, it wouldn't, because bindings were completely overhauled and use different data in the new version. Can you please just check your bindings?

This is by design. Depending on your set, MAME ROMs require various other files from the set. So there really isn't any other option, unless you specifically have what's called a "merged" set. We may add an option for that later on to the exporter, but I imagine that is likely to cause some significant confusion.

I honestly haven't started on that yet, but it is planned. I have a lot of other stuff to tackle first though.

To be honest it will probably be a while before I get back to making any changes or fixes to the pause screens. As I've stated before, both pause and startup screens are finicky at best, due to the fact that you literally have to fight against Windows to implement them, which is why I held off from tackling them for years. There are compatibility issues with the pause screens for sure, but they are working better than I even thought would be possible at first, so I'm happy with them currently as they stand. Feel free to report issues, but honestly I won't be making any changes to them for quite a while.

Have you checked your controller mappings to make sure that nothing is bound to Exit?

Yes, you can turn it off in the Options screen under Backups.

I finally figured this out, unfortunately shortly after I put out the 10.2 release. It was an issue if you had a space in your LaunchBox folder path. I put out 10.3 to address the issue. Thanks for bringing this to my attention @dbalcar.

Ha, that's pretty cool. We can add that here soon, hopefully.

FYI all, I put out 10.2 this morning and then discovered an issue with the data backups, then quickly put out 10.3. I highly recommend updating to 10.3.

Wow, I have never heard of the Back button on controllers causing crashes for Big Box. Are you sure you don't have it mapped that way somehow, either with a controller mapping in Big Box or an external application? It sounds like there's something wonky going on somewhere. By now with all the beta testing we've done, I'm pretty certain those controller issues are unique one-off issues. It might help to know if you see those same issues in 10.1.

Thank you @Kondorito, got this in for the official release.

This sounds like an issue with the screen resolution changing. That can cause issues, so I would suggest changing the emulator settings to always use the native resolution, if possible. There are several issues here that will need separate troubleshooting. Per Big Box "soft crashing", what does that mean? Also, what Big Box theme are you using? Per the controller issues, I'll need more details on that. What happens when it's randomly not working? Is the ScrollBeginDelay issue a new issue with the betas?

Lol, I've never heard of a Wifi hard drive before...

I'll be improving the exporter in the future to better identify connected files, but that feature will probably never be perfect. If you're looking at bin/cue files though, they should be picked up properly, assuming the bin and the cue are named the same. Regardless, sorry you're disappointed in it.

All it takes to fix that issue is to manually copy your PS1 ROM files over to the correct folder.

What issue specifically are you running into? Any error messages?

The error says it's looking for a Z:\ drive, which I assume was a mapped network drive that you had at least at one point. Most likely you have a game or a platform that points to that Z:\ drive. If it no longer exists, you should find and change that path in your collection. LaunchBox will automatically try and create any missing folders when it looks for files. That's the reason for the error. No, LaunchBox does not write to ROM folders unless you ask it to.

Look at the exact error message you posted. It's trying to create that folder, because something in your collection is referring to it. It's that simple.