Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.4f1
2019.4.8f1
2020.1
2020.2
Issue ID
1272865
Regression
Yes
NullReferenceException error is thrown when updating more than one Avatar's animation info at the same time
How to reproduce:
1. Open the user's attached "AvatarUpdateTest.zip" project
2. Expand the "boss_gongshujin001" Asset in the Project window
3. Select the "boss_gongshujin001Avatar" Asset in the Project window
4. Press "Configure Avatar"
5. Rotate any body part, as long as "Character is not in T pose" doesn't pop up
6. Select the "skdl01" and "skdl02" Assets in the Project window
7. Press "Update" and then "Apply" in the Rig section in the Inspector
8. Observe the Console log
Expected result: No error messages are thrown in the Console log
Actual result: "NullReferenceException: Object reference not set to an instance of an object" error message is thrown in the Console log (Full error message in the Edit)
Reproducible with: 2019.3.4f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0a20
Not reproducible with: 2018.4.27f1, 2019.3.3f1, 2020.2.0a21, 2020.2.0b1
Note:
- No errors are thrown when updating the Avatars one by one
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Wrong shader appears when Particle System is added as a component
- Realtime Hard Shadows resolution of Spot Light and Point Light cannot be changed by script when using Universal Render Pipeline (URP)
- Warnings in the Package manager have no margin on the right side
- Errors are thrown in the Console and the Game view fails to render when RenderGraph Compatability is disabled and a Camera stack has a Pixel Perfect Camera Component with "Stretch Fill" Crop Frame
- [Linux] Crash on System.Runtime.InteropServices.Marshal:copy_from_unmanaged_fixed when accessing shared memory
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a21
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.8f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.12f1