faeran

Currently, there are two ways you can find out what was imported. You can go to All Games and Arrange By > Date Added. Or you can Audit all your games and sort by Date Added.

The only reason you would see something like this happen is if the LaunchBox folder that contains all of your data files is not in the location it was expecting. By default, LaunchBox saves all of its files into the user/root of your device just in a folder called LaunchBox. Everything LaunchBox needs to see your library and all of your settings is saved inside of that folder. Some people move that folder onto an SD Card or something similar. If you can find where your folder was originally located, it's possible it's still there with your entire library, and all you have to do is go into LaunchBox's options, click on Data Folder, and repoint to that LaunchBox folder.

Can you be more specific about the games being added?

Good to hear. Although also bad, since Default Plus is one of my themes. I'll have to review the code at some point.

We just triple checked the PS3 scanning, but was unable to get this to happen on our end across a few PCs. They are always importing correctly. I'm assuming something is different in the way you have them imported. Can you toss me your data files in a PM for us to take a look. Can you be more specific about a handful of games and their platforms? I'm guessing a theme issue. Can you test that theory by switching to the default theme and see if you still get it as often. EGS is changing their login stuff again. We've identified what they did this time and we have it fixed internally. It'll be part of the next beta, which should be out today. Not for this round, but it's possible we may provide a management window in the future that may provide some advanced functionality like this.

We missed a check with ScummVM, which has been fixed, but it was intended not to work from the start. MS-DOS will not work unless they were imported like ROMs, and PS3 will work the same way as our current ROM Importer. If anyone finds a platform in their testing that may not be working ideally, we'd love to hear about it.

Not at the moment. We beta'd the idea in the past, and it brought up issues for some users that made the app unusable. We have it on our list to revisit this in the future.

This is still working as-intended, where exporting a MAME set will always copy the entire folder of ROMs to make sure games work while on the other side. My previous post lists some of the challenges with it. I'm not sure when this will get reviewed to see if there's a possibility to add in something specific for users that are using non-merged sets.

It would be helpful if you could confirm the following about some entries: Was the file located within one of your Game Folders? Game Folder meaning the folder that appears under the Folders tab within an Edit Platform window. Was the file not already imported into your library? Based on what you are saying it sounds like you have duplicate files within your game folders that you didn't initially import, and now the auto-import is scanning those folders, finding those extra files and importing them, which would be the feature working as intended, but this would be good to confirm from anyone that has had games imported that may at first not know why.

Beta 2 is out with a few fixes based on your feedback so far. Changelog: Fixed: The ROM Auto-import feature will no longer monitor platforms with a "Scrape As" value of ScummVM Fixed: Changing a game's emulator from the Edit Game window causing a crash Fixed: Rare dictionary error on LaunchBox startup

For the auto-import feature, not at the moment. In the future, we may introduce a management system where users can better fine-tune certain aspects of this. I believe it will scan items within one sub-folder, although best practice would be to keep your ROM folders clean. Are you guys able to filter by all your games and arrange by Date Added. That should give you some clarity as to the files that were added. Some examples would be helpful to determine if the files were within one of your game folders and were not yet imported.

This does appear to be a potential bug, so we'll add it to our list to take a look. The bug being that if you remove an Image Type from any Image Group, and then you set an Image Group Media Limit during a metadata and media download process, LaunchBox will not download an image for that image type. However, just note that if you remove an Image Type from any Image Group, it would limit the ability to view that image type inside of LaunchBox and Big Box.

We will be taking a look at this to see what we can do about it before next release. We haven't made any changes to the Epic Games login code, so we can only assume Epic is undergoing another change to their system.

It's a first time use prompt that informs existing users that update from a build below 13.12 that if they were to use the feature, some games were found and can be imported automatically. It will only happen once, and never again once you see the prompt. It will not continue to scan your folders. However, test it out and let us know if it does prompt you again, as it should not.

This means it's working as intended. You would only see that prompt if the setting was off by default. For existing users we included this prompt to indicate to them that the feature found some games within one of your game folders and it allows you to quickly turn on the feature if you wish. It's a prompt that you would only see once per build.

