faeran

Glad you like it! Since the theme wasn't intended to include "media" image code, what you'd have to do is open your preferred view's xaml file and add the disc image code into it. Our most up-to-date Big Box theming guide is found over on our strategy guide: https://feedback.launchbox.gg/help

CinemaBox - A Simple Movie Importer Plugin View File I had a day to spare on the weekend and wanted to try my hand at a LaunchBox plugin. This is the result. I don't plan to actively develop it too much moving forward, as this was very much a weekend hobby experiment project. Still, it works, and I figured I would share it in case it is useful to someone. Requirement: LaunchBox 13.26 or higher What does this do? It's currently a movie importer plus metadata and artwork scraper. It is designed for people who already have a local movie collection organized for apps like Plex, Jellyfin, or Emby. It imports that folder into LaunchBox with minimal fuss. It also downloads and configures MPV so movies can launch cleanly as an "emulator", and be used with a controller. Metadata and artwork provided by TheTVDB. Installation Close LaunchBox Download the 7z archive Unblock the archive in Windows if needed (Right click > Properties > Unblock) Extract it into your LaunchBox Plugins folder Your structure should end up like this: LaunchBox\Plugins\CinemaBox\CinemaBox.dll LaunchBox\Plugins\CinemaBox\CinemaBox.deps.json How to use Tools > CinemaBox Runs the import and downloads and configures MPV. Right click a movie > CinemaBox > Change Match (TVDB) Rematch the movie and re download metadata and artwork. Right click a movie > CinemaBox > Media Download (Replace Artwork) Grab alternate artwork. A few things to be aware of: Matching is based on folder and file names. If your naming is messy, results may be messy. If TheTVDB changes their API, this plugin can break. Heavy scraping could potentially hit API rate limits. MPV configuration is basic and meant to “just work”. If something breaks, feel free to post about it. I'll be checking in every now and then, and may be able to fix it. Uninstall Close LaunchBox Delete the folder: LaunchBox\Plugins\CinemaBox Submitter faeran Submitted 03/02/2026 Category Third-party Apps and Plugins  

Something like this:

Make sure you also have Theme Specific setting also turned off. I think it's possible to turn that setting off globally but not off for RetroTastic's theme specific options. If that still doesn't work, then you may need to clear your cache. You can see my test here worked fine.

The theme is done at this stage, but the code is out there for anyone wanting to pick up the mantle. Pretty sure the theme just uses the normal "main image" transition code, which means that what you are seeing isn't an image, but the actual 3D Model of the game box, which means you could map some buttons to rotate the box and you can rotate it from that view. You should be able to turn off 3D Models there by going into Options > Game Details > Use 3D Models for Box Images

LaunchBox for Android 1.22 Beta thread has opened:

Hi Everyone, A new beta round has begin for Android for version 1.22. The first beta is out and introduces a powerful new Security system, visual theme update indicators, improved library optimization behavior, and an important scoped storage fix. While the changelog is fairly straightforward, we would really appreciate focused testing, especially around the new Security system. Testers: Things to Focus On Please help us validate the following: Security System: Enable Security under Options > Security, lock multiple features, attempt editing, deleting, importing, emulator management, and platform options. Restart the app and reboot your device to confirm restrictions persist. Test while using LaunchBox as your home launcher as well. Theme Update Indicators: Confirm the green badge appears in Manage Themes and next to individual themes when updates are available. Update a theme and confirm the badge disappears and remains accurate after restart. Scoped Storage Fix: While using LaunchBox as your home launcher, attempt to set or change a Scoped Storage path and confirm it saves and functions correctly. Beta 1 Changelog Added a new Security system that lets you lock down platform and game management features behind a PIN, with extensive configuration options available under Options > Security Added a visual update indicator for themes, showing a green badge on the Manage Themes menu item and next to individual themes when updates are availableUpdated Optimize Library behavior so star ratings across your entire library now refresh automatically when running an Update Library scan Fixed an issue that prevented setting a Scoped Storage path when the app was running as a homescreen launcher Thank you for helping us refine LaunchBox for Android. Your testing and feedback continue to make the app better with every beta.

