Jump to content
LaunchBox Community Forums

dragon57

Members
  • Posts

    1,053
  • Joined

  • Last visited

  • Days Won

    14

dragon57 last won the day on September 4 2024

dragon57 had the most liked content!

About dragon57

  • Birthday July 12

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dragon57's Achievements

128-Bit Self Aware

128-Bit Self Aware (7/7)

631

Reputation

3

Community Answers

  1. Have you seen these? 1440p, but upscale pretty well, plus you can use a number of AI upscalers that do a great job. https://github.com/libretro/overlay-borders/tree/master/16x9 Collections/Nosh01 1440 Plain
  2. Because of the HyperSpin beta being released, a number of changes are taking place on both the HyperSpin site and the EmuMovies side. I would mention your issue on the EmuMovies forum just in case.
  3. Just logging in to the web site isn't enough. That is why I mentioned getting through to an admin on their forums to have their side of things using your EMid verified would be the next step. The way LB connects is purported to use a different way of authentication than just logging in to the EmuMovies web site. A LB dev can correct me if I am wrong.
  4. Since not every user is having EmuMovies issues (mine works fine, for example), have you tried contacting the admins on the EmuMovies forums?
  5. Can you play any games outside of LaunchBox? If you check the dependencies inside of Retroarch for that core, does it agree all the bios files are there and are correct? I once had a syscard3.pce that wasn't the correct one (it had a different checksum value). I had to track down the correct one.
  6. My Attract Mode+ installs thank you from the bottom of my heart. My one remaining LB/BB install as well!
  7. Also, you could try sending a PM to arzoo here on the forums since he is the author of the LEDBlinky software. He may have seen this error before.
  8. I think you can email support@unbrokensoftware.com and request a link to one.
  9. Although I don't have Ledblinky installed, there are a couple of things that might help diagnose things. The error in your pictures says it can't find D:\Launchbox\Games. I assume this directory exists? Have you tried installing an older release to see if the error exists? The older installers should be in your ...\Launchbox\Updates directory.
  10. Excellent! That pic nailed it and fixes so much we will never understand.
  11. Well, I'm even more stumped than I was. I installed a fresh install of TruNAS Scale latest release. I created my initial pool and created a SMB share using Guest access with default settings. I was able to connect from my Launchbox for Android with no problems. I even turned on the option afterward to allow SMB version 1 and that worked too. I am grasping at straws at this point. What version of Android are you running and on which device?
  12. Very interesting. I've tried different shares from a number of windows systems configured different ways, and those all work fine. It must be related to TrueNAS. I don't have a TN setup here, but should be able to spin one up and experiment some. I'll get back when I know more.
  13. NFS on Android is almost non-existent and Google doesn't support it. SMB is much more common and is what you need if you want Launchbox on Android to connect to a share to source/import roms. Are you running the latest version of TrueNAS? I just checked the TrueNAS documentation and SMB1 (version 1) is disabled by default on current builds/versions, so I would think what you have is using SMB2 (version 2). What type of ownership/permissions are on your share?
  14. I finally got around to upgrading Launchbox on my Android phone to test this. Everything worked fine from the share on my Windows server. I then looked at the Changelog for the new Android build, the forums threads and inside the LB app on the phone itself and I don't see any mention of which version of the SMB protocol is supported or required. What I recommend is checking on your TrueNAS server and see what version of SMB it is currently using. If version 1, try setting it to version 2 and try from your Android device again. If you are currently running versions 2, try changing to version 1. Good luck!
  15. This has been discussed a few times here and outside these forums. Read over this thread and see if you can get your setup working.
×
×
  • Create New...