The LaunchBox 13.12 beta thread has been opened, and can be followed here:

Hi Everyone, The first beta for LaunchBox 13.12 has been released. The big new feature is the introduction of an automatic ROM import system. At its core it's essentially two pieces. The first piece allows us to scan your game folders for any file changes within. Game folders are set on a platform level, and can be found in your Edit Platform section, under the Folders tab. If we notice any new files on startup within those folders, you'll see us automatically import those ROMs. We also keep an active monitor on those folders while LaunchBox is open, and if we notice any new files, we will start the import process immediately. The process will import the games, download metadata, and import a small subset of media. The second piece allows you to place ROMs into the LaunchBox\Games folder. While the feature is enabled, you'll find folders for platforms in there. Place ROMs inside of any of those folders, and we will automatically import those ROMs based on the rules of the first piece of this feature. If new platforms are imported via this method that don't already have a default emulator, you will be asked to set one up when you try and launch a game. For existing users this feature will be off by default. For new users, it will be on. The toggle for this feature will be found under Tools > Options > General > Automated Imports We've also begun an overhaul of our search in both LaunchBox and Big Box. It will now search by title (and alt title) by default, with the ability to add filter switches into the mix (eg. genre: adventure). The default theme has a small hint popup that shows the available filter switches (the popup is fully themeable so any theme dev can add it to their theme). These are big changes to core functionality of the app, so any help with beta testing them is much appreciated. As always, below will list the full changelog for this beta cycle. Beta 1: New Feature: LaunchBox can now automatically import ROM files that are placed inside of a platform folder located in LaunchBox\Games. To enable it for existing LaunchBox installations, go to Tools > Options > General > Automated Imports New Feature: LaunchBox will now actively monitor your platform Game folder (found in the Edit Platform window) and import any new ROM files it finds automatically while the program is open and during startup. To enable it for existing LaunchBox installations, go to Tools > Options > General > Automated Imports New Feature: LaunchBox and Big Box's search has now been upgraded. It will now search by title (and alternate title) by default, with advanced options to search for other types of metadata. Improvement: A dynamic list for Games with Achievements has been added to the Games Discovery Center Improvement: The MAME Arcade Full Set Wizard file requirement has been reduced to accommodate HBMAME full sets Improvement: Support for PICO-8 game files has been added into our import processes Improvement: Clear Logos and Icons have been added for the following platforms: PICO-8, Microsoft Series X/S, VTech V.Smile Improvement: RAHasher has been updated to version 1.7 Improvement: The Scan for Added ROMs tool will now import new versions of games you already have in your library Beta 2: Fixed: The ROM Auto-import feature will no longer monitor platforms with a "Scrape As" value of ScummVM Fixed: Changing a game's emulator from the Edit Game window causing a crash Fixed: Rare dictionary error on LaunchBox startup Beta 3: Improvement: Added logic to improve the ability to import SNES MSU-1 ROMs Improvement: A limited file extension blacklist was added to the auto-scan process to help with some common file types Improvement: The auto-scan ROM import notification now includes an action button that directly opens a window displaying the list of imported ROMs. Additionally, imported ROMs are saved within your log files (if enabled). Fixed: Potential issue with adding new platforms to LaunchBox using the ROM auto-import feature Fixed: Problem where Image Types weren't downloaded when removed from all Image Groups while the Media Limit option was enabled Fixed: RAHasher 1.7 has been replaced with its x86 counterpart to remove debug dependencies that the x64 version incorrectly included Fixed: Javascript error that some users encountered during the Epic Games login process Beta 4: Fixed: The auto-import feature unintentionally being used for games that fall under one of the Arcade platforms Fixed: Epic Games Store login will now work with SSO services like Google

