faeran

My guess is that you can add it as a user source in the CTC, but the CTC won't know what to do with it and probably provide an error. There should be a checkbox that allows you to stop it from trying to render that element in the CTC. When you publish the theme, you'll see the 3D Model in Big Box. The only way you would be able to see this Model in the CTC is when the 3D Model is added as a native element within the CTC.

yeah, it's a camera perspective thing. I could probably have another crack at adjusting the camera settings, but that probably won't be for a while. Since this is a custom theme, you will have to dive into the XAML view files in order to remove the parts of the theme you do not want to see.

Are you able to show some screenshots of what you are doing?

Which badge were you thinking should appear?

Sounds like you may have accidentally told LaunchBox to use the 2048 core for those platforms. You can confirm this by going into Tools > Manage > Emulators, then opening the RetroArch entry and enter into the Associated Platforms section. Find those platforms and see what Core it's associated with. Change the core to one that works for those platforms. It's worth knowing how to look through the libretro docs for all sorts of information about cores and bios files for RetroArch: https://docs.libretro.com/library/bios/ It does look like Intellivision also requires some bios files, based on their docs.

Beta 2 is out with the following changes: New Premium Feature: Big Box's keyboard automation can now be used without a Hold key (which enables using a single dedicated key for keyboard automation operations) New Premium Feature: A new option to automatically use Big Box as the Windows Shell has been added to Options > General in Big Box. This option will allow you to avoid loading Windows features like the Start menu, taskbar, etc. and will use Big Box exclusively as the shell. This feature is not for the faint of heart, but does result in a faster and cleaner startup for arcade cabinets and home theater environments. Improvement: Big Box's volume bindings will now work to change the system volume when the Windows shell is changed (such as when launching Big Box directly on Windows startup instead of Explorer.exe) Improvement: Added setting to stop 3D models from being used in Game Details Improvement: Added setting to stop 3D models from being used in CoverFlow views

Yes, within Platform Categories section in LaunchBox, right click your Arcade Platform and use one of the playlist auto-generator options:

Kind of. Really depends on what your end goal is. If your only end goal is to build a section in Big Box that has the platforms, categories, playlists you want to see, in any hierarchical structure you want to see, then that's what Platform Categories is for. Once you create it in LaunchBox, you would use the Platform Categories section in Big Box to see it.

If you want complete control in what you are seeing, whether it be playlists, platforms, or categories, that's what the Platform Categories section is for. It's essentially a way for you to have full control of the building blocks, and you can place whatever you what, wherever you want, and all of that gets reflected in Big Box.

That error message indicates that you have pointed to a folder that does not contain a full MAME Romset. Since the wizard is only designed to work with a full set, it will not continue. If you only want to import some MAME ROMs, you should be using the ROM Import wizard. And yes, MAME ROMs are designed to only work if not unzipped.

Also worth mentioning that if using the MAME Arcade Full Set import wizard, you'll have an option for LaunchBox to create a Vertical game playlist during import.

There's an option in Big Box called Hide Auto-Generated Playlists from Playlists View, found under the Views section. It sounds like this is the option you are looking to disable. You could also build up the Platform Categories section to see only the playlists/platforms/categories you want to see in Big Box.

That option won't do anything in the current default theme. It's essentially an option for a user to set what image group would appear in the game wheel IF the theme's wheel code doesn't hard code a specific image type. Most themes these days hardcode an image type which overrides that setting. Based on your original post, I'm assuming you are trying to get a specific image to appear in the Game Details view, or at least something outside of the game wheel, and the only way to do that is what you did, make the change in LaunchBox by changing the Image Group on a per-platform basis, and that will get reflected in Big Box.

The first 13.1 beta is out now and the thread for it can be found here:

