VCC/SDK failed for correct update to 3.4.0
complete
MrDummy_NL
I noticed VCC has not done everything with upgrading to 3.4.0 and still forgot some files. Two times 0Harmony.dll are there, causing a lot red warnings in Unity. Problem: which file must deleted?
But there is more. VCC and SDK need more adjustments to make error-free 3.4.0 update.
Here are my steps and what happens.
Steps:
- Start at 3.3.0 (pic #1 / #2)
- Let VCC update to 3.4.0, you will see the warning. (Which is good) (pic #3)
- After update, ClientSim is not more in list. UdonSharp is still in list. (pic #4) (pic #5)
- Errors can seen here (pic #6)
There are indeed two 0Harmony.dll files, but.... which one must deleted? We don't want see this problem again. (pic #7)
Others say Udonsharp package should removed. https://feedback.vrchat.com/creator-companion/p/old-udonsharp-package-is-not-removed-when-updating-to-sdk-340
- When i delete it from Package (pic #8), VCC is not more showing Udonsharp in list (pic #9). Good?
- Start Unity up.
- it says some packages are missing (pic #10) - in this part Udonsharp.
- Failed to get package and we have still broken Udonsharp (cant add, incompatible, couldn't resolve) so SDK don't know how to fix it EVEN it has already Udonsharp built-in?
And we cannot solve it. VCC reinstall Base 3.4.0 didn't also NOT solve it. (we know SDK has both built-in, should fix it by itself!) and means SDK cannot solve it, neither VCC can solve it.
I repeated steps again and problem stays there. My conclusion is: VCC and SDK failed to fix the problems for us. Even rookie creator don't know what is going on, and we will see more posts on VRChat Discord. Yeah, that is not good.
It's also weird to see why old package Udonsharp is still there (and should removed according other report) but delete it manually makes things only worser.
I strongly suggest make fix for VCC (and also SDK) to fix update problems: must delete one 0Harmony.dll file OR remove correctly old Udonsharp map. Because you can see at screenshots Udonsharp is still in the list. It was not properly removed!
Please make it urgent fix, many people will have problem with updating to 3.4.0, confirmed in my 2 projects with same problems, and i see more reports from others in VRChat Discord.
Thank you very much.
Log In
Momo the Monster
complete
Momo the Monster
needs more information
Sorry for the trouble, thanks for documenting your issues here. Can you try the latest Creator Companion release to see if it solves your issues?
MrDummy_NL
Momo the Monster: Yes, next VCC updates fixed it because it does update much better by handling existing packages in better way. So yeah, thanks!
MrDummy_NL
Why i think VCC and SDK needs adjustments for error-free update to 3.4.0:
- the used packages are already known and are standard part of VCC, so developers can test and verify. There should no problems from 3.3.0.
- As normal creator you're expecting click on upgrade button to 3.4.0 should not have errors in Unity.
I make now some tests:
- New project with World button -> OK
- New project with Custom button -> FAIL, doesn't create.
Errors showed it:
Couldn't add com.vrchat.clientsim@1.2.7 to target project. It is incompatible
Could not resolve package com.vrchat.clientsim ^1.2.x
Did even
UnityProject removing VPM package com.vrchat.clientsim
UnityProject removing VPM package com.vrchat.udonsharp
So it removes both already.
Which means Custom button is just broken. Should fix it or remove it if it's not more needed since SDK has now built-in.
Let's see with project with 3.3.0 (copied from old project), confirmed no errors in log.
- Update 3.3.0 to 3.4.0, confirmed Udonsharp is removed -> OK (at one small project)
All good? BUT WAIT!
Some projects it failed to fully remove Udonsharp package from Packages map. But why? Project is fine at 3.3.0 setup.
Delete Udonsharp map -> can't resolve package again to fix it, error stays there.
Udonsharp already removed from VCC, can't fix it. Must downgrade to 3.3.0 to let it show up. Then i can go back to 3.3.0 without problems and re-install Udonsharp 1.1.9.
When i do AGAIN the update to 3.4.0 with re-installed Udonsharp 1.1.9, suddenly VCC is able to fully remove Udonsharp package.
My conclusion: VCC is possible not recognize correctly some 3.3.0 projects with UdonSharp, and failed in correct delete map and so it cause problems.
It seems VCC developers has not fully tested on existing projects with 3.3.0 because i noticed it works when project is clean build, but not already build projects. Then VCC missed something to make sure it's fully deleted. Not all projects are succesful updated!
There my result of testing. Sometimes VCC can see files and delete it correctly and upgrade to 3.4.0 went OK.
But some existing projects it failed weird enough to proper remove Udonsharp package, and it causes errors in Unity even VCC thinks it's completed.
Even more, if i re-install Udonsharp 1.1.9 in project, VCC suddenly can see it better and is able to fully remove it.
VCC need some detection adjustments and also extra checks to ensure Udonsharp leftovers after delete are not still there. Such extra checks will very useful for some projects. That is why VCC didn't see everything.
====
Oh, i see now why it cannot remove... QVPen package blocked remove package - STILL VCC put in log update 3.4.0 is a success. But that is NOT right! The log showed the main problem why VCC just keep going.
Actually i must say here, there is no problem to remove Udonsharp because it will come back with 3.4.0. VCC just don't foresee it and that is why VCC failed. VCC need an adjust to overrule this part (ignore some Udonsharp red flags) so it will done correctly!
Otherwise you must uninstall all Udonsharp linked packages from VCC first, upgrade it to 3.4.0 then re-install them again. But who will do this extra work? Not really. VCC should be able do it for YOU!
MrDummy_NL
Those are errors after manually delete old Udonsharp map...
Because both VCC and SDK cannot solve it in normal ways, i stay at 3.3.0 and wait for proper adjustment/fix VCC.