Jump to content
LaunchBox Community Forums

Vita3K usage...


NagakiriHidechi

Recommended Posts

3 hours ago, Nocta said:

I'm already using the #2, that's why I'm so surprised that Launchbox is going to the emulator folder and getting garbage.

If they are simple text files and not Windows shortcut links (lnk ext) then something is misconfigured somewhere else. LB wouldn’t have any idea where the Vita uxo directory is located otherwise with simple pointer file directory with no sub folders. You would need to screenshot a game screen with link as well as your platform paths for Vita to tell. 

Link to comment
Share on other sites

7 hours ago, Nocta said:

Here is what I get if I scan for new roms for PSVita.
image.thumb.png.8463d1513bafe0cb817cd8243f5d585a.png

Hmm…well very odd.  Somewhat stumped now as the platform folder setting is what the scanning feature is supposed to look at.  I have the same exact setup for Vita on my non auto import setup. The only difference is my emulator folder is outside of LB base directory.  If I scan it is limited to that folder only as you expect. That shouldn’t make any difference on emulator location as paths are seen in both cases by LB. But grasping at deltas only thing maybe to test as something LB is doing if within its emulator folder structure.  Not sure that is likely but out of suggestions beyond that if your auto import setting is off.  

Edited by sundogak
Link to comment
Share on other sites

We've added additional logic to the next upcoming beta that we're hoping to get out very soon that should hopefully address this. If I can remember @Nocta I'll ping ya in the new beta thread when that happens and you can vet out if you see the issue corrected or not.

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

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.

Link to comment
Share on other sites

19 hours ago, EvoluZion3 said:

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.

The difference with Nocta’s situation and yours is you are still pointing to the ux0 directory. Point to completely empty directory (no sub directories).    

Link to comment
Share on other sites

22 hours ago, sundogak said:

The difference with Nocta’s situation and yours is you are still pointing to the ux0 directory. Point to completely empty directory (no sub directories).    

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?

Edited by EvoluZion3
Extra question
Link to comment
Share on other sites

2 hours ago, EvoluZion3 said:

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?

Yes, blank folder or LB will wind up doing what you saw (to me should be some logic to stop this if auto import on but at moment not the case).  For Vita3K and PS3 RPCS3 if using auto import feature LB uses the Vita and PS3 emulators to determine pathing.  Thus it is a "must" to have games installed properly in the emulators when you open them. If not in there then LB will not pick up. 

If you point the folders to the rom folders then LB imports all the other files in addition to what it sees via emulator.  Where the empty folder is located is immaterial but here is mine:

Screenshot2024-09-15122937.thumb.png.2efd34ba63bd7ff821d52e937076fb0b.pngScreenshot2024-09-15122548.thumb.png.f1a69b01cdb293527174b4f752b99b41.png

Here are the other setup screens:

This is Metal Slug 3 path that the auto import feature automatically places. Notice it isn't pointing to eboot file (by design) like the "old" way prior to auto import method. 

Screenshot2024-09-15122627.thumb.png.539e769ea150942e16c5699df6cebcc4.png

The key for that is the switch " -r" which tells Vita to run any eboot file in the installed path  (hence why above game only points to folder)

Screenshot2024-09-15122748.thumb.png.d00dd8481bbca1bdddd26c39ab111661.png

This needs to be checked to have LB use Vita (and PS3 RPCS3 which is similar setup)

Screenshot2024-09-15122832.thumb.png.9e6021dea338189ae2a67a8c3cfe9e55.png

The key here is that for most part you never need to run "Scan" anymore as the auto import will pick it up.  You can and if setup correctly as above it shouldn't pick anything spurious in the folder paths.  Sometimes the auto import isn't immediate but will eventually do its thing (force a scan usually triggers).

Side note (for non-Vita, RPCS3 emulators):  The pointing to empty folder trick also works for platforms you do not want LB to do its normal ROM auto import thing. For example, I have Visual Pinball and do not point the rom folder in LB path to the VP tables or it will auto import EVERYTHING and it is a mess.  Hopefully they will improve this at some point but originally was reason I avoided auto import feature.  

Edited by sundogak
Link to comment
Share on other sites

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!

  • Thanks 1
Link to comment
Share on other sites

28 minutes ago, EvoluZion3 said:

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!

Yeah, during the beta I had the text point method prior as well. I do recall I had to nuke the platform and emulator entries and restart (similar with PS3) but was assuming it was a beta thing.  Glad you got it sorted. 

Link to comment
Share on other sites

  • 1 month later...
On 9/16/2024 at 6:53 PM, EvoluZion3 said:

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!

This works for me too! Thanks a lot! 😀

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...