Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    13,723
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Jason Carr

  1. Hi @ehssan, we are seeing some unfortunate issues where LaunchBox is not allowed to write to SD cards due to the scoped storage issues (thanks for nothing, Google). But as of yet, I have not seen an issue where LaunchBox can't read from external storage on Android 11. However, we've been primarily testing with SD cards, of course; we have tested with USB drives, but definitely not with that specific device. So first off, if you have an SD card slot, I would try seeing if that works.
  2. This is a different issue than anything else in this thread, so it would probably be best to troubleshoot it in a new thread. We have found a few devices that are overly restricted and for whatever reason don't allow apps that are using the old storage model to write to the root of external storage. Unfortunately we don't have a solution to this currently. If we upgraded to the new storage model, it would break a number of things that are required in order to share files between the frontend and emulators, so there may not be a good solution here. One option you do have would be to put your games on your SD card, but keep your LaunchBox folder and media in your internal storage.
  3. Thanks, I have this on the list, so I should be able to add it soon.
  4. Using this link: https://github.com/libretro/RetroArch/issues
  5. We did put some related performance improvements in for 11.17, so it may actually be a permanent fix. Let us know if you see it again.
  6. I would expect this issue to be a bug with Retroarch, because launching a game from a frontend should not affect the achievements at all. Can you report this as a bug to the Retroarch team @GrandMasterLynx?
  7. Responded to your thread here:
  8. It looks like it's still downloading media, based on the log. I would suggest running the "Download All Missing Media" option, which should help here. However, I do believe that most, if not all of these issues would go away with faster storage.
  9. Welp, apparently I was wrong with some of this. Back when I implemented it, I did find a way to filter out to only games, but unfortunately it's relatively unreliable. The reason that Lone Wolf Saga isn't showing up is because it's been categorized under productivity for some reason, instead of games like it should be. It looks like we could also do better at not including non-games by not adding the "Undefined" category. The only trouble there is that any game that doesn't have an explicit games category won't show up. But that is the most likely cause for non-games showing up in the list. I guess really, to do this right, at least for the automatic approach, would be to ignore the fact that some games just aren't categorized properly and expect the games to get fixed instead of catering to the issues. I'll probably do that going forward, and then maybe we can add a manual option to fix badly categorized games/apps later.
  10. Huh, I'll look into this. Not sure why any games/apps wouldn't be showing up. On my list.
  11. Yes, that's probably the case. The other option you have is to just download the license file (it should be attached to that email you received). Then you can copy it over to the device and put it in the root of your LaunchBox folder. We provide three different options in that email in case something doesn't work.
  12. @Vhero Did you get this figured out? Make sure you're clicking that link on your actual device. LaunchBox should prompt you to open it with an app, and if you choose LaunchBox, it should apply the license. The link does not work on a non-Android device.
  13. Good point. Unfortunately though, because of how the Android devices are structured, I don't have any way of automatically pointing from one storage device to another. What you can do though is just copy your ROMs over where you want them, and then run the import on the device.
  14. I have this option on my list to add. Android doesn't make it as easy as it should be though, so it will probably be a while.
  15. Are you seeing issues with scrolling performance? I ask because I don't see any post from you about it, unless I missed it. I'm also not experiencing any issues myself on the Nvidia Shield TV. From what I can tell, the issues are pretty much exclusively coming from slow storage devices.
  16. Yeah, it does look like it's just running out of memory. Less systems and fewer games could help the issue, but it's not guaranteed. From what I'm hearing, it does sound like it's worth upgrading to Android 8. Android 6 is ancient at this point, so I don't even have an Android 6 device to test with currently.
  17. Hey all, beta 3 is out now with the following: New Feature: Added a RandomGame property bind to Platform and Filter views within Big Box for theme developers New Feature: Marquee Image Group has been added New Feature: Marquee video type has been added New Feature: Big Box Marquee Views have been overhauled to help with custom theme support Improvement: Theme developers can now use videos in Marquee Views via the FlowVideo control Improvement: FlowVideo now has a VideoHeight and VideoWidth property that gives devs the size of the video being played Fixed: Errors thrown during Steam Import when importing media Fixed: FlowVideo now correctly changes video when it's DataContext updates Fixed: Epic Games import error due to new API requirements from Epic Games
  18. @Maikel__ Assuming you're running off an SD card (like Vader said above), you should be able to solve it by either running it from your internal storage instead, or purchasing and using a faster SD card. I recommend SanDisk Extreme SD cards.
  19. The MAME import process shouldn't really take much longer than a few minutes, so it's probably worth restarting. What device are you using?
  20. Hey all, version 0.41 is out now with the following: Fixed an issue where the Android platform was not saving changes to the view Fixed an issue where the emulator settings pages were not always loading up the correct value for the Extract ROM Archives setting
  21. One thing I have heard on this topic, is that if you're running everything from an SD card, make sure it's a high-quality and fast SD card. You will definitely run into issues like this if you're running everything off of a cheap/slow SD card. Also, to help with performance, make sure you've used the option to "Download all missing media". Let me know if that helps.
  22. Android games are added automatically on startup, if it's enabled in the options. They show up under the Android platform. But unfortunately, Android does not provide a good way (outside of unavailable information from the Play Store) to determine what apps are games and what apps aren't. So unfortunately, there's no better way to auto-import all installed Android games. That said, yes, I can see how an opt-in option would be a good one. However, you can basically get there already just be deleting any non-game apps from the platform. They should not show back up.
  23. Gotcha, that would make good sense.
  24. Just looked into this. Apparently it's a bug with Fire TV. I found this article here: https://www.aftvnews.com/how-to-fix-missing-or-broken-icons-for-sideloaded-apps-on-amazon-fire-tv/ I was tempted to move the icons around, but that doesn't appear to be the recommended way to do it, so rather than try that and risk messing up other devices, I think we'll just leave it until Amazon can fix that bug. I also don't currently have a Fire TV device to test with, so that would probably not be the greatest idea.
  25. @YDINO @Snap1209
×
×
  • Create New...