Hey everyone, LaunchBox 13.1 beta 1 is out now with the following: New Premium Feature: The 3D Box Model can now be viewed full screen in both LaunchBox and Big Box New Premium Feature: CameraPosition binding has been added to the FlowModel control (for theme devs) Improvements: The 3D Box Model can now be panned by the middle mouse button in LaunchBox and the cursor keys on a keyboard, or dpad/left analog stick on a controller, in Big Box. Improvement: The way LaunchBox and Big Box call LEDBlinky has been improved in order to reduce apparent slowdowns when dealing with large controller boards with lots of buttons/RGB Fixed: The default logo rotation on the 3D Box Model Fixed: The appearance of some image types for EmuMovies during the Import and Download Metadata & Media Wizards Fixed: Images with transparency no longer render a 3D Model in Big Box's ImageView Beta 2: New Premium Feature: Big Box's keyboard automation can now be used without a Hold key (which enables using a single dedicated key for keyboard automation operations) New Premium Feature: A new option to automatically use Big Box as the Windows Shell has been added to Options > General in Big Box. This option will allow you to avoid loading Windows features like the Start menu, taskbar, etc. and will use Big Box exclusively as the shell. This feature is not for the faint of heart, but does result in a faster and cleaner startup for arcade cabinets and home theater environments. Improvement: Big Box's volume bindings will now work to change the system volume when the Windows shell is changed (such as when launching Big Box directly on Windows startup instead of Explorer.exe) Improvement: Added setting to stop 3D models from being used in Game Details Improvement: Added setting to stop 3D models from being used in CoverFlow views Beta 3: New Premium Feature: New options to "Hide in Big Box" have been added to platforms, platform categories, and playlists New Premium Feature: Jewel Case and Long Jewel Case models have been added to the 3D Models features. Platforms will automatically utilize this model where applicable with regionalized front spines available for certain platforms. It is also available as an option under the platform's 3D Model Settings in LaunchBox. Improvement: Support for Amiga WHDLoad filename parsing has been added to the ROM Import wizard Improvement: The Navigation Direction binding will now function in the system view, options view, and game details menu view (for Theme Devs) Fixed: Categories and playlists that contain no items will no longer appear in Big Box Fixed: Changing the Default Additional Application for a GOG game would sometimes launch the wrong app Beta 6 New Feature: A new option to automatically start applications alongside LaunchBox or Big Box has been added to LaunchBox's Options > General > Startup Applications. Improvement - LaunchBox Plugins can now correctly read StateManager.SelectedPlatform and are notified when a sidebar value changes (for plugin devs) Improvement: The jewel case 3D model has been updated to include ribs on the top, bottom, and front spines Fixed: Box - Full images were being used incorrectly in some models Thanks to your willingness to help test out these betas with us.

It's all dictated by MAME itself. They categorize every rom for each version of MAME and LaunchBox uses that info.

The page does seem to be fairly self-explanatory as to what it does. Maybe you can list some of your favorite games so you can understand why they would or wouldn't show up depending on the settings. Basically, MAME creates an extensive database of categorizing all their games. LaunchBox uses that database and presents you with options to allow you to filter MAME games during import. You can use websites like Arcade Italia to provide you a visualized breakdown of this information on a per-game version basis. For example, some games require extra CHD files to run, so by checking the Skip games that require a CHD file option, they won't be imported. This includes games like Gauntlet Legends, Street Fighter III, Area 51, CarnEvil, Mace, War Gods... etc. Some games are marked by MAME as unplayable, even if they can basically be played with bugs and the rare freeze. Those games won't be imported if you leave the check mark to Skip games unplayable in MAME, these include games like Primal Rage, Strider 2, etc...

This is actually a user setting. Go into Tools > Options > Data > Search There's an option in there called "Minimum number of community ratings in order to use". Set that number to 10, or whatever you like. There's also the ability to create auto-populated playlists with top rated games, and the Arrange by option can be used to arrange by star ratings, or the ability to look at the results in list view and sort by star rating.

What version of LaunchBox are you on? There was an update at some point that makes it so any new platform imports that happen will now set the default games folder for you based on the location of where your ROMs are located. I just tried it out and it's still working well.

I don't think there's a way to map a button to set a filter. You do have the option to create a dynamic playlist that will only show games that are currently installed on your system, then you can nest that playlist anywhere within your platform categories filter area.

Could be wrong, but I'm pretty sure your portable drive just needs to be formatted in a file system that supports symlinks, so something like NTFS. Then it should work just fine.

If I'm reading this right (and sorry if I'm not), this is actually already an option. During the import, you have the option to Copy/Move files into the Games folder, or use the files in their current location. You'd want to choose the option to use the files in their current location.