Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
4.2.4, 4.2.2, 3.2.2
Issue ID
1250982
Regression
Yes
[2D] Null reference on selecting sprite sub component when Geometry and Weight are applied on it in Skinning Editor
When Geometry and Weights are applied to the sprite in Skinning editor and sprite subcomponent is selected in the project window then editor throws NullReffrenceException
Steps to Reproduce:
1. Create a New Project with 2D Template
2. Import .PSB file in the project.
3. Window > 2D > Sprite editor.
4. Project > Fei_Cel_group.PSB .
5. Sprite Editor > Skinning Editor > Create Bone > Auto Geometry > Genrate for all visible > Apply
6. Project > PSB file > Select some child sprite
Actual Result:
Null reference on selecting sprite sub-component when Geometry and Weight are applied on it in Skking Editor
Expected Result:
Sprite subcomponents are selected without errors after applying geometry and weights
Reproducible on:
2020.2.0a13, 2020.2.0a9, 2020.1.0b11, 2020.1.0b8, 2019.3.15f1, 2019.3.14f1
Working fine on:
2020.2.0a8, 2020.1.0b7, 2019.3.13f1
Package Found version:
4.2.4, 4.2.2, 3.2.2
Package Found version:
4.2.1, 3.2.1
Stack trace:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.U2D.Animation.SpriteSkinEditor.OnInspectorGUI () (at library/packagecache/com.unity.2d.animation@4.2.2/editor/spriteskin/spriteskineditor.cs:129)
UnityEditor.UIElements.InspectorElement+<>c__DisplayClass58_0.<CreateIMGUIInspectorFromEditor>b__0 () (at /Users/builduser/buildslave/unity/build/Editor/Mono/Inspector/InspectorElement.cs:535)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&) (at /Users/builduser/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:189)
Environment:
Windows 10 and macOS 10.15
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #1245149