Jason Carr

Sure, I'll move it. I sent it to my web host, and they're asking for your IP address with your host. If you wouldn't mind sending that my way, I'd appreciate it. You can PM it to me for security reasons if you'd rather. They're also asking for the results of an MTR, but that doesn't really look easy to run.

That's interesting, thanks. I'll forward that to my provider in case there's something they can do. I don't have that 109.236.95.179 IP in my trace routes at all, but it's close to one I do have, so they may have a routing issue.

That is pretty messed up, and disappointing to hear. What type of ISP are they? Cable, DSL? Can you run a traceroute for me? Go to the command prompt in Windows and type this command: tracert www.launchbox-app.com If you can copy/paste the output from that here, that might help us get to the bottom of it.

Yikes, I have not heard of any ISPs completely blocking us, no. That's not a good thing to hear though. Who is your ISP?

Unfortunately I don't think this exists currently. Of course users can turn the setting off, but that setting is currently not theme-specific.

The only other thing that I can think of here would be a faulty controller. I have seen this in the past with other users of the Shield, and the reason why it wasn't an issue with other apps was because we are using the right stick for navigation. I have the exact same setup and can't replicate it otherwise, so I am fairly certain it's not an issue with the app itself. You might try swapping controllers between the two Shields to see if that is actually the issue, or disconnecting your Shield controller and using an Xbox One controller. I think we may have a bug that I haven't yet followed up on where the setting doesn't load up properly when you open the emulator settings screen. If you open the screen, turn it off, and then back out, it should at least save it until you open up the emulator settings again. I've been thinking about this lately as well. Don't have a solution for it currently, but it is on my radar.

No, you won't lose anything. Just make sure you install it to your LaunchBox folder, and not a subfolder of your LaunchBox folder, because the setup makes that slightly confusing.

You could, but honestly at this point it may be best to just manually install the 10.10 version from the website, and see if you still have trouble going forward. I don't recall any updating issues with previous versions, but we should probably rule that out.

It's hard to say what could be causing it then. Maybe a firewall issue? Do you get prompted on startup if you turn off background updates?

Hi Jurgen, do you have an expired license by chance? Are you licensed with the premium version? Newer versions do have an option to check for updates. Worst case scenario, you can always just download the latest version from the site and install over top of your existing folder, and all should work fine. However, if you have an expired license, that would cause your license to stop working, so it would revert to the free version.

Have you searched the platform XML for the missing games? That would be a big clue, whether they're in the XML or not.

Okay. I still can't reproduce. Just ran a few tests for SNES, default platform name, and nothing was missing. What ROM set specifically are you using? Are you importing any media? What happens if you turn off all media on import? That would help us to narrow down if maybe it's a media issue.

My first hunch here is that maybe it's combining games incorrectly? @neil9000 I assume you left the "Combine Games with Matching Titles" option checked? What happens if you uncheck that box and run your original test?

@e2zippo Generally this happens when something else is focused during the Big Box startup process. But between different systems, setups, and drivers, it could be anything. Windows focus stuff is a very complicated beast these days, and Windows purposefully tries to remove that control from app developers, so there's probably not a lot we can do to fix that particular issue. At least it's easy enough to fix just with an Alt+Tab. It shouldn't need a restart, but it does need to update the background. So it should work to just click on a new game with a different background. Pretty much all of this is related to the startup and/or pause screens, which have always been hacks, because that's straight up the only way to implement them (unfortunately they fly in the face of how Windows wants apps to work). On most systems all these features work fine, but there are still some systems that have occasional trouble. In that case, unfortunately your best option is to just disable the startup or pause screens, or try updating drivers, as it's often caused by driver issues. I wish I had a better solution for this, but there really isn't one. We held off on implementing startup and pause screens for ages for this very reason, but eventually went ahead with them due to user demands. There really aren't any better solutions out there for those features, so we did the best that we could.

@viking Are these new changes to your theme? Or is this the same code that's always been in the Colorful theme? I ask because I haven't seen any of those issues with it myself. You could try taking out the TransitionSelector property of the TransitionPresenter (which would remove the transition) to see if that helps. Beyond that, I'm not coming up with any other ideas. Unfortunately it could just be a performance issue with XAML just from trying to do too much all at one time.

Unfortunately it sounds like there's something else, unrelated to this thread, going on here. The above issues are no longer a thing. Most likely it's faulty drivers or something of that nature, which unfortunately makes the issue difficult to resolve. It's also possible that you have an app running in the background that is poorly written and conflicting with LaunchBox/Big Box. So the first thing I would try is closing all background processes/apps via Task Manager to see if that helps, and then look for driver updates.

Thanks all. I have these translations all updated. Going to put out the official release here shortly.

I don't have a complete list anywhere, but each platform will list compatible emulators that work with that platform. Yes, the desktop export process will only export one system at a time, and removes things that were previously in the export folder. You can just copy the exported folder over to your device before exporting again. Otherwise, the on-Android importer works well now as well. I just tested 0.33 on my Shield TV with a couple different controllers and I'm not seeing that issue. Maybe there's a stray connected controller somewhere that's forcing the navigation down? Check any connected devices and check for BlueTooth devices that could be causing the issue.

If the Clean Up Media tool finds duplicate files, there's no reason at all to review them. It means that the files are 100% exactly the same, so there's literally no reason to keep both of them, or pick and choose which one to keep. Reviewing is really only going to helpful for peace of mind, or if you happen to be using the LaunchBox image folders for another frontend and want to make sure that you're not removing anything that affects anything else.

The update should be live now.

Just started a new thread with the 0.33 release here:

I just uploaded version 0.33 to the Play Store with the following: Added support for over 50 new emulators! Custom emulators are now supported, if you have the correct metadata for them (package name, activity name, and ROM path key) Fixed issues with imports on a few platforms with incorrect platform names that don't exist on the LaunchBox Games Database Added the Sammy Atomiswave platform Some of these were already in the 0.32 release, but 0.32 was only released to beta. Thanks to the community we've found and fixed some bugs in the 0.32 release, so 0.33 is going out to everyone with the fixes in place, as well as a new Sammy Atomiswave platform. As always, it's not available quite yet because Google takes a few hours to make the update live. I'll update this thread when it goes live in a few hours.

Yeah, that's worth a shot. Otherwise, you can try completely uninstalling/removing .NET 4.8. I have unfortunately seen rare situations where the .NET Framework is corrupt and the repair tool doesn't fix it. Hopefully uninstalling and reinstalling will fix the issue.

See my post just above yours...

By chance, do you know what the launching parameters need to be for NES? I have them for GBA and GB/GBC, but not for NES. Thought you might be the developer, so I figured it was worth asking.