Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    13,723
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Jason Carr

  1. 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?
  2. 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
  3. 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.
  4. 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.
  5. 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.
  6. Hi guys, I just tested this with the version I have downloaded, and it's working just fine. I guess maybe there's just multiple versions of Dolphin MMJR available on the web? The version that I have downloaded is this one: https://github.com/Bankaimaster999/Dolphin-MMJR/releases It's the latest 11460 version. What version are you downloading and where are you getting it?
  7. Okay, that is certainly interesting. I'm not seeing those issues on devices with similar or lesser performance, so something looks like it's awry. Will look into it.
  8. Yes, these are current known issues with the desktop exporter. All are on our list to fix here soon.
  9. This report was created in the Android section, so I assumed that the issue happened on Android and not on the desktop. I assume that is correct @YDINO?
  10. Currently with the Android importer it's not possible to restrict to certain file extensions, unfortunately. We'll be adding some sort of feature to allow for that before too long though. In the mean time, you might be able to use the desktop exporter to import that platform.
  11. It might help to turn on debug logging in the options and then share some of the log files with me after you get one of the crashes. It may be that it's just running out of memory, or it could be a different bug that I need to look into. It is true though that the device is rather under-powered. It might help to use one of the easier-to-run views.
  12. Thanks guys, I'll look into this here soon.
  13. Unfortunately that currently won't allow you to set custom banners yet. This feature is a priority though, so it will be coming soon.
  14. Thanks, I can replicate this, so I'll get it fixed. Some of the settings are very platform or emulator-specific, so a lot of them don't make sense to set globally (such as the extract archives option). I can see that causing more issues than helping. But yes, changing the view everywhere would be very helpful. I'll add that to the list.
  15. Most likely Android is somehow refusing write permissions to the root of the SD card on the device, but the Android APIs are claiming that the app does have write permissions. Anyways, I still have this on my list to look into and dive in deeper.
  16. Can you explain what you mean by won't recognize them? Are you referring to the import process?
  17. I put this on the list. We should be able to add it here soon.
  18. We do plan to add support for video snaps here soon. Not sure on formats yet, but we'll look into that when we start working on video support.
  19. @Vader I'll look into that issue. To be honest, the Shield is a relatively low-powered device, so we might not be able to get the scrolling to be completely smooth. It might be also that it would help to download any missing media so that it doesn't have to happen in the background. Have you tried running that process to see if it helps with scrolling performance?
  20. Thanks for the note about the icon. Not sure what could be causing that, but it's on the list now. Yes, that should be possible. However, the right stick can already be used to move much more quickly through the collection.
  21. This is because, traditionally, MAME ROM sets cannot be divided up without major issues. This was by design because of those MAME restrictions. There are ROM sets that can be divided up, but most MAME ROM sets cannot because files rely on other files in the set. In the future, we're planning to add an option to ignore that, but the only way it will work in that case is if you have a non-merged set.
  22. Hi @Bodine Grunch, is LaunchBox giving you that error message, or is it the emulator? I suspect that the issue is the commands that you're putting in for the emulator itself, but I can't say for certain without more information. If you can give me a screenshot of the error message, that would be helpful.
  23. Yes, it works well on the Nvidia Shield TV.
×
×
  • Create New...