C-Beats

If you're referring to RA core settings that is store in RetroArch folder and isn't managed by LaunchBox at all.

Both entries I'm referring to I believe are error logs. You get the error log you posted then another with the actual error text (which is in neither of the logs you posted)

Typically this is caused by a bad refresh rate being set by RetroArch or your monitor. Make sure you are running at full framerate and at least at 60hz

Sounds like a plan. Many thanks for the help @moudrost

1) I've seen it reported a few times now and is on the short list to see if I can replicate and correct for next version. What theme are you running? May help in identifying the cause of the issue. 2-3) This is caused because you are still caching images. You can force the image cache in the options menu to help reduce this. I will warn you that depending on your setup this can take a WHILE and should treated as an overnight task in most cases 4) That is all determined by your theme. Typically though no they play the videos in the video section and treat it the same regardless of the type of video 5) If manually correcting yes, but our process should be able to find those regional differences and name the files appropriately. That being said we expect region data to be in parens so if it isn't that could cause issues. 6) that is set up entirely by the uploader

You could copy the view and make a platform specific override to change the border image to be 16:9 so that it works with your videos. This would require manually altering the XAML files though.

Just mean physically press the button causing the issue. For that side menu you'd press the left shoulder button or press the left trigger and it should stop (or does on my device when I have the issue).

As Neil stated that is working as intended. When first entering a sidebar value the default background is used as you're seeing. You can however change that in the options. What you see in ETA Primes video is that he uses his desktop wallpaper as his background instead of LaunchBox's default one

If you have 600+ gb of MAME games you probably grabbed them from the wrong spot or have a bunch of useless CHD files bloating your install. Full non-merged set is something like 125gb as far as I remember

This is typically caused when you first open up the app in the "Games Missing Media" sidebar filter. Change the filter before closing the app and it should correct this.

There is a hidden field we have set in the data that stores the GOG App Id of the game that is used when launching from GOG Galaxy

There are a lot of things that can affect this. The most common two are: You have a media limit set and have reached the limit for that image type You already have the image (CRC's match)

@moudrost when you see the app has hard crashed to the desktop could you please look in Windows Event Viewer in the application logs for the error log that would have been generated. There will be two for each crash, one tends to have an actual error code, the other is just a log saying it crashed. Could you send us a copy of the log with the error? This will help quite a bit in discovering what is causing the crash on your system so as we move forward we can do a better job identifying and addressing it.

You don't have the ability to manually change the height of that section of the control. To do so you'd need to scale the whole thing up and then scale the preview items down. This would result in the preview image/section becoming bigger and making the preview items stay the same.

Look in the GameDetailsView.xaml file for a Carousel element (is the only one) You need to increase the size of that carousel (believe it has a MaxHeight set you can change. There is an ItemScale property that can be set if you need to shrink the preview items as well, by tweaking the two you should be able to increase it the way you're hoping. That being said I think we force a 16:9 aspect on that preview section so you're not going to be able to increase it much without making your GameDetails wider

What theme are you using? If you go to that theme's View folder (\\LaunchBox\Themes\{Theme Name}\Views) if there is a KeyboardView.xaml file in there can you delete it and then restart Big Box and tell me if you still have the issue?

Assuming this is for Big Box the default theme files can be found in \\LaunchBox\Themes\Default. You will want to copy this folder to a new one before making alterations as Default folder gets overwritten on startup. You can't load the theme into CTC because it wasn't made with it and has many features that the CTC doesn't currently support.

Concerns like this are WHY we have the Beta release. If you're concerned about something like this drastically affecting your everyday use case, please upgrade to Beta and let us know for sure so it can be properly addressed before an official release. As with the official version updates, you can downgrade after you have tested your concerns if you don't wish to remain on that version.

Thanks for letting me know. This DOES appear to be an issue with the beta's and a code change introduced in beta 4. I have been able to find the cause and correct it and will be in the next release. Thanks for working through this with me and glad we were able to find the issue before the official version release.

What version of LaunchBox are you running?

These popups can be navigated with controller to press the keys and search. Are you saying you can't do that?

Sounds like you're running RetroArch for mame and don't have your core set correctly and are defaulting to the 2042 (or whatever number it is) core. Go to Tools > Manage > Manage Emulators and edit RetroArch. Go to the associated platform tab and update the core for the Arcade platform (or whatever you called your platform) to use the correct MAME core you wish to use. Then press OK and you should be good to go.