-
Notifications
You must be signed in to change notification settings - Fork 428
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
Minor compatibility issues with Unity 2021.1 #1051
Comments
I tried it with unity-2021.1.12f1 and it didn't cause the same problem. Another issue # 1066 has occurred and has been fixed. Check if there is still a problem with |
Thank you for taking care of this issue. I tried (edit) Since this issue doesn't happen in your environemnt, I'm checking my Unity Editor environment. I don't mean to review the code, but it seems I've also confirmed it with the following change to #if UNITY_2019_1_OR_NEWER
[SettingsProvider]
static SettingsProvider CreateProjectSettingsProvider()
{
+ foreach(var keyword in SettingsProvider.GetSearchKeywordsFromGUIContentProperties<Styles>()) {
+ Debug.Log($"keyword=<{keyword}>");
+ }
var provider = new SettingsProvider("Preferences/UniGLTF",
... |
I will remove the argument from the SettingsProvider |
|
Describe the bug
When I've imported
UniVRM-0.77.0_4a14.unitypackage
to Unity 2021.1.12f1 project, it reports the following error:After I fixed above error, I've also seen the following error:
Since they're independent classes for Preferences dialog, it seems both UniVRM and UniGLTF runtime/editor code works fine though.
To Reproduce
UniVRM-0.77.0_4a14.unitypackage
to the project.UniGLTF.UniGLTFPreference:CreateProjectSettingsProvider()
as descibed above.VRM.VrmPreference:CreateProjectSettingsProvider()
as descibed above.Expected behavior
UniVRM
package works without error.Environments (please complete the following information):
Windows 10
Unity 2021.1.12f1
UniVRM-0.77.0_4a14.unitypackage
Additional context
For now, I've fixed this issue with the following ad-hoc changes:
The text was updated successfully, but these errors were encountered: