Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    13,723
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Jason Carr

  1. Well, I'm pretty puzzled then, as I haven't heard of this issue from anyone else. What theme are you trying to use?
  2. Okay, try completely uninstalling .NET Core from add/remove programs, then reboot, download, and run this: https://download.visualstudio.microsoft.com/download/pr/add2ffbe-a288-4d47-8b09-a39c8645f505/8516700dd5bd85fe07e8010e55d8f653/windowsdesktop-runtime-3.1.8-win-x64.exe If that doesn't work, what version of Windows 10 are you running? You can get the details on the version by typing "winver" into the Start menu.
  3. If it did indeed repair some corrupted files, then I'm fairly certain that Windows corruption is the culprit, unfortunately. From what I've read, sometimes you do have to run the "sfc /scannow" command multiple times in order to fix everything, so that would be worth trying. The best course of action is to run it after a fresh reboot, and keep rebooting and running it until it no longer reports any errors. Let me know if that makes any difference.
  4. @Vastarien I have fixed these issues with the CriticalZoneV2 - Default theme for 11.7-beta-3, which should be out later today.
  5. No worries. Did you have any luck fixing the drive corruption?
  6. Thanks @Middcore. What theme were you running when those errors appeared? Unfortunately, I'm guessing you have some sort of corruption with your .NET Framework or .NET Core installs. It might be worth trying to uninstall and reinstall them. It also might help to run "sfc /scannow" from a command-line to see if it finds and fixes any Windows errors or corruption.
  7. Thanks @slickrickstyles and @DOS76; this should be fixed in the next beta, which should be out later today. Let me know if you're still seeing this after updating to 11.7-beta-3.
  8. There's more to the Audit screen than just copying and pasting into Excel. But we'll look to see if .NET provides any kind of a solution for this. We'll look into this and see if we can reproduce.
  9. I'm pretty sure I have this fixed (the disappearing wheel issue) for the next beta. Should be out later today. This should be fixed for the new beta as well (should at least work as well as themes on exFAT work elsewhere).
  10. If a folder in Windows is telling you that it's corrupted, then you unfortunately have a file system issue. You'll need to run chkdsk and repair the drive.
  11. Older versions of LaunchBox did not do this because they did not cache jpg files as jpg files; they cached all files as PNGs. This is happening because the mislabeled files are now being cached as jpgs because of the mislabeled file extension. If it didn't work, then either a step was missed or something went wrong in the testing process.
  12. Does it fix the issue if you refresh your image cache? Try going to Tools > Refresh All Images in LaunchBox.
  13. @Dodoraemon Logos that show up with black backgrounds in Big Box are clear logos that are improperly labeled with a .jpg extension for some reason. You can fix them by renaming them back to .png. You may have to refresh your image cache to get them to update.
  14. The issue has been fixed as much as possible (and as much as it will be). *Most* themes have been fixed for that scenario, but not all themes. We still do not recommend using the exFAT file system when running LaunchBox from an external drive. It's much better to use NTFS.
  15. Just to clarify, you only need to purchase one license, and you can install it on as many machines as you own. The licenses that get banned for new versions are just the licenses that are distributed freely online.
  16. Beta 2 is out now with the following: New Premium Feature: A new "Start Themes Demo" option is available under the Big Box system menu that will randomly switch between the various themes, views, and platforms that you have installed. It's similar to attract mode, but also switches between themes and views. There are also various options for it available in the Big Box Options Themes Demo section. Improvement: The Big Box platform image cache is now theme-specific, which should help prevent platform images from one theme from showing up incorrectly on another theme Improvement: The Manage Platforms window has been overhauled The new Themes Demo features were built for several reasons; one, I think it'll be a neat feature that people will enjoy, and two, because it taxes the WPF theming engine more than pretty much anything else has in the past, so we'll be using it for internal testing.
  17. This is on my own personal bucket list as well, so I do plan to attempt it here at some point. The biggest challenge is that we'll need new media in order for the boxes to actually look correct.
  18. Oic, is it the "CriticalZoneV2 - Default" theme, or is the "Default" theme? I'm guessing that's where the confusion is coming from. Looks like we need to update the project file for that one.
  19. Odd, I see. So the issue is that your Big Box Default theme is waaaaay out of date. Did you used to have a Big Box license? The Default theme is only updated when you actually start up Big Box, so I'm guessing that it just hasn't been updated in a long time. I can get you an updated Default theme if needed. Let me know if you still need it after playing around with the theme creator.
  20. Thank you guys. I still haven't been able to reproduce either error, unfortunately. I'm still running my testing. @MrSco I'm thinking I have to be missing something somehow. I'm sorry that it's been so long and that we haven't been able to get it figured out. I'm wondering if you'd be willing to do (yet another) test for me. From what I can tell, it has to somehow be related to the collection (because you're testing on multiple machines and such), but as I've been testing with your data it doesn't seem to be data-related, and now we know that it doesn't seem to be media-related. Would you be willing to make a brand new instance of LaunchBox/Big Box on one of your machines and import just a few platforms? That way we can confirm whether it's actually collection-related or not. @ItchyRobot Can you try updating to the latest version of .NET Core? There's actually a later version out than the one that comes with the setup. Here's a direct link: https://download.visualstudio.microsoft.com/download/pr/add2ffbe-a288-4d47-8b09-a39c8645f505/8516700dd5bd85fe07e8010e55d8f653/windowsdesktop-runtime-3.1.8-win-x64.exe
  21. All of the Options pages and screens are indeed themeable in recent versions of Big Box, so there shouldn't be anything holding theme developers back, from that perspective. Changing font sizes is very easy to do, even by hand. I understand though if the Community Theme Creator doesn't support this yet; @y2guru's been busting his butt on it to meet the demands of the community (and they are very demanding lol).
  22. Okay, thanks guys. I'll do some more testing with EmuMovies media. What particular platforms are you importing that you're seeing issues with? Any chance you can screenshot me the errors/file names?
  23. @Vastarien We would recommend using @y2guru's Community Theme Creator: It'll give you a decent idea of what can be done in theming Big Box without having a license. I did just load up the Default theme project in Visual Studio though (the one that comes with 11.6), and I'm not seeing any errors. What errors are you seeing? Per what Big Box can do theme-wise, there are lots of videos on the YouTube channel. Unfortunately though Visual Studio won't really give you all that much of a way to test your themes, without having a Big Box license.
×
×
  • Create New...