C-Beats

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.

Then you need to check your spacing settings. Airy doesn't add gaps like that on it's own. Option page looks like this. Decrease Vertical spacing and it should decrease that gap.

What theme are you trying to use and how did you install it?

Should be able to just turn on dynamic box sizing in options and it'll take care of it for you

First off you need to understand LaunchBox is a front end NOT the emulator playing the games. You're first two would be emulator questions as they handle all game input and display settings. LaunchBox doesn't care about your screen refresh rate. Third item answer is yes, you can organize your collection however you want. Put them in their own platform, playlist, etc so that you can navigate to them how you want.

Can import them all, delete the items you don't want from LB, then (if you're using a non-merged set) use LB to move the roms to a different folder for whatever is left and then delete the rest.

Instead of importing the folder you can import just the files and hand pick. Either use "Select Files" in the wizard, or just drag the roms to LB and run the importer from there

Not sure I've seen the error you're talking about regarding not being able to install to Program Files before (unless that some OS error you were getting). You however easily change the roms paths in your collection. Open LaunchBox and select a single platform in the side bar, then select all the games in the grid and go to Toos > File Management > Change ROMs path for Selected Games (or something similar to that) and point it to the folder those games are in, then rinse repeat for all your platforms.

The menu is the LaunchBox Icon in upper left corner. Click it and you can navigate to any of the menus from there.

Short of the MAME Fullset importer LaunchBox only adds games you tell it to add so you can put in whatever you want. You could even pull down a large set, and use LaunchBox to pair down the collection and remove ROM files you're no longer interested in. If importing MAME roms just make sure you check the "Force use MAME metadata" checkbox on import so it properly reads those "cryptic" file names for you and matches them appropriately.

Just had some one report something similar in Discord and the cause for them is because they had "Use All Controllers" on and a wheel plugged in and it was causing it. I'd make sure you aren't in a similar boat.

LB shouldn't actually crash, but Windows will probably tell you the app has stopped responding. Doing an auto-pop with no filters takes that window FOREVER to grab all the games (which it does on the main thread) and so Windows see's it as locked up and offers to close the app for you. If you let it go though it will eventually come back with that tab full of every game in your library. Is something we should probably make work a bit better, but certainly isn't new to this version.

If you're on 11.8 you should be good to just grab the latest installer and run it over your current install. You won't lose any data during the upgrade installation.

This happens when you're operating system is telling us it's not installed and so seems like you have a disconnect somewhere on your machine. First step would be to open command prompt as administrator and type the command "sfc /scannow" (without quotes) and let that run then restart your computer. If that doesn't do it you could grab the runtime installer directly from M$ here. If that STILL doesn't work go to Add/Remove programs and remove any .NET Core runtimes you see in the list and then run the installer again.