What you can do instead is drop the bat files into LaunchBox, and then choose the option: None of the Above Since you are not importing ROMs that's the option you'll want to use, then you won't have to choose an emulator.

We've talked extensively internally about upgrading our internal tools and infrastructure, but always delay it due to time investment and the very real risk of breaking what we already have set up and working for the last decade. If we spin up another project, we most definitely will take advantage of a more modern approach, although it will be more to help us, and less about public perception. Not really sure it matters, but we needed to fix a problem with our import wizards locking only to find out we already fixed it internally in a branch that also contained the FB Neo import. It would have taken just as much, if not more time to decouple the two and test them separately than it would to just test what was already there and working, so hence, new feature The next beta cycle will start soon enough as we already have branches in the code review / internal testing phases, so expect a new beta thread in the next week or so. I'll close this one down for now until then. Thanks everyone for the help with beta testing this release.

As we mentioned from the beginning of this cycle, this was a quick hotfix release cycle to address some of the major issues that showed up with 13.25. We'll have some communication shortly about the hotfix release in a number of places. For the most part, Beta 2 is what the hotfix turned into, and we've already started the next release cycle internally. Yes, you will end up having issues if you are 7zipping games like that. Instead, I would look into compression alternatives. Ask someone on the forums for emulator specific compression alternatives that don't require decompression to run, there's most usually a solution. Also note that RetroAchievement scanning will not take place for Platforms that RetroAchievements does not support. Sounds like you've had a string of bad luck, which we apologize for. We were unable to duplicate any of the music issues you are having. We've actually specifically addressed a number of them within this hotfix release. For any other issues you may have, it's best to both ask on the forums if there are any simple solutions you may be missing, or report a bug using the above menu under HELP & SUPPORT > REPORT A BUG Each report should have thing you deem a bug, and you'll want to provide as much information as you possibly can. For any crash related items make sure to include a crash report, along with exact reproduction steps, including plugins, themes, views you use, features you were using, those kinds of things. Include at least your Settings files, or your entire Data folder. The more information, the better we can see if there's something in our code base that we need to address, or if it's something else we can help you with.

Make sure to turn it on under Options > Show Playlist Filters

Make sure you are also setting the Scrape As value to Arcade. Those are the two rules in order to see the fbneo import page at the end of the import wizard. We'll have a write up once this goes live, and we will also look to expand this logic to include the emulators as well in future updates.

