loggin

after finally being able to connect to my nas I am unable to navigate folder structure using a remote or controller, no touch interface is possible

ok got this sorted I had to enable legacy support for windows within the network settings on the nas, guess the app is reliant upon wins/netbios names

aarrggh, finally giving this feature a go and launchbox is just seeing my nas where the mounted, it sees the other nas and windows devices, just not the location where the games actually are. the only potential clue I currently have is the file xplore app on both my fire sticks don't see the nas's host/share name, yet other devices seem to be fine with seeing it (phone and windows)

sorry to necro but rather than starting a new post I'm wanting this answer so I can load a custom config per platform to load in my bezel packs on an android tv device, can't find it under the emulator settings when long clicking (pressing) on the platform in game list view

Ok so I thought, let's copy the new games.yml in config folder to the root folder and now I've got my newly added games so launchbox is defintely expecting it in the root folder. I probably ended up with two games.yml files as I most likely did a rollback on rpcs3 versions and then when finally going forward any cleanup process didn't run as I had a copy in config already.

I've removed the one in the root already, RPCS3 is carrying as normal and launchbox is still not finding new games, haven't tried a detected removed rom as yet for obvious reasons and probably won't till it's importing again

Launchbox isn't loading any new games added to RPCS3, has the games.yml moved location as I've noticed I have 2, one in the apps root folder which hasn't updated since February 2025 and another current one now in the config folder

solved, some of the directories had double spacing in, obviously launchbox doesn't like this

kinda got a similar problem but it's only for some of the games (some launch, some don't), I've checked and they start in retroarch but doing nothing when trying to open from launchbox, not zipped as have .neo extension and the option isn't checked anyway

The title basically says it all, I got the update a week ago and it is a vast improvement, previously struggling to get my large libraries to load but now no more crashing, just one minor issue the icon on the panels to select the launchbox app is not loading or completely missing. This is on a Fire TV 4K Max stick.

Think I had a bit of an amalgam of issues, one game appeared to be multidisc (several eboot.bin files inside the directory structure) and wasn't even loading into RPCS3 so I removed that and rolling back to an earlier version got it to load all my disc games

Maybe not, after finding out it created a load of dupes for those with entries in the hdd folder as well as disc images I decided to delete the library and reimport and now I've only got half my titles

Fixed it, so I did a couple of individual game imports, this then set the Platforms game folder to one of those games which it then tried to import some of the files inside it as individual games, so figured I needed to sort that and upon resetting the game folder it imported all my other missing titles

So I've been merrily importing my PS3 game library without too much hinderance but the latest batch has had a few missing titles, so want to garner some knowledge about the best way to resolve this, currently I'm thinking I need to individually import the missing titles from the Disc Game folder, but believe that was problematic since the automatic importer was implemented. Also I had 3 titles pop up during a scan (after 2-3 scans of not finding them) and only one of them was added to the library so suspect there maybe more at play. What I have noticed is that some (not checked all) do not have a folder within the /dev_hhd/game directory or if they do do not have an EBOOT.bin within their folder in this directory. So ideas, what's probably gonna be the best way to resolve these missing titles ? They are appearing in RPCS3 game list and in some cases after allowing them to launch and do their thing (install) launchbox then finds them.

Cool thanks the Associated Platforms was everyone and his son, once I sorted that it started working