Jason Carr

Beta 2 is out now with the following: New Feature: For Steam games, LaunchBox will pull down Steam's play times instead of manually tracking them; they're updated on imports, metadata updates, and after playing New Feature: GOG achievements are now available in both LaunchBox and Big Box! They can be viewed in the game details sidebar and via a popup from the game details menu in Big Box. Improvement: Added on the fly filters for MAME High Score Support, Status, and Custom Fields Improvement: Added Play Time arrange by Improvement: Added Play Time column to LaunchBox ListView Fixed: Could not add a space at the end of the default command line in the Add/Edit Emulator window (introduced in 12.0) We will look into any remaining issues next week. Thanks for testing, guys.

It will have the same or a similar feel to the Android port, but the Android port will feel more and more like Big Box on the desktop as time goes on. We are definitely planning to focus more on Raspberry Pi/single board/portables though than on the classic desktop. There are many, many more users with Linux on those types of devices than users who use Linux on the desktop, by a mile.

@Just_a_Guy Thanks very much for the support. We can definitely still get you a refund though if you'd like.

Good to know, I'll put this on my list to add the Swanstation core.

Thanks @JsARCLIGHT; this is on our list. Yes, I agree that I think it is probably video related. We are looking into it.

Did you purchase an Android license specifically?

I'm guessing this was just the placebo effect. We've done extensive testing and there is no difference (in performance or in code) between early versions and the latest versions in the single game media downloads.

Unbroken.LaunchBox.Wpf is an old DLL file that no longer exists. It was replaced by Unbroken.LaunchBox.Windows. So you might be able to fix the issue by adding a reference to that DLL file.

I'm not sure if I'm fully understanding the issue, or exactly what's happening. Would you be able to take a screenshot or a video of it? Per the cache, you can always clear the entire Big Box cache in the options menu. There are several options to clear. Or, you can just delete the entire LaunchBox\Images\Cache-BB folder.

We'll definitely be adding that functionality here soon (screenshots). Good to know.

Thanks, will take a look.

Unfortunately most likely this is probably somehow related to data corruption, especially if it all started happening from a force close. You could try restoring your oldest backup from the LaunchBox\Backups folder to see if that helps (if you haven't tried that already). Otherwise, the first step would be enabling Debug Logging under Tools > Options > General > Debugging in LaunchBox. That might give us a clue as to what's going on. The logs will then be located under LaunchBox\Logs. If that doesn't help, it will probably need to be trial and error, trying to move data files out of the Data folder until we figure out the culprit.

What devices are you using? Just tested this and haven't been able to reproduce the issue with 0.42.

We can look into Pizza Boy Pro to see if maybe something broke with an update. We do already have unzip support. It's an option in the emulator settings. We're working on videos right now. However, I don't have a specific time frame.

Yes, that's the gist of it.

I'm a little baffled on this, because this issue doesn't appear to be happening to anyone else. If I recall correctly, we do have other users who are using the GPD XP. I don't currently have one to test with though. All I can figure is that maybe it could be a BlueTooth connectivity issue? Do the controllers connect via BlueTooth?

Appreciated. We honestly haven't made any decisions on pricing yet, or whether it will be under the same license as Android. It will probably depend on how much additional development is required for the Linux version, which we're not fully clear on yet.

I hear you. I am looking into it. I would appreciate if you could stop jumping to ultimate conclusions, though. None of this is as simple as what you're suggesting, unfortunately.

Thank you @Soomin papa! I'll get these files into the next beta that we put out.

Yes, the fragmented ecosystem on Android is an absolute mess, especially right now with Google hell-bent on breaking as much as possible in the name of "security". This was the original reason why left the Android platform half a year ago (or one of the biggest ones). That said, we are committed to developing and improving it going forward, even if Google continues to cause problems. We may not be able to always make LaunchBox for Android work with every single emulator all of the time (after all, none of the frontends on Android can), but we will do our best. Remember that RetroArch is a saving grace here; it generally works great for most platforms, and there are no issues with it, so if all else fails, use RetroArch (at least in the mean time while we navigate the muddy waters that Google has created).

Hey all, I talked to @circo at EmuMovies last night and confirmed that it's not a LaunchBox bug. They're in the middle of some server upgrades that should hopefully help the situation. What we are working on for the moment is a way to make it so that extended wait times while searching for EmuMovies media can be easily cancelled so that you don't have to wait (in the manual download media process for single games). We should have that out in beta form soon.

I will be looking into this. I'm not sure how feasible any of it is, but it's on my list.

Sure, for now you should be able to fix the issue by removing the "-1" at the end of all of the file names. It is true that the importer on Android is not quite as "smart" as the importer on Windows. It's very close, but not quite. Even still, you'll probably get better scanning even on Windows if you don't have extraneous junk at the end of file names.

Sorry for the late reply here. We're not aware of any issues with EmuMovies downloads in 12.3 (or 12.4, which recently came out). Assuming you're still seeing these issues, can you turn on Debug Logging under Tools > Options > Debugging in LaunchBox? Then you can try downloading some and share the most recent log file with us from your LaunchBox\Logs folder.