faeran

That makes sense then, as both of those file names aren't part of the current MAME filename standards. As far as LaunchBox crashing, it might be a bug. I just tried it on my device and can't get it to crash at all, so it might be device specific, or user data specific. I don't have an Nvidia Shield to test this out on, but I know other people in the community do. That's good to hear. the fbneo core is definitely the way to go if you have a set that works with it.

The only reason I can think of where a file doesn't get imported is if it's already imported and in your library somewhere. To test this theory out, turn on the option to "Force Import Duplicate Games that Already Exist in Your Collection...". If you see the games listed in the import, then this is what the issue is. Not really sure here. That core is for a really old version of a set that doesn't really exist these days, so I'm assuming your files are from a set that is fairly old. Did you make sure in LaunchBox that it's launching into the right version of RetroArch and using the same core that works when launching directly in RetroArch? You will also need to disable the option to "Extract ROM Archives", if it's on, as Arcade games don't like it when you do that.

Cool concept, although I'd say not all of it could be done at the moment, even with code. The main thing that's probably missing is a Z axis offset property that would allow you to have items get progressively smaller the further away from the selected item you go. Other than that, you could get close, but even in the concept image some issues would arise, like you are only displaying 5 images within the wheel, so what exactly would happen on the left and right sides of the wheel as you navigate around? I'm also assuming those are the 2.D images, which look great in still images, but kind of lose their mystique when thrown inside of a 3D control. Also, since the images are so compact together, you may run into some z-fighting as things move around. I took my 3-DIMENSIONS theme and did a quick and dirty job here to show that some of what you are after is certainly possible:

Sounds like you may be using an outdated theme. If you would like to continue to use this theme, you can delete the following file: LaunchBox\Themes\[theme name]\Views\MusicNotificationView.xaml After that, you should be okay. There may be other files you'll need to delete (like the KeyboardView.xaml) if you run into similar issues using that theme.

I updated the CTC files. You'll have to tell me whether they are correct, as it's been a while since I did the 2.03 update.

yup, changing the video file would work. For per-platform video, maybe the easiest solution would be to set up multiple per-platform view files, and inside of each one, point to different video files.

Something to keep in mind is that we use the official hashing program by RetroAchievements, found here: https://github.com/RetroAchievements/RALibretro/releases Any time there's a new version of that program, we will be updating LaunchBox with it. It may be worth the effort to help them determine where they should be focusing their time.

Themes can now be downloaded from within the app itself using the Theme Manager. Here's more info about it: If you mean Platform videos, here's a video about them:

Is this a Big Box question or a COMMUNITY Theme Creator question? I wasn't able to tell. If you can also clarify what exactly you are wanting to do (screenshots go a long way), that could help as well.

Rlad is right that you are confusing the 3D Box Images with the new 3D Box Model. This theme uses your Box - Front, Box - Back, and Box - Spine images to create a 3D Model of each game that you can flip and rotate around. The only thing is that since this is a Theme specific 3D Model implementation, there's no way to turn it off in the options. If you don't want to download 2D Images for your games, you'll have to use another version of Unified.

It's definitely possible when I circle back around to this one. Not entirely sure when that will be, but I'll keep these platforms in mind when I do. If anyone else wants to take a stab at them in the meantime, I wouldn't mind either 😉

Any changes to the interface that you make will save the next time you close LaunchBox. LaunchBox runs a whole bunch of shutdown processes when you close it out, and your layout is one of them.

If you are happy with the way things are working, then there's never really a need to update anything. If you do end up updating LaunchBox, there shouldn't be any reason to update your metadata or run any of the other tools in LaunchBox.

If I had to guess, it probably does work, but not sure if it does it gracefully. I ran a quick test on one of my monitors and it seems okay. Everything fits, and you can resize the game details panel and the box sizes and such. It's not perfect, but it does seem to work okay.

Awesome. Can always immortalize your pack in the downloads section here: https://forums.launchbox-app.com/files/category/226-custom-sidebar-icons/

Pretty sure it was mentioned earlier in this thread that in the icon file name you can simply replace the apostrophe with an underscore and you should be good to go.

Thanks @Self-Mao. Yes, it's possible. I'm guessing you mean the clear logo inside of the banner, which is all custom code. I haven't taken a look at it in a long while, but you would essentially create a text block displaying the game's name in the same position as the clear logo, set the visibility to collapsed, then create a data trigger that says "if the game has no clear logo, set the visibility to visible".

Pretty sure with that theme the quality level is determined by your CoverFlow Image Quality setting. Go into your Big Box options, under Images > CoverFlow Image Quality and adjust to your liking. After you do that, you may need to refresh your image cache under the Image Cache options.

Sorry to hear, although there has been multiple responses from us within this very thread. The only reasons LaunchBox would keep asking for .NET to be installed would be either: You have the incorrect version of .NET Core Runtime that's required for LaunchBox to operate (there's so many different versions, and so many variations of the same version that it's easy to mix them up) Some Windows files are corrupt and cannot tell that you have the correct version of .NET Core installed. Here's the link to the correct version of .NET Core 3.1: https://dotnet.microsoft.com/en-us/download/dotnet/3.1 You should be downloading the x64 link under the header: .NET Desktop Runtime 3.1.32 (middle part - right hand side) If you would like to know which versions of .NET Core you have installed, you can do the following: hit Windows Key + R (for run) type cmd and hit enter type: dotnet --list-runtimes If Windows files are corrupt, you can do the following to try and fix it: hit Windows Key type cmd, right click on "Command Prompt" and choose Run as Administrator type: sfc /scannow There are also tools out there that can try and repair or uninstall different versions of .NET that may be conflicting, but I believe those tools are more advanced and you should use them at your own discretion.