Jason Carr

Hello all, I just uploaded version 0.26 in beta form to the Play Store. Hopefully it will go live quickly here. I've been working on an import process that runs directly on the Android device (instead of requiring an export from the desktop app) for weeks now, and this is the result. I'm releasing this in beta form first, because it's such a big release. The only other new thing with this release is the fact that the app should now work on Intel x86 and x64 devices as well (instead of just arm and arm64). In order to use the betas, you'll need to opt-in to the beta releases here: https://play.google.com/apps/testing/com.unbrokensoftware.launchbox Once you've opted in, you should be able to able to update to the beta version on your Android device. Please keep in mind that if you opt-in to the betas, you won't be able to leave a public review of the app (and we can use them if you're willing). You have to use the same link to opt out of the betas before you'll be able to leave a public review. Any testing you guys can do on the new import process (or anywhere else) would be much appreciated.

Actually, the reason why this is an issue in the first place is in order to allow multiple users to control Big Box at once. The issue is just a side effect of the fact that we don't currently differentiate between different controllers when taking inputs. We have this issue on our list.

Hi @mariano2860, this is a known issue. I assume you're using two different XInput controllers (360 or Xbone or compatible). The controller code currently doesn't differentiate between them in that case, so that is why. It's not a major focus for us, but we do have an item on our list for it.

Hmm, I'm not sure why a playlist would lose those settings; I haven't seen that situation before. I'll keep an eye out though. Thanks @RULLUR. Yeah, this is just Windows. There's unfortunately not anything we can do about it.

Good to hear guys. I'm pretty sure the issue comes from using different DPIs on your various monitors. Windows still does not handle that well without jumping through a bunch of additional hoops.

There should be a new "Games Missing Media" option available in the side bar filter type drop down.

I see. Steam is not known to cause any issues, no, but that is certainly a clue. It may be controller-related somehow. Maybe try disabling controllers in LaunchBox and/or Big Box, and disabling Steam's various controller features as well.

You can do this relatively easily by just using Arrange By Platform.

Unfortunately I think currently you would need a plugin for this. The plugin would have to get all the available screenshots, and then show two of them. I don't think there's a way to do it otherwise, though I could be wrong.

Hmm, well...I'm running out of ideas. But I guess the next thing to try would be to install LaunchBox to a new folder fresh (just run the installer again and choose a different folder than your existing install). Add a game quick and see if you still have the same problem with Big Box. That would help us to pinpoint whether it's an issue with your data, or somehow an issue with Big Box on your system.

Beta 2 is out now guys with the following: New Feature: You can now filter your library in LaunchBox based on missing media. In the sidebar drop down select "Games Missing Media" and then pick the appropriate media type. New Feature: You can now manually check for updates in LaunchBox under Help > Check for Updates Improvement: When using the Steam Import Wizard it now orders your found games by the game's name instead of by the Steam ID Fixed: Steam trailers were not always downloading correctly using the "Download Media" tool Fixed: In some cases the background music was not resuming properly when returning to Big Box after using the pause screen I'm still working on the on-Android import process as well, but it's very close now and I expect to release a beta of it this week. Thanks to @CBeatt13 for the above work.

Hi @RULLUR, I'm not really following this. Can you re-explain?

Okay, yeah, I can't explain that from those specs and games. It sounds like there's something going wrong. Usually when this happens it's some kind of a conflict without another app that's running in the background (usually poorly-written anti-virus or anti-malware software). Try closing down everything you have running in the background to see if that fixes the issue.

No, Big Box certainly should not take 10 minutes to start (assuming that's what you meant). What hardware are you using? how many games do you have in your collection?

Most likely the ROM file paths are wrong. Edit the games and check the ROM file path field.

Commenting here just to let you know I'm tracking this thread @salmistaabel. Retro is on the right track; let us know the answers to his questions.

LaunchBox sees them as separate controllers as well, of course. Always has. But there's no way to map controllers differently between them currently in LaunchBox. Which, I suppose, in most cases is fine, because it just means that player 2 will have the same controls as player 1. But if you want it to work differently, that's not currently supported.

The LaunchBox code doesn't do anything with F9, F10, or K, unless you bind to those keys. So I'm still confused as to what's going on here.

I see. It's still the same issue. LaunchBox and Big Box don't currently make any distinction between inputs from different controllers, and we'd have to make significant changes to the interface and the backend to support that. Is there a reason why the controllers need to act as game controllers and not keyboard-based devices?

Hmm, not sure why that would be slow for you from there. I'm in CA and speeds are fine for me, but the Internet is a fickle beast sometimes, especially now that net neutrality was abolished here in the US. Worst case scenario, you can try using a VPN service; that will get around any throttling that your ISP happens to be doing (and yes, I'm pretty sure that our servers are sometimes throttled these days).

Hi corvus, I'll see if I can't add Dolphin MMJ here soon. I know I've successfully run Dreamcast games in the past using Reicast and Redream, so I'm not sure what the issue might be there. Have you tried Redream? Are you running the latest version of Reicast?

Galaxy S10+ is a wonderful phone both for emulation and other use; I own it myself. The only drawback is the price. I'm not very familiar with the Razer Phone 2, however. If you're coming from iOS though, I would recommend sticking with Samsung as it's the best "it just works" version of Android available, IMO.

Am I understanding correctly that you have a controller board that basically acts like two separate game controllers? Assuming that is correct, I think the only way we would be able to manage something like that is to add controller-specific bindings to each option. That's possible, but it would be a fairly significant new feature to add.

@kidshoalin That kind of crap talk isn't allowed here. It's unnecessary, useless, and offensive. Next time you'll get banned.

There's really only a few other things that could cause stuff like that, crashes/power failures/reboots, faulty hardware, or a corrupted file system. You might want to run chkdsk first to see if you have any file system issues.