Tbh, I'm not entirely sure. Maybe someone familiar with this core could answer this better. RetroArch, and a bunch of emulators will automatically provide some kind of default controller profile that should just work out of the box, but if not, you'd have to go into each emulator you've decided to use and set the controller at least once. I'm not sure. I know some ROMs require CHD files in order to run properly, make sure you have them in the right place. Graphic glitching would be an emulator issue that you may want to bring up to the community for the emulator in question.

We will look into this and hopefully get it fixed before the next deploy. Unfortunately, this would not be possible at this time. The theme would need to be reworked to fit into the new backend, and then we'd have to create a theme system that would allow users to switch between multiple themes. Then, moving forward, we'd have to remember to support any new features in all themes we end up creating. It's not out of the question, but at this time I think we are mostly themed out and ready to start adding new DB features Thanks everyone. We've read all the constructive criticisms about the database up until this point, and we will be making an update that will address as many of them as we can, which should get deployed either this week or next.

Simplest way is to use the game statistics syncing feature, which will sync your favorites (along with a few other pieces of data) across to any of your builds. You can find it under Tools > Cloud > Enable Game Statistics Syncing You will need a LaunchBox Games Database account in order to use this feature.

LaunchBox for Android is similar, but not quite the same, as the Desktop app. The difference is that the emulator choosing process comes after the import. When you are in any game view, click on the top-right menu and select Emulator Settings, and you'll see some emulator choices. For most systems, we do have a recommended emulator that is automatically chosen for you. If you try and play any game without first going into the Emulator Settings section, it will bring you to the Emulator Settings to set one up first. With the latest update, if you were to try and play a game that has an available RetroArch core, we will ask if you would like us to download RetroArch for you. If you agree, then we will take care of downloading and setting up RetroArch. We will also handle downloading the cores for you as well. Inside of the Emulator Settings menu, you can choose which core you'd like us to download and use in RetroArch for any given platform. For any other emulator (or version of RetroArch), you'll want to make sure you have it installed, and that you do any setup process inside of the emulator first, before choosing it in LaunchBox.

We will take a look into this emulator and see what can be done, before next release.

Thanks for letting us know. We were able to recreate it and it should be fixed for the next beta.

