vrchat-community / creator-companion

The Entry Point for Making Things in VRChat
https://vrchat.com/home/download
60 stars 424 forks source link

[BUG] VCC won't convert project from 2019.4.31f1 to 2022.3.22f1 #487

Closed SourceTheProto closed 4 months ago

SourceTheProto commented 4 months ago

Describe the bug

I was trying to convert one of my older projects to the newest unity version, however it fails almost instantly, giving the error message "Trying to Check Changes for an unsupported project, you should not have gotten this far!" seeming to even fail before it starts the migration according to the logs Screenshot 2024-05-20 200034

Also, a weird detail that may be causing the issue is that VCC reports the project type as unknown, although I don't know why it would be labeled as such Screenshot 2024-05-20 200603

To Reproduce

  1. Click the Unity version upgrade button on the project
  2. Select 2022.3.22f1 as the version to migrate to
  3. Click the migrate button, then "Migrate in-place" when the confirmation dialogue appears
  4. Errors show saying migration failed

Expected behavior

I've previously upgraded projects from 2019 to 2022.3.6f1 before, but the only project i've upgraded to 2022.3.22f1 successfully before this was one that was already on 2022.3.6f1, and I had no issues with that one.

Screenshots

No response

Related Product

VCC (VRChat Creator Companion)

Product Version

2.3.1

OS

Windows 10

Additional context

I would just like to clarify that I did try googling first to no avail, and the weird project type and error message seemed appropriate to post here.

orels1 commented 4 months ago

Hey! Project type unknown won't be able to be converted, that's correct. Unknown usually means that there are no worlds/avatars sdk packages installed in the Packages folder

Can you share the list of folders inside your project's Packages folder? Also, what is this project meant to be? A world project or an avatar one?

SourceTheProto commented 4 months ago

Oh yeah it does appear to not have the SDK packages installed somehow, it was supposed to be an avatar; here are the screenshots of the packages folder and the manage project page: packages manage

I re-added the packages, then opened the project just to make sure they were fully installed, closed the project, and then attempted the migration again, but it failed again. Although I did discover that it seems to be removing the SDK packages as a part of the migration and then failing on something else, and leaving them like that, as it notes that in the logs and the packages are gone again. logs post migration Also don't mind that it's in my downloads folder in some of the screenshots, that's me testing if the file system it was in was the problem, which it doesn't seem to be.

orels1 commented 4 months ago

Interesting, I wonder why its getting stuck on that file 🤔 You can try removing it temporarily and see if it migrates? Not sure why it would get locked

SourceTheProto commented 4 months ago

Oh that actually worked! It just regenerated the file on its own and it went through with the process, thank you for that!

orels1 commented 4 months ago

I think I'm going to close out this issue then. I think the most we can do here is improve documentation / error messages, but I don't think this is a bug in the VCC code itself. Thoughts @Faxmashine ?