C-Beats

Most of the time we here this it's because an overzealous AV has quarantined a required file. Please verify this hasn't happened. You can also look in Windows Event Viewer's application logs for a .NET Runtime Error error log. There could be one in there that says LaunchBox crashed, along with a second log entry that has the actual error and stack trace saying why.

Thanks was able to track down the cause and it'll be corrected in 13.21 release. Once that's out I'll push a theme update which solves @hkr's issue as well as some visibility binding errors related to MAME high scores.

Yeah, you can do this. The issue is related to WPF trying to decide if needs to display the scrollbar or not and this forces it to always do so which eliminates that.

Was able to replicate this thanks to your video and pin point the cause. Unfortunately override logos for Platforms and Playlists and dumping into the wrong folder. If you want to use this functionality between now and when the correction is released you can manually place the images in the appropriate folder: For Playlists: \\LaunchBox\Images\Media Packs\Overrides\Platform Clear Logos\Playlists For Platforms: \\LaunchBox\Images\Media Packs\Overrides\Platform Clear Logos\Platforms

Thanks for this, we'll take a look.

Yeah, that functionality is all built in and should be working. What aren't you seeing work?

Inside of LaunchBox there is a Video Priorities section in the Options Window. It was moved there when the new video types were added.

Just posting here so others with a similar issue can potentially find relief as well. User posted in Discord this was because of SSL/TLS options/filters in the user's antivirus program interfering with the processes.

I moved this out of the beta thread since it isn't beta related. Anytime LB hard crashes without showing an error message first then the issue is a .NET runtime issue and should appear in Event Viewer in Windows. Open it up and look in the applications logs for error records. There will be two back to back error messages (at least one of them should say something about a .NET runtime error). One of the logs will just say the app crashed and tell you the exe file for the crash. The next log has the actual error and stack trace (will just function calls with line numbers at the end). That message is needed and will point to the cause of the issue. If you can find that post it up here and we can try to help you get the issue resolved.

This should be resolved with the changes to our installer that is planned to be rolled out next version. Glad you were able to get it sorted for now though.

When it's ready. Soon™

I'm not aware of any, but I'm not 100% positive. I do know we've been getting a lot of reports of their API having issues over the last few weeks so they may be making changes over there and it causing some potential connectivity/stability issues.

Should resume from where it it's at if you close and reopen LaunchBox. If it doesn't just rerun the wizard. If you select the "do no replace" option it'll only download the media for the items that still need it