-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package Manager, Unity 2018.2: open Utility Panel causing many editor errors #238
Comments
Ahoy! DOTween's editor will have many more errors other than that, because it requires DOTween to be in the project folder as of now. The package manager is not truly open yet for packages that are not Unity's own (though Unity is working on it for the future), so I think it would really be better to postpone this to when it's ready :P On a secondary note, I'll soon release a big modular upgrade to DOTween that will allow it to enable/disable modules just like the Package Manager does. |
My problem doesn't concern the modular DOTween issue. Because I have many projects that use a same set of packages so I've just put them into one directory and make the Package Manager reading from there. |
I understand. But I prefer to wait for the Package Manager to be really ready for external assets before I change DOTween's code to allow it (also because it won't be an easy task—there will be a lot of stuff to change in the editor). |
Any updates on this? We package DOTween internally so multiple projects can use the same package and get updates whenever we choose to, but this issue stops us from using DOTween via the package manager. |
I've made DOTween a custom package to be used with the new Package Manager of Unity 2018.2.
Everything works well except the Utility Panel: it's all blank. And these are the error logs I've received:
The text was updated successfully, but these errors were encountered: