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. There is different functionality specifically for MAME, since MAME requires other files from the set. Currently, you can't export only a small set of MAME games. It exports all files in the MAME games folder. You could always just remove the ones you don't need though.
  2. Exporting selected games works perfectly fine, but it's still copies all MAME files if you try and export MAME. I haven't built the option to disable that in yet.
  3. @dov_EL Let's take your issue to another thread if we need to continue discussing it. I'm pretty sure there's nothing I can do from a development standpoint though. This is indeed a beta thread, so it is definitely for beta troubleshooting and discussion, but I know that back-and-forth banter like this can be annoying to some people. Regardless, I would appreciate it if we were all a little more gentle with our words, because yes, it does cause unnecessary drama.
  4. That's because the issue has nothing to do with any keyboards or keys. It's a glitch with controller button combos in Retroarch.
  5. There are no keyboard drivers involved, other than the standard ones. This issue has nothing to do with the keyboard or the keyboard keys that we are sending. It has everything to do with the controllers. We already figured this out and we know exactly what's going on. Retroarch is interpreting button combinations incorrectly. Again, it has nothing to do with the keyboard.
  6. Yes, that's exactly what we use. We sound those volume down and volume up keys. That's what we've always done.
  7. I'm still confused here.
  8. Unfortunately I'm confused by what you mean. Can you explain?
  9. I'm pretty sure fixing it isn't even possible at this point. It was an issue with all previous releases, and as I've already stated, it's pretty clearly a bug in Retroarch. I don't think there's anything we can do to fix it.
  10. Hi @LeSpank, sorry for the trouble there. Currently, the Android app requires that the platforms are named exactly as expected, or at least that the Scrape As field is populated correctly in your desktop collection. If you edit that platform with LaunchBox on the desktop, and populate the Scrape As field to Sega Genesis, it should work properly after you re-export that platform.
  11. Responded here: https://forums.launchbox-app.com/topic/50926-pause-screen-and-background-music/
  12. Hi guys, sorry for the delays on this. I'm trying to reproduce it to get it fixed, but even if I use the pause screen, the music is resuming just fine for me in my testing. Is it happening for all emulators for you? What emulators are affected? Do you have the Game Shutdown screens enabled? Are they showing up properly?
  13. Thanks @Wanderer189. I don't currently have a good test environment set up for PCSX2, unfortunately, so I can't easily dive in to testing for that emulator. I know it was working previously, but it could be that an update broke it or something. Does it work properly when you press Escape?
  14. No, the desktop interface of Big Box won't automatically be accessible on Android if you start it from Kodi.
  15. Yeah, that seems like it's not .NET. We've seen that issue previously with .NET, but clearly you've tried everything there. Are you running any anti-virus, anti-malware, or security software? I ask because we've seen some of that stuff cause interference in the past.
  16. Wow, sorry to hear about all the trouble. The version of .NET that you need is the .NET 4.8 Runtime from here: https://dotnet.microsoft.com/download/dotnet-framework/net48 Is that what you already tried installing? Also have you made sure that Windows 7 is all up to date with Windows updates?
  17. BlueTooth does work, but we have seen some complications with it for some people. Are you using DS4Windows? If not, DS4Windows fixes a lot of issues with PS4 controllers, so I would recommend downloading and installing that. See if you can get it working that way.
  18. Hi @Fredonneur; to be honest I don't fully understand your issue here, but I have fixed a number of things for the latest beta release. If you can try updating to the beta, it might fix your issue. You can update to the beta release by going to Tools > Options > General > Updates in LaunchBox and checking the box to update to beta releases. Uncheck the box for background updates, and then restart, and it should prompt you to update.
  19. I just put out beta 2; I believe I finally figured your issue out. The controller automation features were not working properly in LaunchBox *if* pause screens were disabled. So hopefully this version will fix it for you.
  20. Beta 2 is out now with the following fixes: Fixed: LaunchBox controller automation features were not working properly in some cases with pause screens disabled Fixed: The new controller mapping features were slightly misleading as they allowed free users to map controller automation features, but they do not work without a premium license
  21. Hmm, by chance, is your LaunchBox licensed? I just realized that the controller automation features do not work if you don't have a license to LaunchBox Premium on the LaunchBox install. I know you have Big Box though, so that wouldn't make too much sense.
  22. Hi Bobby, that issue is specific to the PCSX2 emulator, which doesn't look to be installed properly. You will probably need to re-download/reinstall PCSX2. The new beta is out; you can update to the beta by going to Tools > Options > General > Updates in LaunchBox and checking the box to update to beta releases. Uncheck the box for background updates and then restart LaunchBox and you should be prompted to update.
  23. Okay, I tested your InputBindings.xml and didn't have any issues with exiting games or opening the Pause menu in LaunchBox. Tested with an Xbox One controller and a PS4 controller via XInput, and the PS4 controller via DirectInput. So I'm baffled here. Can you zip up and PM me your entire LaunchBox\Data folder? Don't upload it here for security reasons.
  24. @Android16 Also, if you're willing, do me a favor and zip up and PM me your entire LaunchBox\Data folder. That may help me with the bindings issue.
  25. The bindings reverting thing is definitely something I need to figure out. The code is set to populate the bindings fresh, if and only if the InputBindings.xml file doesn't exist. By chance, are you removing this file? If not, then I need to figure out why on earth that's happening. Per the scrolling delay, I didn't understand that the issue was unrelated to controllers. I haven't looked into that one yet.
×
×
  • Create New...