Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    13,723
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Jason Carr

  1. @erling1000 @Wanderer189 Per Future Pinball, we'll look into why that command line wouldn't be working.
  2. I see. Here's the proper installer for .NET Core 3.1.6 x64: http://download.visualstudio.microsoft.com/download/pr/3eb7efa1-96c6-4e97-bb9f-563ecf595f8a/7efd9c1cdd74df8fb0a34c288138a84f/windowsdesktop-runtime-3.1.6-win-x64.exe Can you try installing that?
  3. I see. Running 32-bit or 64-bit Windows 10?
  4. Those files look right, so I'm baffled as to why you'd be getting any issues with .NET Core. What version of Windows are you running? Oddly, I just tested this and it seems to be working fine. We seem to be seeing a lot of strange issues with your setup; they're fairly varied, however. Would be nice to get to the bottom of what's different and causing all the issues. Do you have anything unique about your setup? I've change some code around here which should hopefully help for the next beta. Syncing your collection to the cloud is also fixed for the next beta as well.
  5. @wallmachine That all looks correct, yes. We have no control over whether Microsoft prompts to unblock the setups; thankfully, though, they do remove that warning after a certain number of people download it without issues. I can add more folder links for media and the ThirdParty folders if that will fix some plugin issues; I'll do that. That is helpful, but I need the same thing for the LaunchBox\Core folder.
  6. I checked the code, and it doesn't look we reference Microsoft.VisualBasic.Devices.Computer from anywhere in the code, so this definitely looks to be caused by a plugin. What plugins do you have in your LaunchBox\Plugins folder?
  7. What is the exact error?
  8. @Android16 We'll be fixing the project file in the default theme to work properly without errors before the official release.
  9. It would be good to figure out why the installer isn't working to upgrade your existing folder. The fact that it runs from a separate folder though means that you do, in fact, have .NET Core installed correctly. Can you take a screenshot of the files in your LaunchBox folder and your LaunchBox\Core folder?
  10. Beta 2 I believe.
  11. You can create button or key bindings to Switch View and/or Switch Theme which will allow you to switch the view and theme regardless.
  12. If the setup isn't prompting you to install .NET Core, then I would think you have it installed correctly, unless something got oddly corrupted.
  13. It already does. The new setups prompt you to download and install .NET Core if it's not installed. I would not release an official version with missing dependencies.
  14. It already is included.
  15. The problem with this code is that siteoforigin unfortunately now refers to the LaunchBox\Core folder, so it no longer works properly. However, I believe if you replace "pack://siteoforigin:,,," with "LAUNCHBOX_ROOT_FOLDER", it should work. Any themes that do this will most likely need changed/upgraded for 11.3, but I don't think it's a very common thing for themes to do.
  16. That's interesting. I assume the setup process does not prompt you to install .NET Core? I've seen this issue before, but only when files are missing from the LaunchBox\Core folder. Have you tried installing beta 4 to a new folder, separate from your current LaunchBox install? Can you give me an example of a theme that does this? Themes that use a custom folder outside of the theme's folder unfortunately may need tweaked/upgraded for the new version when it comes out.
  17. Beta 4 is out now, with the goal of fixing as many theme-related issues as possible. For example, the Colorful theme should work properly now, and startup and pause themes should work as well (but there may be some outliers still). There are still things in this thread that need addressed, but please let me know if you run into any theme-specific issues with this beta (and what theme it is as well as the error). Thanks again all!
  18. @Zeaede Are you trying to upgrade to a beta release, or the 11.2 official release? It's probably best to just download the latest installer from the website and install it over top of your current installation. Just make sure to install it to your LaunchBox folder and not a LaunchBox folder inside of your LaunchBox folder. It won't overwrite your data or your configuration.
  19. Beta 3 is out now with the following: Fix for the LaunchBox interface appearing to be "stuck" when navigating Additional fixes for launching games Corrected issue where the Download Metadata and Media tool would download a theme video even though you already had one when selecting the "Do Not Replace" option Fixed custom field filter duplicates Corrected issue that required you to restart LaunchBox when adding a new custom field to see it in the Sidebar filter drop down Fixed pack:// URIs Add/Edit Metadata page now uses alternate names to set the region-correct title You can now change the main title of the game from the alternate names page Fixed DPI issues with some windows This beta does not address everything in this thread, but I wanted to at least get out what we had for today. Thanks for bearing with us as we work through these issues that have come up from the .NET Core migration, and thanks for the reports.
  20. This isn't true either. The pause screen does work with some exclusive fullscreen mode emulators, and just because a game uses exclusive fullscreen does not necessarily mean that it won't work with the pause screens.
  21. Thanks all for the testing and feedback. Beta 2 is out now with the following: Fixed all known cases where folders weren't opening and/or games weren't launching Fixed column visibility not sticking with the LaunchBox list view Hopeful fix for LaunchBox plugin issues (tested with Steam Scraper and YouTube Scraper plugins) Fixed EmuMovies credentials being forgotten Fixed Epic Games importer not showing any games Made the Region and Image Priorities check box lists less confusing to use (selection vs. checking) The setup now prompts you to download and install .NET Core 3.1.6 if needed Hopefully this will address most of the issues. Apparently with .NET Core, you can distribute it so that it does not require the framework to be installed, but it requires separate versions for x64 and x86, and would require an extra 100 megabytes on top for the download, so we've decided to not do that and just prompt users to download and install .NET Core if needed during the setup.
  22. Thanks for the reports guys. I know what the plugin issue is and I can get it fixed and into a beta tomorrow. I'll look into the other issues as well.
  23. The first 11.3 beta is out here:
  24. Hey all, the first 11.3 beta is out now with the following: New Feature: Alternate names are now downloaded from the LaunchBox Games Database when importing or downloading metadata for your games, and they are editable in Add/Edit New Feature: New fields have been added for Max Players, Release Type, Video URL, and Wikipedia URL, downloaded from the LaunchBox Games Database when available Improvement: LaunchBox and Big Box have been upgraded to .NET Core 3.1, which brings with it many advantages, such as no longer requiring a .NET Framework installation, better performance, increased security, and potential cross-platform support Improvement: The LaunchBox options screen has been overhauled to remove the "legacy" portion and organize everything much more cleanly Improvement: The Installed, Games Database ID, Application Path, Max Players, Release Type, Video URL, and Wikipedia URL fields have been added to the LaunchBox list view Improvement: Date formats should now more closely reflect the Windows settings Improvement: Using custom fields in the sidebar now supports multi-string fields similar to Genre and Series Improvement: Plugin developers can now perform a search in Big Box using PluginHelper.BigBoxMainViewModel.Search(string query) Fixed: Rare image cache reading error Fixed: Screenshots pulled from GOG were sometimes cut off Fixed: Some games imported from GOG were not using DOSBox correctly The .NET Core 3.1 upgrades are a relatively big deal, and a lot of work went into them (and basically everything needs tested as a result). There is one known issue with this beta: the new Release Type field is not currently downloaded from the LaunchBox Games Database on imports and metadata updates, but the rest of the fields are. Let us know how this beta fares.
  25. I have a feeling that something is wrong with how your collection is configured, but it's really hard to figure it out without seeing it and your media. My best guess would be conflicting folders or something of that nature. Big Box should randomly pick from the highest-priority available videos as you browse your collection, but yeah, there's nothing in Big Box to show all the videos at once at this point.
×
×
  • Create New...