This post should help theme developers create a custom theme for the Game Discovery Center. I assume you already have some knowledge about how Big Box themes work. The Documentation.pdf file inside of your LaunchBox\Themes folder is a better place to gain knowledge on basic Big Box theming and bindings. I'll try and keep this updated if this view gains more themable features. Let me know if you have any questions. What is the Game Discovery Center From a themers perspective, the Game Discovery Center is a list embedded in another list. You have a list of games inside of a list of lists. It consists of just one xaml file where all code is located within. The file is called DiscoveryPageView.xaml How to start coding this view in your Custom Theme Assuming that you've run Big Box at least once with version 13.10 or higher, you can simply find the following file and copy it into your own custom theme's Views folder: LaunchBox\Themes\Default\Views\DiscoveryPageView.xaml To start editing the view, open your custom theme's project file, or open the DiscoveryPageView.xaml directly. The View File This section will break down the major parts of this file, so you can get an idea of what things are. The Parent List (The List of Lists) This will show up in the code as: <flow:DiscoveryPageList ...> Place this code where you want all the lists to appear on the screen. Here's a list of some properties you should know about: VisibleRows (int) - This controls how many rows should be visible at any given time. The lower the number the better performance, but go too low and you could get rows appearing from out of nowhere. You'll need to find a balance based on what your view looks like. SelectedItemPosition - This controls where the selected row will appear in the space you provide. This can force the selected list to always appear in one spot on the screen. The values are: Bottom, Center, None, Top SelectedItemOffset (int) - This will offset the list on the y-axis, starting at the top of the space provided, to give you more granular control over where the selected list appears. The following sections are used inside of the DiscoveryPageList: flow:DiscoverypageList.Style (optional) A basic Style section. In the default theme, it's used to change the SelectedItemOffset and SelectedItemPosition values for specific lists. flow:DiscoveryPageList.ItemTemplate This will contain what each list will look like. A DataTemplate will hold the layout of what each list will look like. Inside of a DataTemplate, you can add a FlowControl list or a ListView list (or both). These lists will contain the list of games (You can see examples of both inside of the default DiscoveryPageView.xml file). A FlowControl is a regular wheel type of list and is heavily documented inside of the Documentation.pdf file. A ListView is a type of list that is used in Text List Views, as well as the thumbnail lists on some platform views that display favorited and recently played games. flow:DiscoveryPageList.ContentLists This will contain the type of lists you want to see in your view. They will display in the order that you list them. The default theme contains a number of them that you can use. There are two distinct types of lists you can use: Hardcoded: We've hardcoded a number of lists that can be used inside your view Auto-Populated Lists: Lists based on our auto-populate playlist ruleset A list of all hardcoded binding options: An example of a hardcoded list of recently played games: Under the UserControl.Resources section of the view, add the following line to declare your list: <win:BindingProxy x:Key="RecentlyPlayed" Data="{Binding RecentlyPlayedList}" /> Then under the ContentLists section, place your list: <controls:SingleItemCollection Item="{Binding Source={StaticResource RecentlyPlayed}, Path=Data}" /> An example of a custom built list that shows recently added games: <controls:SingleItemCollection> <controls:SingleItemCollection.Item> <flow:GameContentList Title="Recently Added" Sort="DateAdded" MaximumItems="25" MinimumItems="5"> <flow:GameContentList.Criteria> <flow:GameContentListCriteria Field="DateAdded" Comparison="RecentDays" Value="360" /> </flow:GameContentList.Criteria> </flow:GameContentList> </controls:SingleItemCollection.Item> </controls:SingleItemCollection> flow:GameContentList This list type will populate games based on the choices you make within. Here are notable properties and what they do: Title - Gives your list a title which you could use in triggers and also use to display on the view somewhere Sort - Will sort the list based on possible values: DateAdded, DateModified, Developer, Favorite, GameCompleted, Genre, Installed, LastPlayed, LaunchBoxId, MameHighScore, MaxPlayers, Platform, PlayCount, PlayMode, PlayTime, Portable, Publisher, Rating, Region, ReleaseDate, ReleaseDateYear, ReleaseType, Series, Source, StarRating, Status, Title, Version, Random SortAscending (bool) - Tells which direction the games will be sorted. Default value is True MaximumItems - The maximum amount of items that will be generated in this list MinimumItems - The minimum amount of items that the list requires before it will be displayed flow:GameContentList.Criteria In this section, you can list all possible rules you want your list to adhere to. The rulesets are equal to what we have available under the auto-populate section when creating a playlist. It's highly recommended to build out an auto-populate playlist first so you can check if the games that get added to it meet what you want to accomplish. Then you can use that playlist to determine the values that need to be entered into the list. The following are the 3 available fields and their potential values (Remember that not all Field values work with all Comparison values) Field Comparison: Value - This is the value that you would input into the auto-populate playlist value field Dynamic Lists The system is designed to display an unlimited amount of dynamic lists which will start appearing after your lists in the XAML end. To the user this will be seamless, as a theme developer this is something you should be aware of when building your view. There's a lot of different types of lists that this can consist of, and each time the view loads, it will generate a completely random set of dynamic lists. Here's a breakdown of some types of lists that may appear in this section: Best - displays a random group of games that is above a specific user or community star rating Explore - displays a random group of games Worst - displays a random group of games that is below a specific user or community star rating The above may also be combined with other pieces of metadata, for example: Best of [year] Explore [platform] Worst of [genre] Best [genre] games of [year] F.A.Q. I want some game lists to look different than other lists, how do I do this? How do I display an image or text outside of a template? How do I display a video outside of a template? How do I change the title of a hardcoded or dynamic list?

If you were using the "RetroArch" entry as the emulator, what is happening is that when you launch a game, it checks what core you are using, downloads the newest version from their buildbot server, and loads it into RetroArch, then loads the game using the new version of the core. This could potentially cause a mismatch if you are using an old version of RetroArch. What device are you using, and which version of RetroArch do you have installed?