cscottbrown

@C-Beats Nice one! I can confirm this was the culprit. I cut config.yml from the Vita3k folder, opened LB, added the Vita3k emulator, closed LB, opened LB again, waited a few minutes, and all Vita games auto-imported as expected. Moved the config.yml file back to the folder, and everything's good. Thanks!

@C-Beats I'm assuming you mean Vita3k's config.yml file? If so, it's attached. config.yml

Thanks @C-Beats, I appreciate the troubleshooting assistance. And no, I am running LB locally without administrator privileges. I am running it from a partitioned drive, although I doubt that would be the cause of this. Also, just as an FYI, importing other ROMs for other systems works fine. Atuo-importing also works fine. It's just Vita that seems to be the problem.

I am confused by this request, so I just screenshotted both sections you seem to be referring to

Same result as last time. The Import Wizard listed no games as being imported and then added the Vita3k emulator and the PlayStation Vita platform but connected zero games.

Let me try the process again and tick the "Force Import Duplicates" option. For your second question, yes: the PlayStation Vita platform is listed (I mentioned this in the previous comment) and it lists zero games. I'll respond again in a sec once I re-try the process.

@C-Beats Hi there! I did my best to follow your instructions. I decided to try and import an eboot.bin for an actual PlayStation Vita game. I've included screenshots of the significant steps here so you can see them. However, when I got to the point where the Import Wizard would list out the games, there was nothing listed (see screenshot). So the steps where I should have selected and deleted the row weren't possible. I pressed forward, though, importing an empty list. When I did so, LaunchBox did its usual thing of querying the LB database and "importing" the game. I then shut down and restarted LB, and waited five minutes. In the end, nothing happened. There was no PlayStation Vita game added, but there is now a listing for Vita in the Manasge Platforms list and a listing for Vita3k in the Manage Emulators list. Let me know if you want me to re-try this under different instructions/circumstances.

Thanks for the fast reply @AstroBob. Here are the answers to your questions: I have confirmed that Enable Automatic ROM Imports is checked in the Automated Imports section I have confirmed that the Sony PlayStation Vita platform does not have the Disable ROM Auto-Imports setting checked Vita3k is installed in the LaunchBox folder under "Emulators>vita3k." This is where I keep all my emulators. Screenshot attached. I have ZIP files of my PS Vita games. I open Vita3k and go to File>Install .zip and find the appropriate ZIP file and install it. I have attached a screenshot of the games folder for clarity. Let me know if you need anything else!

I have Vita3K installed properly with a bunch of games in the "ux0" folder. All have been left alone, so they should match perfectly with games. However, when I follow ETA Prime's tutorial for the 13.16 release, it doesn't import any of the ROMs. Vita3k is added to my emulators list just fine, but even with automatic ROM importing on, the ROMs never actually import. Is there something I'm doing incorrectly? What exactly was fixed in 13.19 to make Vita imports work again? What was broken before? I'd love to have my Vita games in LB, even if it means using some workaround method, but everything I find online doesn't work.

Sweet, thanks for the additional input @Fursphere! Seems like I don't need to overthink this too much. I'll mark this as answered!

Thanks! I'll leave this thread open for a bit in case anyone else thinks of anything. If not, I'll mark it answered.

I have Launchbox installed on my laptop in a partitioned drive. It is fully portable: all the Launchbox files are in there, as well as my emulators and ROMs. I also just built a gaming PC. I'm going to use SyncThing to mirror all the files in that Launchbox drive on my laptop to a drive on the gaming PC. That way anything I do in Launchbox on my laptop should be mirrored on my gaming PC, and vice versa. This will allow me to play a game on my laptop, save it, and then pick up right where I left off on my gaming PC (or the other way around). However, my gaming PC and my laptop have different specs. They also have different display resolutions and will have different controllers connected. This means I will need NOT to sync certain things. For example, I intend to tell SyncThing not to sync the config files for each emulator, so those files alone are independent of each machine. Theoretically, I should be able to update the emulator from either machine and not change its config file on the other, cutting down on maintenance. My question is, which Launchbox files should I also not sync? Are there any Launchbox or Big Box files that shouldn't carry over when being mirrored like this? Any insight into this that will save me headaches down the road will be most appreciated!

@Kiinkyfoxx this worked! It was that forceful pause screen check. Unchecking that did the trick. Thanks so much!

Thanks! I had found this tip in my searching before posting this thread, though. What this does is spread the emulated game across multiple monitors, which would be a fine fix for this if you don't have multiple monitors. I do, and it spreads the game across them, which makes it unplayable, so this method didn't work for me What's weird about this whole problem is that it only seems to be me. I can't believe that no other LB/BB users out there don't play PPSSPP games and use the Pause screen. I just don't know what's weird about my setup, as it is all pretty standard as far as I can tell. But something must be off.

First, thanks for the fast reply. You're right that this does fix the problem, although it is a bit "ugly" since it flashes the screen with a command window and then goes back to fullscreen quickly thereafter. So it works, but it's not ideal. I'm going to leave this thread unanswered for a bit just in case someone else can chime in with what the actual problem might be so I can avoid this workaround fix. But if no one else chimes in, I'll mark this as answered with this hack. Thanks so much either way!