Jason Carr

Hmm, I do wonder if upgrading to .NET Core 3.1.8 would fix it for the people who are having issues.

@MuddyWaters79 I'm glad you got it resolved. I wish we knew what in particular was causing it though. I think it's probably caused by something being corrupted somewhere, but having to reinstall Windows and everything else from scratch is such a pain.

@dietz33 This is the first time I've seen that error. What version of Windows are you running?

Yes, unfortunately we cannot accept censored images. It makes zero difference whether a nipple is replaced with a little tiny star or not lol. This is ultimately for the longevity of the site, so we don't get shut down, and for the protection of children. LaunchBox is based in the US, and so we have to follow US laws.

Okay, then the external should not be the issue. Yes, it would be worth trying to uninstall and reinstall both the .NET Framework and .NET Core. It also can't hurt to reinstall LaunchBox; just install it over top of the same folder and you won't lose any data.

@MrSco I'm currently testing with your data on the WD external drive. Out of curiosity, I'm wondering if perhaps there's a custom setting that could be causing the issue. Either way, I'll probably find out soon enough in my testing, but if you want to test, you can try deleting your Settings.xml and BigBoxSettings.xml files (actually probably best to just temporarily move them somewhere else, so you can get them back). I'm curious if that makes any difference. I'll let you know how my testing goes.

Also, @MuddyWaters79, what file system are you running on your external? If it's exFAT or FAT32, that could possibly be the issue.

@MuddyWaters79 I updated my video drivers to 452.06, and I don't have the issue. So it doesn't look to be caused by a certain video driver version. Can you try killing all your background apps to see if that has anything to do with the issue? My only other ideas are corrupted .NET installs, though that would be odd considering you're running Visual Studio. Perhaps it could be caused by a corrupt .NET Core install, however.

I happen to have the exact same CPU and GPU on my main development machine, so that rules that out as an issue. It would certainly be nice to figure out exactly what is causing it. My nVidia drivers are currently on 451.48. I'm going to try updating to 452.06 to see if perhaps the latest drivers actually cause this issue...

That is actually possible. Generally, it's best to keep the same resolution throughout, especially if you use the startup and pause screens.

For clarity, here's what I posted in the other topic: Hi guys, just wanted to chime in here. First off, I'm sorry for the trouble with the video corruption. Unfortunately this particular issue is some kind of bug or incompatibility between .NET Core and certain video drivers. Out of curiosity, what video cards do you have? This one is a tough one because it's either a Microsoft or a driver bug, and so there's very little we can do to try and fix the issue. We use Microsoft's WPF to render things in LaunchBox and Big Box, so unfortunately that means that if WPF has a bug, LaunchBox and Big Box will too. If I had to guess, though, this probably comes down to a bug with certain video drivers. I would first try updating your video drivers to the latest version available, and then making sure that you're 100% up to date on Windows updates. I would even try updating to the Windows 10 May 2020 Update if you haven't already: https://www.microsoft.com/en-us/software-download/windows10 If worse comes to worse and there isn't a fix available for your system yet, I would recommend staying on the 11.2 version until Microsoft and/or your video card manufacturer fixes the issue. Here's a link to download 11.2: https://www.dropbox.com/s/cg7fteljnwf0s9r/LaunchBox-11.2-Setup.exe?dl=0

Please see my post above @MuddyWaters79.

@MrSco Still working on reproducing. Can you zip up and PM your LaunchBox\Data folder? Outside of media, that should put us on almost exactly the same page.

Not a bad idea. Can you create a BitBucket ticket for it? Okay, I'll do some testing on some older hardware to see if I can reproduce. Obviously the core count doesn't look to be an issue. Unfortunately I don't have a solution for this currently. I'd have to re-engineer the setup. My best idea currently would be to install it on another system and copy the files over.

Come to think of it, we should get your data in case the error is just being misleading. Can you zip up and PM me your LaunchBox\Data folder?

This oddly seems to be an isolated issue; I haven't seen it anywhere else. Currently, my only thought is that it could be some kind of weird text parsing issue maybe due to localization settings? What country do you live in?

Hey all, I've updated the script at the beginning of this topic with the following: Updated to install the new 11.5 release Fix for a possible out-of-date apt-get issue Fix for @jedigu's reported issue above 11.5 was seeing some conflicts with the symlinks that were created by the previous script, so you may need to delete the ~/LaunchBox/drive_c/LaunchBox/Core folder before installing 11.5 if you're not starting fresh.

Are you installing it via the forums or the Big Box Themes Manager inside of Big Box?

Thank you @kurzih.

I see. Yeah, unfortunately something is corrupted on that machine, though it might be difficult to tell what. This looks to be a different issue than the Big Box video corruption issues. Unfortunately troubleshooting it is likely to be a huge pain in the rear. I would suggest making sure that nothing else is running in the background (just in case that is the issue), then searching specifically for updated (or even downgraded) video drivers, just in case the version you have is glitched for some reason. Make sure you download the video drivers straight from nVidia.

@Danabis This error is quite strange because it suggests that the theme XML files have somehow gotten corrupted. Either that or they're way outdated or something weird like that. I would suggest removing Unified Redux completely via the themes manager, and then reinstalling it to see if it resolves the issue.

Okay, yeah, that's all the way up to date. If 11.2 isn't working either, then something is unfortunately messed up on the machine. What exactly is happening with 11.2? The same video corruption stuff?

What specific version of Windows 10 Pro? You can type winver into the Start menu to get the details.

This has been resolved for 11.6-beta-1, which isn't out yet, but should be soon. In the mean time, I still recommend the solution above.

Hey all, I made some progress on this issue. The issue is showing up because of conflicting versions of the ListBoxScrollCenter.dll file. As a temporary solution, if you copy the ListBoxScrollCenter.dll file from the Colorful - Dark theme to other themes that use it (like CoverBox) and overwrite the other versions, it should resolve the issue. I'm working on a more permanent and automated fix for this.