Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    13,723
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Jason Carr

  1. We added regions after the fact, and never added support for regions when adding media manually, nor can you currently change the region that is associated with a particular image. Currently, it's all only done through the folders. I do have an item on my list to allow changing and specifying media regions, which I believe would solve these issues. I'm not exactly sure when we'll get to it, but it is on my list.
  2. @Muckers I've seen this issue elsewhere, and just asked what that user did to fix it. This was his response: Can you check to see if somehow Open and Play are assigned to the same controller button?
  3. Gotcha, thank you. I think we may have a similar issue elsewhere, so that helps me tremendously. Many thanks.
  4. @AYOOB What did you do to fix this issue?
  5. @Muckers Do you have startup screens or pause screens enabled?
  6. I'm not aware of an issue like that. Are you seeing that issue too @viking?
  7. @Bob Benson Most likely this is the result of a stray controller or an incorrect controller configuration, and it's also what probably caused the weird stretched frame issue above. Your best bet is to unplug all game controllers attached the system, and then go into the game controller configuration to see what might be wrong. If you have Use All Controllers checked, then that could be the issue.
  8. Hi lucky, start with NES as that's a simple platform to get working. If Retroarch isn't working (giving you a black screen), try first running an NES game in Retroarch without LaunchBox. You will need to download the correct core.
  9. Thanks for pointing this out @e2zippo. We just upgraded to a new server 8 days ago, and apparently the metadata was not updating properly ever since. I'm currently getting it fixed.
  10. Good to know @robnmish. I'll put that on my list of emulators to add here soon.
  11. If games are showing up in LaunchBox on Android, but you're getting a black screen when launching, that's not a storage issue. That's either an emulator or a configuration issue. We'd have to troubleshoot that individually for each emulator/platform that you're running into it with. To remove the unbroken folder from your Shield internal storage, one option would be to hook it up to your computer with a USB cable. That's probably the simplest way. Then you can work with files on the internal storage just like you can with a phone.
  12. Looking awesome @PaDeMoNiuM.
  13. @harryoke I see the issue; the "/" in the name is causing trouble. It's on my list to fix.
  14. Thanks Chunk. I'll look into that extract issue. All those feature requests are planned sans for bezels; I'm not even sure if that would be possible on Android, but I really doubt it.
  15. For the original GPD XD, the Android version is ancient, which means that modern storage APIs do not work properly. I am planning on adding some compatibility code here soon to attempt to fix it, but as for now, because the version of Android is so old, you'll need to stick with internal storage.
  16. LaunchBox for Android looks for the /Android/data/com.unbrokensoftware.launchbox/files/LaunchBox folder on every drive found attached to the device, picks the first one it finds, and uses the data from that folder. So if you put it in the right spot, it should be automatically picked up from any drive (assuming a recent version of Android, but the Shield is fine for that). I'm having trouble following this lol. Can you re-explain exactly what's happening?
  17. Jason Carr

    Amiga

    Unfortunately I haven't tried it yet, but sadly it's probably not going to work for you at this point. Let me know if you figure out a good emulator to use on Android and if you can get it working without LaunchBox.
  18. Looking at the plugin code, I'm not finding an obvious way. I just added a RefreshData method to ILaunchBoxMainViewModel; that will be available once the next beta comes out. It might be a bit before that beta is released though.
  19. Hmm, first I'm hearing of this. Looks like that happens for new/indie games that haven't reached a certain threshold in sales or use. Unfortunately I'm not sure if there's anything we can really do about that. We need the Steam API in order to find the games, and if the API sucks (surprise, surprise), I don't think there's much we can do, sadly.
  20. Sure, I'll put this on my ideas list.
  21. Also, we'll be keeping him far, far away from Neil.
  22. Just wanted to announce here that we have filled the position. Details forthcoming. We're currently waiting on the new hire to put in his 2-weeks notice.
  23. I believe there is a DOSBox keyboard shortcut to make it fullscreen. Maybe F11? Or Alt+Enter? Either way though, that keyboard shortcut is intercepted by DOSBox, so the actual MS-DOS code can't do anything with it.
  24. Sorry for the late reply here @terrornoize. I may release the source here soon; I'll github it if/when I do. I'll probably want to tweak it a bit before I do though. Not quite following here @freerunner. This is an MS-DOS app, and already runs fullscreen. If you're referring to making DOSBox fullscreen from within an MS-DOS app, that is basically impossible.
  25. Unfortunately not yet. It is on my list of to-do items though.
×
×
  • Create New...