search

umasteeringgroup / UMA

Unity Multipurpose Avatar
MIT License
739 stars 168 forks source link

null reference exception when adding receipe #363

Closed tatmanblue closed 3 years ago

tatmanblue commented 3 years ago

Describe the bug I added a UMADynamicCharacterAvatar to my new scene. I then dragged MailHair1 recipe and got this error.

NullReferenceException: Object reference not set to an instance of an object
UMA.TextureProcessPRO.ProcessTexture (UMA.UMAData _umaData, UMA.UMAGeneratorBase _umaGenerator) (at Assets/UMA/Core/StandardAssets/UMA/Scripts/TextureProcessPro.cs:58)
UMA.UMAGeneratorPro.ProcessTexture (UMA.UMAGeneratorBase _umaGenerator, UMA.UMAData _umaData, System.Boolean updateMaterialList, System.Int32 InitialScaleFactor) (at Assets/UMA/Core/StandardAssets/UMA/Scripts/UMAGeneratorPro.cs:372)
UMA.UMAGeneratorBuiltin.GenerateSingleUMA (UMA.UMAData data, System.Boolean fireEvents) (at Assets/UMA/Core/StandardAssets/UMA/Scripts/UMAGeneratorBuiltin.cs:305)
UMA.UMAGeneratorBuiltin.OnDirtyUpdate () (at Assets/UMA/Core/StandardAssets/UMA/Scripts/UMAGeneratorBuiltin.cs:454)
UnityEngine.Debug:LogException(Exception)
UMA.UMAGeneratorBuiltin:OnDirtyUpdate() (at Assets/UMA/Core/StandardAssets/UMA/Scripts/UMAGeneratorBuiltin.cs:476)
UMA.UMAGeneratorBuiltin:Work() (at Assets/UMA/Core/StandardAssets/UMA/Scripts/UMAGeneratorBuiltin.cs:160)
UMA.UMAGeneratorBuiltin:Update() (at Assets/UMA/Core/StandardAssets/UMA/Scripts/UMAGeneratorBuiltin.cs:112)

I deleted UMAEditorContext game object as well as the UMADynamicCharacterAvatar game object. I re-added UMADynamicCharacterAvatar and dragged MailJeans1 recipe to the inspector and got the error again.

Once the error appears, the UMA character is no longer rendered.

Environment (please complete the following information):

To Reproduce see above

Expected behavior Recipe to appear on UMA character and UMA character renders successfully

Screenshots If applicable, add screenshots to help explain your problem.

See https://imgur.com/a/7iN8qJP

Additional context Add any other context about the problem here.

Jaimi commented 3 years ago

Fixed in 2.13. An editor context is no longer automatically created. instead, you are prompted to add the UMA_GLIB to the scene (either permanently or temporarily). For now, you can get back to normal by selecting a recipe or character, and while the editor context is created, lock the inspector, select a non-uma item, drop a UMA_GLIB into the scene, and then unlock the inspector.

tatmanblue commented 3 years ago

when will 2.13 be available?

fyi: I think I followed those steps correct and it does not fix the problem.

edit: saving the scene causes the UMA character to be rendered.

Jaimi commented 3 years ago

Maybe 3-4 weeks? Depends on a few items. You can get the current test version from the develop branch.