[FEEDBACK] Remove Unity version warnings in Control Panel because we now have VCC
Sayamame
In the VRCSDK control panel, there is a "Wrong Unity Version." warning and "You are not using the recommended Unity version for VRChat SDK. Content built with this version may not work correctly. Please use Unity xxxx.x.xxx" warning.
The second one has a very confusing "Auto Fix" button.
Well, we now have VCC, which we can use it to update the various packages and update the Unity version of our project.
So, the warnings on the SDK side are only confusing and should be removed.
This is because users may read the SDK warnings and try to upgrade directly using Unity Hub or others without VCC. This will destroy the project.
There should be no official navigation from anything other than the documentation, VCC, and VPMCLI. (BTW, VPMCLI does not have any migration feature now. https://github.com/vrchat-community/creator-companion/issues/403 )
Even if you keep the indication, it would be best to direct them to the official migration instructions page with a message like "(Info Icon) You are not using the recommended Unity version for VRChat SDK. To upgrade this project, read the document. ("Docs" Button)".
Log In
＃かなたん
At least the “Auto fix” button is very scary and I would like to see it fixed...
Whaddageek
What you need to realize is people are not always super up-to-date on new releases, or even all that technically competent (not a slam, just a statement). A version update is information you need to make sure gets seen so users will actually update, so it ABSOLUTELY should be in a place like the SDK control panel.
Sayamame
Whaddageek
I completely agree with the first part of what you are saying. But that is precisely why VCC exists, so I don't see much need for it to exist in SDK with the odd "Auto Fix" button...
Anyway, I think it should be changed. Not necessarily to remove it, but the current state is not appropriate.
Whaddageek
Sayamame People aren't gonna look in VCC. Half the time _I_ forget to check package manager for updates. You know where they always will look? When they go to the build screen to upload.
Sayamame
This is not particularly useful now (since the SDK for 2022.3.6f1 is already released), but I wrote this because it will affect us again in the future.