C-Beats

Not sure I understand the question. A games platform is only used to determine what BezelProject repository to pull from. After that everything is driven by the ROMs file name.

Bezels aren't saved anywhere inside of LaunchBox's directory permanently. They are downloading to a temporary directory that is deleted when LaunchBox is closed. There is also no way to view an individual game's bezel inside of LaunchBox at this time.

Close LaunchBox. Then navigate to your \\LaunchBox\Updates folder and find the installer in there. Then manually run the installer over your install (make sure you don't create a \\LaunchBox\LaunchBox directory when doing so) and you should be good to go.

Just edit those games and on the first page set installed to a checkbox (true) instead of the square (empty). You can also use bulk edit to do it for multiple games at once.

Can use Arcade Italia to get a list of those titles and output an ini file. Then use @JoeViking245s plugin here to create a playlist with it.

LaunchBox and Big Box have never played the game inside of the application itself. We just launch your emulator. Where there MAY be some confusion is that perhaps in the past your emulator was told to run full screen and now is not. You may need to check the command line arguments you have set in your emulator to ensure you're telling it to launch full screen.

Ah yeah. That data grid is pretty temperamental about what columns you can/cannot have in it. Not sure you'd be able to put it in it's own column with any degree of success. You can append it inside of another column (title for instance) if you wanted to pretty easily though. I'll take a look while I'm working on next version to see if there is any other work arounds I can find to help it all work.

Can grab the latest release of my Beats theme to see it in action. All that's needed to do it is add an Image who's source is "{Binding ContentImage}".

Yes. 12.13 is live and official. The release date wasn't properly added to the changelog before publishing the version. It'll be corrected with the next beta release.

To be honest I'm not entirely sure. The .NET core run up was pretty different to what Microsoft did with .NET Framework and many of the SDKs/Runtimes weren't fully backward compatible. Also .NET 6 is just simply "dot net" while 3.1 is "dot net core" in moniker and I'm unsure if there was anything done in that transition that makes the newer runtimes not as compatible. Pointing to 3.1 runtime ensures they have a version that WILL run the app and eliminates the possibility of a newer runtime causing potential issues that we then have to get past to troubleshoot any future issues. If the user HAS to have that runtime to run other apps and the OS overwrites the 3.1 runtime there is of course little the user can do, but if it isn't required it eliminates a possible issue for them to get tripped up on moving forward.

Hmm in your video when in the Aether app adding the folder it doesn't look to me like it added the folder you were navigating to. I don't see it getting added to the list and the one that IS there isn't the same as what you're pointing to in LaunchBox.

The link to the correct runtime version is here: https://dotnet.microsoft.com/en-us/download/dotnet/3.1 The screenshot above shows .NET 6 which is not what LaunchBox uses. For Windows 11 users having issues with the runtime not detecting you can do the following: Navigate to Add/Remove Programs Look for an entry that starts with "Microsoft .NET Core" and remove them. Restart your computer. Download and apply the 3.1 desktop runtime (x64) from the link provided and then restart your computer again. You should then be able to open LaunchBox. We've had a few users have to go through this process (unsure if the OP had to or not) for some reason on Windows 11.

I would open up Windows Event Viewer and look in the Application logs for an error log for LaunchBox. Sounds like you have a dependency crashing, that log would help identify which one it is.

I'd make sure you're on the current version of LaunchBox then. Mine works fine, but mine are on SD storage and not internal storage so not sure if you're running into anything weird with that. @Jason Carr would know more than I regarding that though.

You need to tell Aethersx2 where you ROMs are and let it scan the folder at least once. It will ask for permission and you will need to give it to the app. Then it should work in LaunchBox.

Define "won't update". Do you get an error while the installer is running? Is the installer running then opening to the wrong version?

Theme has been updated to 1.4 with the following changes: LaunchBox requirement changed to 12.13 or newer. - List View is no longer a data grid and is instead a single file list of games displaying the following information - Game Image - Title - Platform and Release Year - Date Last Played and Time Played - Badges

At the moment the only way to do what you are asking is to tell the Download Metadata and Media Wizard to overwrite all existing media. This will delete any media you have for that image type and import new. Alternatively you could delete the corresponding folder in \\LaunchBox\Images, and then run the tool.

It doesn't have all the filter logic you are referring to but there is a "Select Random Game" function in LaunchBox in the Tools menu.

Thanks for the report @SqHd. I have code change in place and this will be corrected in next release.

What core are you running for those systems?

This means you have an invalid license.xml file in the root of your LaunchBox folder

No ideally we'd track down the cause and correct it if it is caused by the beta. Does this happen with all themes? If so could you turn on debug logging, start LaunchBox, let the grid load with the issue and then close it and send me the log file generated.

Nice theme choice. I'm unable to replicate this though on any of my builds. If you select all the items and press F5 do they come back?

I don't know enough about that emulator to know if the folder structure is the same and the same lay files work in it. If you know they are the same you could probably change the exe name to "mame.exe" then update your emulator entry in LaunchBox. Run the wizard and then undo those changes.