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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1245149