dragon57

Just fyi, if you ever want to disable a full set of Retroarch bezels, go to the ...\retroarch\overlays\GameBezels folder and rename the appropriate subdirectory to something other than the existing named directory.

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

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.

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.

Since not every user is having EmuMovies issues (mine works fine, for example), have you tried contacting the admins on the EmuMovies forums?

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.

My Attract Mode+ installs thank you from the bottom of my heart. My one remaining LB/BB install as well!

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.

I think you can email support@unbrokensoftware.com and request a link to one.

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.

Excellent! That pic nailed it and fixes so much we will never understand.

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?

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.

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?

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!

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.

Are you using LaunchBoxes startup theme option along with Rocketlauncher? If so, that will not integrate well. You would need to disable the Launchbox option and use the native Rocketlauncher startup theme launcher.

Have you tried changing the Sidebar font in Options?

I just tried Dreamcast on my new Windows 11 laptop using Retroarch and its Flycast core and my Dreamcast chd games boot right up with no issues. Your results are quite strange, I just say. Do you have the Startup screen option set in Launchbox? If so, that might be masking any errors you may be getting. You didn't specifically say you tried this in Launchbox. If you haven't, try it there and see how far you get. I would be happy to assist if I can.

Damage, have you listed those things out already, other than Shredder's first post, or is that basically it? If so, I must have missed them in the past, so point me to the post. If not, list them here and I'll try to answer your question. I'm not trying to be vague on purpose. At the time of my decision to drop RocketLauncher, I didn't have a set todo list of items I wanted to extend in to, but if I had decided to stay with RL, I would have just taken things one by one until I was satisfied. Honestly, my decision to switch over to LB fully was because the RL devs stopped responding to the forum, direct contact, you name it. While a couple of users on the forum tried to support with updating modules, it just wasn't enough, plus no source code was released from the RL devs. Shredder, as far as the 'extra' folders getting created under certain conditions, if that is a hard line in the sand, then you will never be happy. This has been mentioned quite a few times in the past, and the devs seem open to changes IF enough support exists from the majority of the user base (we all vote around once per year). You can request a feature under the Help & Support area at the top of the page here on the forum, but I am almost sure there are requests for this already. Again, it is a matter of agreement from the user base.

I'll add my experience converting from Hyperspin and Rocketlauncher long ago, for what it is worth. I also was a big Hyperspin/Rocketlauncher user and supporter back when those developments and forums were active. Like many here, I tried the free version of Launchbox and saw promise. As Launchbox matured, I decided to switch. I continued using Rocketlauncher by following the Launchbox and Rocketlauncher integration info from the Rocketlauncher forums. While this did work after editing platform names on the Rocketlauncher side to match what Launchbox used as standards, I eventually moved away from that approach as Rocketlauncher stopped being developed and supported by the devs on its forum. Moving away from the old environments to a total Launchbox/Bigbox one has been overall very satisfying. It does take time to adapt, but that is the way of things in any world requiring certain applications to support a particular task. I have been an application coder since 1981. While I could continue to extend and develop myself in supporting my old Rocketlauncher installation, I decided anything I developed would probably be specific to my needs and not necessarily useful to anyone else. To me, asking for Launchbox to extend support for a dead application isn't productive for the vast number of Launchbox users, and I understand why this was never done. I would recommend joining in the forums here, be patient as you learn and use the products here and have fun gaming.

<launchbox installation folder>\Data\Platforms. The file is most likely named Sony Playstation.xml or something similar.

What I did when I performed a conversion like that was to exit LaunchBox/BigBox, then use one of those text editors like Notepad++ to mass edit the appropriate XML file.

Everything in the chain should match naming wise, so I would rename the file in the zip and give that a try. There is no easy way to update things. That bezel set requires a rom set that follows the No-Intro naming standard, so you could try finding a recent No-Intro set and see if that roms work better for you. There should be little to rename, if any, that way.