p bizzy

Have you tried it with the roms or emulators going through a symbolic link? I am not the first to report that on this thread. It is useful for external HDD's that move between systems.

Probably, but I like the relative pathing for portable use. But now after 13.19 it doesnt work, so im stuck on 13.18. I wonder if just the current working directory needs to be set since I did see some updates to the syntax for .NET9

Anyone able to replicate symlinks still not working? This would mean either I would need to stay on 13.18 -- or move my launchbox instalation off the NVME to the HDD where my rom rom collection is, which would probably offset any new performance improvements and then some.

Exact same issue, only going back to 13.18 fixes it.

Darn, was hoping the UNC paths fix indirectly nudged the relative paths issue I'm still having. Does no one else really use relative paths and seeing the games/emulators as now unavailable after the beta update? I was able to re-produce on a fresh out of the box Legion Go and add 1 game. By the way using 'add folder' when importing new roms uses relative paths by default.

I can if needed, but shouldn't be necessary (plus its over 80k collection and quite a bit to sift through 😆). I installed beta3 on a fresh-out-of-the-box Legion Go gaming handheld and added one rom and it had the same issue, so it shouldnt be something with my particular data. Should also note that by default the 'add folder' function when adding roms does relative paths by default so I'm miffed no one else reported it yet, made me think I might be looking at something wrong 😄.

That's true and I get it. But its advertised as a portable application and I use it explicitly as such, so relative paths are still the best for my use case.

I'm guessing it's not related to relative pathnames. You needing to uninstall a redistributable might be a clue. The new beta builds .NET9 into it, so no need to install any extra redistributable to make it work. It probably isn't the redistributable, but not sure what else to try. I installed 13.19-beta3 and the problem returned right back, and other apps are accessing relative paths fine. Every single emulator and rom are unavailable until I edit details and update paths to an absolute path.

I had an issue where none of my roms or emulators were found (I believe) due to me using relative pathnames (like "..\games\game.rom" ). I had to reinstall 13.18 *and* uninstall the lastest redistributable before it worked again.

Now that there is a new beta with search filtering -- also wondering about this...

And second/third level tree view indentations for the side bar if you get a chance, please. ?

I have also had issues with multi-select and then trying to subsequently making another selection from the same platoform later and it not making the correct 're-selections'. I never put together an exact way to replicate it as it wasn't 100% so I didn't report it yet, but it definitely exists. The workaround is to switch platforms and come back to it for selections to work proper again.

Hey @eXo, maybe relevant to your interests, maybe not: https://tech.slashdot.org/story/18/06/05/2130254/70-long-lost-japanese-video-games-discovered-in-a-67gb-folder-of-roms-on-a-private-forum I see they are being uploaded here for the first time (not all there yet), and some of them are Windows 95 CD-ROMs such as the long lost Labyrinthe sequels the article mentions: https://archive.org/details/@philsalv

This reminds me of this bounty -- http://www.rlauncher.com/forum/archive/index.php/t-5076.html?s=7eae2ed1e3db2c730f3fe356a57d2c60 Using the retroarch version of dosbox seems like a good solution to this if it could mount just using the config files but the current structure doesn't seem to allow that. This would allow for other cool things such as auto-controller config and rewind, too. Maybe someone knows a better way and can cash in on that bounty

Could we do 2 letter jumps (or more) for those of us with large collections? I know this is technically a feature request and this thread is for feature parity, but thought I'd try as it may be easier to nip this when you're already delving in this particular code