Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    13,723
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Jason Carr

  1. Maybe. My tablet is on Android 7 though and it works perfectly fine as well. So if it is an issue with Android 7, the issue is specific to that device, sigh.
  2. Yes, I've tested a million times on my G5 and I've never seen it crash. However, my G5 is running Android 8.0.0. Maybe that's the clue...
  3. I see. What file from the archive is it supposed to open on startup?
  4. Thanks guys, I'm currently looking deeper into this. I don't currently have any devices that I can replicate the crashes on, despite having 5 different devices lol. I'm gonna do some further testing to see what else is possible.
  5. @wallmachine Looks like you might be dealing with issues caused by an audio device getting removed or disabled, or something of that nature. I'm going to see if I can make that code more robust in that situation, but if I had to guess based on your logs, that'd be my guess (at least for that one situation and log file). In that case, unfortunately you're dealing with a compromised system, so there's not much we can do to help in that regard unless you can reinstall Windows and get everything working properly. I'm sorry for the bad news on that one. The particular error you're running into is a heap corruption error with the .NET Framework, which is unfortunately a nightmare because it could be caused by anything, and it's probably a bug with a driver, Windows, or the .NET Framework. So bad news there as well, because without a lead, there's not a whole lot I can do. What I would recommend there, is to make sure that you close down any and all apps that could be running in the background (use Task Manager), and unplug any extra USB devices you have plugged into the machine, just to be safe (other than keyboard and mouse). From there, we can figure out if it's still happening or not, and try to pinpoint what might be causing it. Sadly, this one's not going to be easy, but we can probably get it figured out eventually if you're willing to do a little sleuthing.
  6. If that's the case, make sure you don't have it installed to Program Files, or anywhere that needs admin rights to write to the folder.
  7. @Niknice Most likely Redream is just having trouble loading the game, I'm guessing. What's the file extension on the ROM?
  8. Yeah, I haven't really researched this yet, but it may or may not be possible, and if it is possible, it won't be easy. So it's on my list to research, but Android's limitations might get in the way.
  9. Ick. I don't recognize that error code at all. It sounds like somehow something is going seriously wrong on that system, but it's hard to say exactly what it is. Make sure you've given it a reboot and installed all Windows updates.
  10. Have you tried all the suggestions in this thread?
  11. Jason Carr

    Mame

    Hmm, I'll give this a test to see if I can reproduce.
  12. Jason Carr

    Mame

    Keep in mind that a lot of this is completely out of our control. We can't create a log file for Retroarch's crashes. If Retroarch is giving you a black screen, then something could be going wrong with the launch, but it would certainly be nice if Retroarch would say that or log it, instead of just crashing to a black screen. That's something that sadly we can't fix ourselves. I currently have MAME running just fine via Retroarch, and it's working fine with several of the MAME cores and different versions of Retroarch, so I'm really not sure what could be causing that problem. Do make sure that LaunchBox is not set to extract archives for that platform, and of course make sure that the cores are downloaded in Retroarch.
  13. The EmuMovies downloads are not currently threaded. The LaunchBox Games Database downloads are, but we've had many people test it and it significantly boosted speeds, not slowed them down. My guess is that any actual speed issues are likely the result of high traffic.
  14. Keep in mind that you will need the 32-bit version of the APK in order for it to work properly on the Fire Stick, and so you'll need a 32-bit device with Google Play in order to purchase it on that. It's not really an easy process, unfortunately. We'll be putting it up on the Amazon store here soon though.
  15. No changes were made to the EmuMovies downloads at all, so I expect that's either just your perception or just the fact that it's busier because of the Black Friday traffic.
  16. Hi guys, this may be an oversight with the 10.7 release. We'll review and look into it. Thanks for the report.
  17. Sorry for the delay here Polybius; the theme looks awesome. Thanks for submitting it. It's been busy over here for the past couple of weeks so I haven't gotten it tested and approved yet. I'll get started on that tomorrow.
  18. Okay, what folder did you install it to? Can you try re-running the setup?
  19. Hi @Dnet, thanks for the purchase and sorry to hear about the issue. That FileNotFoundException means that there's either something corrupted with the LaunchBox install or something corrupted with the .NET Framework install (most likely the latter). Can you try uninstalling and reinstalling .NET 4.8 from here? https://dotnet.microsoft.com/download/dotnet-framework/net48
  20. LaunchBox on Android currently resembles more of a LaunchBox experience. Big Box type views are planned and coming soon, but not quite there yet. It will export your desktop collection to your device, yes. If you're looking for a sync specifically, though (syncing back and forth), that's not really planned due to the differences between the platforms.
  21. Big Box comes with LaunchBox Premium on the desktop, yes.
  22. Unfortunately the Android version is a separate purchase from the Play Store.
  23. Thank you @Morbidmetal85. That helps.
  24. Sorry for another question, but it helps me get it figured out. How long does it display that loading circle before it crashes?
×
×
  • Create New...