Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    13,723
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Jason Carr

  1. No problem Claudio, updated it for the next beta, which should be out later today. Planning on this one being the last beta before release.
  2. Thanks all, this bug should be fixed in LaunchBox.Next; the next version will be coming out in a few days, and .Next will be feature-complete.
  3. Yes, it could be fixable by editing vlc.cfg. Nothing has changed on the Big Box stack at all recently with videos, so I'm guessing somehow something changed on your system. VLC is used to play music, so I'm guessing that's probably why it's still happening. Maybe see if you can find instructions on completely removing all versions of VLC from your system, including settings?
  4. Was it the reboot or the anti-virus that fixed it?
  5. @Mithrot Try rebooting the machine and temporarily turning off any anti-virus. Is that LaunchBox or LaunchBox.Next?
  6. I've increased the default dead zone in order to better combat this for 360 controllers with loose sticks. In the future, we'll probably add custom dead zone options, but for now, this should do it. It's now set to the same dead zone that OG LaunchBox had. These changes will be in the next beta (8.4-beta-18), out later today or tomorrow.
  7. Beta 17 is out now; thanks to @neil9000 we've discovered that the remaining crashes in .Next were being caused by game controllers (or the game controller code), at least for him. Still confirming with @Zombeaver and @Retro808 that their issues are the same. This beta adds some more logging related to game controllers so that we can better troubleshoot it going forward. There's also a minor controllers fix that might resolve some issues.
  8. Are you scrolling with the mouse wheel or a game controller?
  9. Hopefully things will be a lot smoother once the background caching completes (as noted by the progress bar at the top). Are you scrolling the whole time in the All view in that video? Or just line by line?
  10. @ichimitch That should just about cover it, though you may be missing some DirectX libraries if you only have DirectX 11. Make sure you have every DirectX library ever (you'll need them for emulators anyways). This should include all of them: https://www.microsoft.com/en-us/download/details.aspx?id=8109 Also, you'll need to make sure both Big Box and LaunchBox separately are configured to use VLC instead of Windows Media Player, as obviously Windows Media Player won't be included. Running Big Box on ancient hardware isn't going to work out very well, but I am interested to know if you successfully get everything running on WinPE.
  11. Thank you guys; sorry if I came across a bit blunt. I'm just neck-deep in debugging this difficult to reproduce crash that Zom posted above, and I'm more interested in fixing the bug than other things that will set me back.
  12. I may come back to this at a later date, but as for right now, I have more important things to worry about than the file count on the beta releases.
  13. That is correct. It should be out later today.
  14. Sure, I can add that here at some point. You should be able to disable controllers in .Next in the mean time (which is isolated from the Big Box option). What controller are you using?
  15. Thanks for pointing this out. Added it to my list. @jabrick I can confirm that the issue is not having write permissions to the LaunchBox folder without administrative access. You'll need to enable write permissions on the LaunchBox folder, and let it propagate to all subfolders and files as well. The process will be similar to this: https://www.laptopmag.com/articles/take-ownership-folder-windows-10-using-file-explorer
  16. Thanks again all, I have the translations in for the next beta, which should come out either today or tomorrow. We're finally nearing the release, as it seems that the major bugs have been fixed.
  17. Thank the Lord, I already have confirmation from @Retro808 that the stability issues seem to be fixed with this beta. Do let me know if anyone else is experiencing any crashes. I understand your request here, but I've already confirmed that the logging does not impact performance in any noticeable way (it does I'm sure but it's not noticeable). It's also worth noting that if performance is your focus, the betas are definitely not advised. Beta releases are just that, betas, and I don't recommend using them as your daily driver unless you're up for some occasional issues and you're not concerned with getting the best possible experience. Because you won't.
  18. Beta 16 is now out, with some hopeful fixes for various issues. To be honest, some of these bugs have been truly nasty to fix; I'm having nightmares hearkening back to the days of the Big Box VLC stability issues. Anyways, here's what I've changed/fixed for this beta: Added LaunchBox.Next support for "minimize on game launch" and "restore on game exit" options Fixed LaunchBox.Next side bar combo box and search box not sizing properly for custom fonts Added significant debug logging information for .Next window events (to provide better debugging information for freezing issues on some systems) Changed the debug logging to use a timestamp instead of a GUID in the file names (for easier navigation in debug logs) Forcing debug logs to be enabled for all beta versions (see below) Added a missing, thought-to-be-unused DLL reference, which could possibly be causing the stability issues (though that's a shot in the dark) As described above, I've made some minor changes to the debug logging system, as well as force-enabled it for beta versions. This means that a new LaunchBox\Logs folder will show up that logs various debugging information that can help when troubleshooting things like crashes. Each time LaunchBox, Big Box, or .Next are started up, a new file will show up in the LaunchBox\Logs folder with a timestamp on it, so you can easily find the latest file. In the future, if you experience a crash with a beta release, please post your debug log file here in addition to any other error messages that you have. Thanks all, please let me know how this beta fares; specifically, I'm most interested in any crashes that you get.
  19. Unfortunately the issues that I'm working on having nothing to do with having a 4K monitor. I wish it was that easy lol. Great to hear.
  20. Awesome to hear. Very excited about a notifications API thing.
  21. It's not over $20. He got the $20 back. It's over $0.
  22. You do whatever you wish. You've been refunded. Good day.
  23. Your purchase has been refunded. I have not found any other purchases of yours other than the $20 purchase, so I can guarantee you that you have not been charged for any additional purchases.
  24. I'm sorry we couldn't help you. I will refund your $20 purchase. If you did make a purchase earlier, please let me know the email that you used and I will refund that one as well.
×
×
  • Create New...