VPM project upgrade fails on Linux
SophieBlue
It says it works fine, but the new project has most of the SDK in the Assets/VRCSDK folder, which causes conflicts with the SDK that's now installed in the Packages folder. This makes the project unusable.
As a test I migrated another copy of the same project using VCC in Windows and that worked just fine.
No idea if this will format right, but here's what I've got after migration:
$ find . -type f -name VRC.Dynamics.dll
./Assets/VRCSDK/Plugins/VRC.Dynamics.dll
./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/VRC.Dynamics.dll
Yes I'm using version 0.1.12.
Log In
D
Docteh
What happens if you delete Assets/VRCSDK? I'm assuming you've got your backups in order of course.
SophieBlue
Docteh: Ignoring for the moment the part where a user of such a tool should not have to do this, and the final message from VPM is "Successfully migrated", if I delete that directory
before
opening the project in Unity, yes, that does actually seem to result in a successful migration.So I guess it's actually usable.
D
Docteh
SophieBlue: as far as the tool is currently programmed, it thought it did a good job. Your GitHub issue will help the devs make the tool do a better job for future users.
ChromeSky
Huh, I was wondering why my test project is totally broken after migrating it.