We haven't been able to recreate this, and RetroArch code hasn't been touched in a very long time, so my guess is that the issue is fairly internal to your location unfortunately, for whatever reason. If you are referring to LaunchBox, the default is Box Fronts, so it would be strange for it to suddenly change randomly. I don't believe there's any code that allows the change globally like that (it's always possible a plugin could introduce that kind of functionality). This would be best to troubleshoot in another thread. The way FinalBurn Neo import currently works is that you'd have to import a platform that has a name similar enough to FinalBurn Neo, then you'll see it. In the future, I could see a benefit to opening this up to take into consideration the emulator's exe, and core for people that use RetroArch, although that won't happen for this hotfix. Let us know if naming the platform properly works for you. Thanks. Looks like it's the "RotationAmount" property. We will look into this before the hotfix drops. What we would need from anyone experiencing any kind of crash for either LaunchBox or Big Box for us to take a look: Any Crash Reports that LaunchBox or Big Box provides Any Crash Reports found in Event Viewer specific to the crash that also are .NET crashes (there may be multiple per crash) The Settings.xml and BigBoxSettings.xml files would also be super helpful, as long as they are in the exact state that makes you crash Then, click on HELP & SUPPORT in the menu above, and choose REPORT A BUG, and send us a full report of exactly what is happening at the time of the crash, along with all the above. We utilize RA Hasher, the official hashing tool from RetroAchievements, which as far as I know, doesn't allow you to read bits flowing through RAM to gain the hash that it needs. If they ever get support for that, we can look into supporting it. RA Hasher doesn't have support to read the contents of a 7zip file to obtain the hash (hence the need to extract), but it does have support for zip. So, from a user's perspective, the better format to store your small ROM files is either uncompressed entirely, or within a zip, if RetroAchievements is important to you.

Thanks, that trail will lead you to the answer. What you got was the same issue when you were on beta 1. The fix was applied to beta 2

Read the first post, it should explain it to you. Also, there's currently no server issue. Not sure why it crawls from where you are. You won't get the full speed, but it's usually enough to download in a few minutes.

Beta 2 is out with the following: Improved: Optimized music playback in LaunchBox to run off the main thread and reuse the same VLC session, improving overall performance and playback stability Improved: Addressed multiple reported issues related to music playback reliability and session management Fixed: Background music no longer restarts or skips the current track when the screensaver activates Fixed: Platform videos in LaunchBox now stop playing correctly when the platform details pane is closed Fixed: Restored video playback on Platform Hybrid views where videos were previously not playing Fixed: The Play Video Audio with Background Music option can now be toggled independently from the Prioritize Soundtrack Music setting, allowing both options to work as expected Fixed: Resolved an index out of range error that could occur during automatic ROM imports in rare empty list scenarios The first post and in app explains more of how you can help test the changes in this beta. Thanks all.

Not to linger on it, but it was essentially just a flip of a setting that then caused some users not to see that an update was available in some scenarios. That was essentially it. Early adopters of 13.25 would have potentially seen this in their build. In all cases there were ways around not getting the notification, which most people here found, with a few others ways as well that weren't mentioned.

It's actually an issue with 13.25 (can't be a problem with the beta when you haven't even installed it yet :P). There was a short time where 13.25 had that issue but it has been since fixed.

When I mentioned Arcade platform. It's less about lumping everything into an Arcade platform, and more about utilizing "Scrape As: Arcade" and the logic built behind that, which then attempted to answer your first question. As far as Media Packs are concerned, that's just us thinking ahead so we are prepared with some default custom platform names for users.

Well, for your example, RetroArch should already be able to play a Sega Master System game without the need to extract the file, so in that scenario, it may be a bit redundant to use LaunchBox's extraction method there (depending on core used.) Most small ROM based cores can handle playing without extracting 7z and zip, where disc based systems, almost all of them have their own compression format that they support these days that can be read without the need for extraction, which , together, all becomes a lot better for your hard drive in the long run as well. Anyway, in order for this to work, we'd have to basically follow what RetroArch is trying to do. So if a user is using the Content Directory setting for save files and they have made the choice to utilize a region folder like \\Sega Master System\USA\, then RetroArch will place your save files inside of a USA folder, and ignore Sega Master System entirely. We would need to match this to have our feature make any sense.

Well, let's look at it slightly differently. Remember that TeknoParrot is not a platform. The platform is Arcade, which has its own file parsing logic streams that have yet to make their way to our auto-import feature. This is why TeknoParrot, which requires a scrape as value of Arcade, won't work via the auto-import system right now. So, yes, it's currently a limitation by design. I could see it being one of the easier ones to get working though, so it's never out of the question, where once a user has added a TeknoParrot emulator, we can deduce where the xml files should be and allow auto-imports for platforms that match or are close to the name TeknoParrot. As long as people don't drastically mis-spell or decide to name their platform something funky, it should, in theory, work. Although, the names of the xml files would also be super important to find a GamesDB match properly.

Did you manage to get it to download? Nothing on our side indicates that anything is wrong there. Thanks for the report. Both are fixed internally and should be part of beta 2. Thanks for the report. I believe it's worked like this for a very long time (like over half a decade or longer). So, while this won't make the hotfix, it's probably about time we take another look at this to smooth out the edges that may have been introduced since its implementation. I'll see about remembering to go through that entire pipeline early in the next beta cycle to see if there's some easy wins here.

This part is actually working "as intended", in that there was no effort to filter down search results like this in hybrid views. I'll see what it would take, but it would be a new effort, so I'm not sure where in line it will get placed. As far as switching to the TextGamesView, that's by design. The PlatformHybridView is a Platform view with a game list tacked on (not the other way around), which means, that the only true Game view in that theme is the TextGamesView, which Search results requires to utilize.

Thanks guys. Fixed internally, should be in beta 2.