C-Beats

Need to enable the selected option in Attract Mode options via the Options menu

This isn't a bezel. It's your transparent image trying to be rendered on the new 3D model and is caused because you're using a 3D Box image type in the Box Front image group. To stop this from happening you'd want to use the 3D Box image group in your LaunchBox grid, and then the change will apply to the images in that view as well and you would no longer get the effect you are seeing.

Is there a reason you can't use List View to accomplish this?

If the game HAS GOG Achievements they are located the same place the Steam ones are. If the game has both Steam and GOG then there will be two tabs in the Achievement section and you can move left/right to go between them. It's important to note that just because a game has Steam Achievements doesn't mean that it will have them in GOG. Achievements are a newer mechanic for GOG and so many older games were revisited after release to add them to the GOG version.

Right now the websites have been going through a pretty large number of improvements and changes, and because of those we have not been able to add the new image types to the website just yet. If you have a pack like that I'd suggest uploading them to the forums download section for now. Users can then use the image pack importer to import and apply them to their collection.

This is related to using the Box Models in ImageView. Your images aren't the standard Front images which don't have transparency as is causing the issues you are seeing. I'll be looking into ways to mitigate this from happening for people using more custom images like that.

What you're asking for isn't randomness. What you're asking for is a predetermined value selected based on previous selections. Random would have repeats as you are seeing, the latter wouldn't (which is what you're asking for).

This is because you are using the 3D Box image as a Box Front image. If you removed 3D Box from the Front Image group you wouldn't see those black area's around the box. If you change your image priorities though you will need to delete your image cache and let it repopulate.

Revert, then go to LaunchBox\Data and remove InputBindings.xml file and you should be good to go. You will need to remap your controller bindings inside of LaunchBox and Big Box though after doing this.

What theme are you running? Event Viewer log reads like the fault was a memory access violation which typically happens when you run out of memory.

@The Mask What system is that case for? Want to take a look at the potential causes. Almost looks like UVs are backward but I haven't seen that previously happen.

You can turn it off in the Game Details area of the Options window

If you open Event Viewer you want to look inn Windows Logs > Application. Then once that grid loads up you'd look for a event log where the Level is "Error" and the source is "Application Error" Then look for one that mentions the faulting application name being BigBox.exe. Typically these come in pairs. One just says that Big Box faulted, and then another that has the actual error. The actual error is typically more useful, but both could be helpful.

There is no option but you can alter a theme to revert it to the old style. To get rid of that error delete InputBindings.xml file in \\LaunchBox\Data\. Doing so will reset your controller bindings in Big Box though so make sure you reset them after.

Go to Add/Remove Programs. Look for an entry labeled "Microsoft Windows Desktop Runtime - 3.1..." (there is probably a third number, depending on what you do or don't have installed. If that exists select it and remove it then restart your computer before moving onto the next step. Go here and download the .NET Desktop Runtime 3.1.31 (you want the x64 installer). Once downloaded run that setup, restart your computer again and you should be good to go.

@RobertBlum The issue you're running into is you don't HAVE Box images. You have 3D Box images. They are different in the LaunchBox ecosystem. The new models utilize the images from the Front/Back image group as well as spines and logo images (or a full scan cover image). If you want to continue to use the images you have in the old CoverFlow style you CAN but it requires an alteration to your theme file. Attach or PM me the "CoverFlowWithDetailsView.xaml" file in your \\LaunchBox\Themes\{ThemeName}\ directory and I can show you where/how to do that.

Typically this is because of corrupted system files in your operating system. To resolve the issue do the following: Run command prompt as administrator and then type the command "sfc /scannow" (without quotes) and let it run, then restart your computer. After you come back run the installer again. If that doesn't correct you may need to manually uninstall the runtimes and then manually install them again. If you get to this point and need help just ask and we can get you steps to do that as well.

Are you seeing anything in Windows Event Viewer? I know Jason has an army of test machines and all were started with the 13.0 official release before we deployed it, and as of last night he reported in that all were still running.

Just so I'm clear, are you referring to LaunchBox or Big Box?

Please stop opening frivolous tickets... The only image types in Carousel are Screenshots and Backgrounds, and every item that is IN the carousel can be opted out/in via the options menu

No, at the moment the feature doesn't support importing your own model files. It'd be interesting to try at some point, but there are just so many ways for that process to go wrong that it wasn't considered feasible to tackle first go around.

It'd require you messing with theme files but you could alter PlatformMarqueeView and GameMarqueeView to display the video instead of the main view and then enable the marquee on your second monitor. There currently is nothing in the UI you can tinker with to make it do this out of the box.

Could you be more specific? What theme are you using (assume you mean Old Default) and what view are wanting back to the way it was?

Norton is a pretty trash piece of software and is far more akin to ransomware than it is an antivirus program. You'd do far better removing it and using Windows Defender. In the meantime check your \\LaunchBox\Updates\ folder and see if you have the 12.16 installer in there. If so run that against your current install and it should put 12.16 and all it's files back and get you back up and running. Running the installer won't clear any data so you're safe there. Just make sure you don't accidentally install it to \\LaunchBox\LaunchBox\

Nice catch @elwooha6! I have this corrected on our end. Should work better in the next release.