EvoluZion3

Hi @sundogak. I've managed to get it working! Thanks to your very detailed and helpful explanation above, I was able to confirm that that is exactly how mine was set up! I could have taken those screenshots myself (except my installation is on F: not G:). I did have half a dozen or so Vita games on LB, but used the "blank PCSE000xxx text files in the Games folder" method which I believe was previously the best method of anchoring your Vita3K-installed games before LB 13.15 came along. All I can think of is that this has messed with LB's ability to auto-import games for Vita somehow. Even with my system identical to what you show above, LB was not auto-importing anything upon startup (with Auto-import checked), any attempt to drag in either a PCSE folder from ux0\apps as a ROM, or to do a Scan For Added, resulted in unwanted files being identified, but dragging in an eboot.bin seemed to work but Vita3K didn't like it if I tried to launch (without manually removing the eboot.bin from the Launcher CLI). So I deleted all my Vita games from LB so the Platform was removed, deleted Vita3K from the Emulators list and restarted LB, then followed ETA Prime's 13.15 video of how to add Vita3K (as if I'd never had it installed before), and after another restart LB finally worked its magic! Thanks for persisting with me on this one. Damn LaunchBox and its community are great!

Hi @sundogak, thanks for your response. Sorry I don't understand where the empty directory would be. You mean create an empty Vita directory under Games and then run the Scan for Added Vita games? Also, can I ask, what the Launching command line looks like for a successfully imported game? Does it point to the relevant eboot.bin file, or does it point to a dummy PCSE000xx text file, or anything else?

Hi. Is there a European equivalent of the Sony Playstation Vita.xml file? Or instead is it possible to convert a PCSB/F ID to a PCSA/E ID? My games are all PCSB and PCSF.

I posted in the 13.15 thread but thought it best to post here - I'm still having exactly the same issue as Nocta here - games are installed into Vita3K, but when I scan for added games it returns all the files from within the PCSE00xxx folder, sound files, image files, level XML files, all sorts. I'm on 13.16 release version now with the same issue. I thought I'd got to the bottom of the issue because I happened to click Edit on the Vita platform itself from within LB, and saw that the Games directory was set to Emulators\Vita3K\ux0\app\PCSE00xxx. It'd gone into one of the games subfolders. I removed the PCSE from the end and retried, but same issue. In fact it's re-added the PCSE folder onto the end of the path again.

Hi @AstroBob. Not a problem! No I don't have any symbolic links, all game files are there in their respective platform-named subfolders under Games, as per recommended. Yes a few of my games are in subfolders inside their respective platforms (example: Atari ST, Amiga), and a large proportion of all other ROMs are 7zipped or zipped. Actually I did tell a porky earlier on - the ExoDOS and ExoWin3.x projects are in their own "eXo" folder under LaunchBox, which contains emulators, utils, etc. as well as the games. To be honest, it's not very often I need to scan for added ROMs any more, so am happy to mark this one as "to be solved at some point in the future"

Same again - 22 hours later it did a long scan of a different platform first (Fairchild Channel F), then quick scans after that.

Hi @AstroBob, I've reopened LB for the first time since I last posted, did another Scan for Added Jaguar CD ROMs, and it took 284 seconds (I counted them!). Did a scan on two other platforms, and it took a couple of seconds. It does look like it's doing a full scan the first time you do it after (24/48?) hours, but I wonder if it's necessary seeing as normally you would only be scanning the specific platform's subfolder...

Hi @AstroBob, here's my answers: What LB version are you using? I'm assuming the latest 13.15? - I think the issue might have started around 13.14-ish, but persists with 13.15 and even 13.16b3 (I have another issue around PS Vita imports and C-Beats advised I try the beta). Is your `Games` directory located within your LaunchBox directory, or is it stored somewhere outside of this location? - It is immediately inside the LaunchBox folder, yes Do you experience slowness when scanning for additional ROMs, even if there aren't any new ROMs present? Or is it only when there are new ROMs present? - yes even if there are no new ROMs present it would take a long time Are there any differences when scanning for different platforms? I'm assuming not, as you mentioned it's still slow on platforms with a small number of games, but would be good to confirm - please see below... What is your total game count roughly? - 50k Finally, to completely rule out any version issues, if you update to the latest beta (currently 13.16-3) do you experience the same issue? - yes am currently running 13.16b3 with the issue Interestingly, after running a Scan for a platform at random (Jaguar CD with only 14 games - and it taking approx. 3 minutes to complete, with no results as expected) when I go to scan another platform, it finished almost immediately. When I scan Jaguar CD again, it finished almost immediately. So it almost looks like the first scan takes an unusual amount of time. It does say "searching for additional ROMs" with an active progress bar during the 3 minutes or so. I have tried closing LB, making sure it is definitely closed, reopening and rescanning Jaguar CD, and it was immediate again. Perhaps tomorrow (or whenever there's a metadata update?) it'll take an initial 3 minutes again... I've added a reminder to try this again in 3 days time, and post back here.

I've updated to 13.16b3 but still have the same issue after scanning for added Vita Roms. I've tried deleting the Vita3K emulator and re-adding it.

Same issue here with LB trying to import every single asset from the Vita3K ux0\app folders. 2,084 "games" across 10 actual installed games. Surely it's only supposed to be looking for eboot.bin files? EDIT - I am doing "Scan for Added PS Vita games", I'm not using auto-import.

Since maybe the last couple of versions of LB I've noticed that performing a Scan for Added ROMs (just for a single platform) is taking ages (several minutes) whereas previously it'd only take a few seconds. It even takes several minutes when there's literally only half a dozen files in the folder. It's as if it's scanning the whole drive for added ROMs, not just the \Games\platform subfolder. Is it just me?

@lou silver thank you for the amazing work you have put into this project. I have a question about the LB Platforms XML in that the .fpt files seem to be in subfolders which don't exist/are named differently in the dump of tables I managed to source. For example: XML says: <ApplicationPath>Emulators\Future Pinball\Tables\commander_keen-table_2_0\Commander Keen (2.0).fpt</ApplicationPath> File location in the torrent (once I've extracted the zip) is: \Commander Keen (Mark1)(3.0)\2.0\Commander Keen (2.0).fpt Is there a better torrent which aligns to the naming convention of the XML, or is there an updated XML which matches the naming in the torrent?

Hopefully one for 13.13 then thanks for your suggestions, I'm sure a solution will present itself soon.

This ought to be obvious but I can't find how to only move the files. Apologies, which menu option should I be using, "Change ROMs Folder Path" or "Export/Copy ROM Files"? Neither of them ask whether I want to move only. I'm on LB 13.12.

Thanks for your suggestion. Only one of the ROMs had an additional app so I'm happy to proceed, however when I select all the games and click File Management, I'm a little confused because I can only either: i) "Change ROMs Folder Path" which won't move the files, only repoint them to a new folder where they won't exist, or ii) "Export/Copy ROM Files to New Folder" which will create a copy of all the "genuine" ROMs in the new folder, leaving me to manually identify the extra ones in the existing directory amongst the originals. I suppose I could use a folder comparison tool to do this. Or option iii) would be to Export/Copy to a new folder, then Change ROMs Folder Path, then delete all files in the original folder, then Export/Copy back to the original folder, then Change ROMs Folder Path back to the original folder. This should fix it but seems a long way around (plus I won't be able to identify the rogue ROMs and have a look into why they won't import in the first place).