[2.0.2] The VRChat Package Resolver Tool does not install automatically
closed
Lusiiky
Hello,
I noticed that the package "VRChat Package Resolver Tool" was not installed automatically, while once installed, it is well written that this package is mandatory and can't be uninstalled.
Is this normal? Is it possible to fix this?
Thank you!
Lusiiky
Log In
Momo the Monster
closed
Closed as the problem seems to be solved, and no further issues reported for many months.
Lusiiky
Momo the Monster: I've tried again, and I can confirm that the problem seems to have been solved!
Thank you.
Fax
interested
Thank you for clarifying the issue, Lusiiky. You're correct, it's possible to add the Base, Worlds, and Avatars SDK without adding the Package Resolver.
We'll investigate whether this is something we'll want to change. Perhaps the Package Resolver should be removable?
Lusiiky
Fax:
For me, it doesn't matter. If VRChat considers it mandatory, then let them leave it... I didn't even find the point of it, but if it does for VRChat.
So I leave you with this problem and don't hesitate to come back if you need :)
Lusiiky
Fox_score
Fax: YES – Make it not only removable, don't force-add it by default at all!
It doesn't work most of the time, only clutters the console, and doesn't have any real functionality in-editor anyways. You can't manage any packages, only update already installed ones.
The name “Package Resolver” is also very misleading, as, again, you can't use it to install any packages, and it frequently fails at re-adding missing packages (especially if they are from a “community repo”).
Please either make it a proper package manager, or stop forcing its inclusion.
Fax
needs more information
Hi Lusiiky! Thanks for the report.
Does this occur whenever you create a new project with the Creator Companion? Could you check if your
Packages
folder contains any packages?Lusiiky
Fax:
Hello,
No, when creating a project, obviously, the VRChat PRT installs well.
It only appears when migrating or manually installing a Base, Avatars or Worlds package.
The projects I use have nothing special in the Package folder before the migration except the basic files "manifest.json" and "packages-lock.json".
Thank you,
Lusiiky
Fax
Lusiiky: Thank you for elaborating.
Could you please confirm that you're on version 2.0.2 of the Creator Companion, and version 2019.4.31f1 of Unity?
By 'manual installation', are you referring to the VCC packages offered through our website?
If so, are you importing them into a brand-new project created through Unity Hub?
Lusiiky
Fax:
Yes, I do use VCC 2.0.2 and Unity 2019.4.31.
No, by manual installation I'm talking about a project created on the Unity Hub for example, then that I perform the migration in the VCC and that I click, still in the VCC to add the VRCSDK Base and Avatar for example in the project.
Lusiiky
Fax
Lusiiky: Oh, that's very unusual! Let me try and write the reproduction steps for you:
- Create a 2019.4.31f1 project in Unity Hub
- Add it to the Creator Companion ('Add existing project')
I'm unable to reproduce your issue. The VCC does not prompt me to migrate the project. Instead, I'm able to successfully add the package resolver.
Could you please clarify if my reproduction steps are correct, or if there's another way to recreate your issue?
Lusiiky