Jason Carr

What do you mean by no longer seem to be working? Do you have "Play random game videos for platforms" checked in the Big Box video settings?

An update to the Colorful theme is in the works. We've already solved the issues. The theme should be out soon.

Thanks for the report. I've reverted the release over this, so the official release is now back to 11.12 until we can get that issue fixed. We should have it fixed and have a new release out tomorrow. You're free to stay on 11.13 for now, or you should be able to downgrade to 11.12 by just installing 11.12 over top.

Thank you all. Btw, I have all three translations into beta 7 (actually I think they were in a previous beta as well). We're planning to release on Monday.

We still have never been able to reproduce this, so we're not exactly sure what to do there.

Hi Claudio, for some reason I don't see the upload here.

Hi all, we're nearly ready to release 11.13, so it's that time again. Thank you all so much for your work on the translations. We're hoping to release early next week. @Opak @cyanjiang @Bardock @MajKSA @gamehacker @Kondorito @Nyny77 @alexposad @k_kutsugi @dukeemu @Just001Kim @Cauptain

I'm definitely keeping a close eye on this, and I might buy myself one if it turns out that I truly can install Windows on it and do whatever I want with it. As per running it natively, it's just a flavor of Linux, so it's gonna run into the same issues we've run into previously with Linux. It works, but not nearly as well as on Windows, and developing a native version is kind of a joke (it would take years). That said, also, I'm back to developing on Android, and though we don't plan to ever put it on the Play Store, you can expect a new version of the Android app to be out in a month or two.

Well, it took me a bit to dig through what is and isn't currently possible, but it does appear that Android 11 still does allow you to pretend to be an older application and use the older storage mechanisms. That appears to be what the other frontends are currently doing. There are still some silly restrictions on where and how you can share files (for example, our previous file extraction routines aren't working on Android 11 at all), but I'm grateful that it looks like there are ways to make things work on Android 11. Some of my testing with the other frontends was faulty, so I apologize for that. It does appear that users are able to create a folder in the root of the SD card or internal memory with ROMs and launch them in Retroarch. Back when we stopped development, Google's plans and directions along these lines were up in the air and terribly documented. Unfortunately, they still are. I can't find any information from Google as to when the older storage mechanisms will be completely disabled, or if they'll be available at all in Android 12. So the future feasibility of emulation frontends on Android is still very much at risk, but at least there are ways to keep things working on the current version of Android. Google's penalty for sticking with the older storage mechanisms is that you can't target the latest Android features, but I don't currently see that as a major issue. So, hooray? It looks like we can actually continue developing and releasing on Android, at least for now. However, as we won't be using the Play Store anymore, we do have a significant amount of work and changes to make to our backend systems to support our own purchases, downloads, and updates. But stay tuned.

Hey all, I am considering the possibility of opening LaunchBox for Android back up for development and release. That said, I've done literally only a half hour of research and already I'm running into the same nasty problems that plagued us the first time around: Having to place ROMs in ridiculously deep and ugly folders in order for them to be able to be launched Security issues launching games (Retroarch basically just crashes if Android doesn't allow the launch) Issues with app switching (you can't load up a new ROM in Retroarch if you don't manually close the previous one) Needless to say, my hope to get back into Android development was dampered pretty quickly. It's a real shame, because most of these issues are superficial, but they're also out of our control, and they make for a confusing and lacking experience on Android no matter what we do. If anyone knows of any solutions to these problems though, please let me know. I will say that all three of these issues are still problems in Dig and Reset Collection, so I doubt that they can truly be solved, but I am all ears if you know any solutions. After running the latest versions of the other frontends, I am convinced that there is still plenty of room for improvement. The other frontends still make for a confusing and difficult experience, if nothing else. And with most people having an Android phone that is quite powerful these days, it would certainly be nice if there was a better emulation experience available. Anyways, if we do end up getting back into Android dev, we will probably do it without the Play Store, as our experience was so terrible over there. I'm interested in hearing your thoughts on whether that is a deal breaker for you, and how you personally get around the above issues. Thanks y'all!

@kevin.k Of your screenshots in the first post, the Keyboard one can be changed via KeyboardView.xaml. The others are unfortunately not currently able to be modified. We can fix that for a future release; however, it may not exactly be the highest priority, if I'm honest.

We've put this on our internal list, @James Carden. Hopefully we can get to it soon.

We'd like to announce that @faeran has officially joined our team here at Unbroken Software, LLC! If you've been around long enough, you probably know him from all the themes he's been sharing with the community since 2017. He will now be serving as our Product Manager, and while that title doesn't do justice to all the things he'll be doing behind the scenes, you'll definitely be seeing his presence more and more as he settles. Some of his new roles pertaining to the community will include: Supporting LaunchBox through email, forums and social media Listening to the community and providing feedback to the team Leading the marketing and video creation efforts Helping guide the direction of LaunchBox updates Providing community live streams for theme development Continuing to develop themes for the community Let's all welcome him into the LaunchBox family!

Beta 7 is out now with the following: Fixed: Missing retro achievements leaderboard in Big Box Fixed: Rare error when opening a "Browse Folder" dialog window Fixed: The Add/Edit Game window wasn't always saving image files correctly when two games in a platform had the same title

@megashub Unfortunately, even if it is a bug, there's not likely anything that we'll be able to do to fix it, because we use either VLC or Windows Media Player to play the videos. We do have a general volume control on the videos of course, but obviously it's not getting changed between videos, so if there's a volume discrepancy, there's not really anything we can do about it. Do all the videos play at the same volume when you compare them to the prerecorded videos outside of LaunchBox/Big Box?

Do you have any FLV videos? Several other people lately have noticed VLC having stability issues with FLV videos. Unfortunately themes that really on the eatkinola plugins may not continue working going forward, especially the video plugin, as it was always prone to stability issues.

Beta 6 is out now with several stability fixes and performance improvements for imports and metadata/media downloads. Also resolved several issues with continuing EmuMovies downloads after restarting the app.

Thank you @Kondorito; I have this in for the official, which we're hoping to put out later today.

Beta 4 is out now with the following: Improvement: Double clicking a controller in Manage Controllers will now open the edit screen for that controller Fixed: Controllers weren't showing to add in Bulk Edit Fixed: Removing controllers via the Manage Game Controllers window were not removing controllers Fixed: The metadata scraper was only scraping one controller entry per game even if there were multiple

Thanks @Cauptain, we have it updated for beta 4.

For everyone having issues with EmuMovies downloads, please update to 11.12-beta-3 and let us know if it fixes the issues for you.

Beta 3 is out now with the following: Improvement: Added a "Doesn't Require" comparison for Controller Support with auto-populate playlists Improvement: The "Clearing Image Cache" process at the end of the download metadata process should now be faster (will still heavily utilize the CPU - this is of course by design, might as well utilize that fancy CPU) Fixed: Manage Game Controller's delete button now works Fixed: When finding controllers by platform only the first platform was found Fixed: Threading error caused by wizards Fixed: When adding a playlist and selected "Auto-Populate" the grid was populating with the current playlist/category name as a platform filter Fixed: Potential batch EmuMovies media download issues (introduced in 11.11)