Search Issue Tracker
Fixed in preview.8 - 2.0.0
Votes
0
Found in [Package]
preview.1 - 1.0.12
Issue ID
1106474
Regression
Yes
[2D] Sprite Shape Profile component breaks when creating range
Sprite Shape Profile component breaks when creating range and exceptions thrown in the console
Steps to repro:
1. Open a new project
2. Go to Window>PackageManager
3. Install 2D SpriteShape
4. In Project, right-click > Create > Sprite Shape Profile > Empty
5. Assign texture or psd in the texture field of Sprite Shape Profile
6. Click on Range
Actual Result: Sprite Shape Profile component breaks and throws errors in the console when clicking on the range
Expected Result: Angle of ranges creates
Occurring on :
2019.1.0a11
Working Fine on:
2018.3.0f1, 2019.1.0a10, 2019.1.0a9
Environment:
Windows 10 and Mac 10.13
StackTrace:
NullReferenceException: Object reference not set to an instance of an objectUnityEditor.U2D.SpriteShapeEditor.GetPreviewSpriteIndexFromSessionState (Int32 rangeIndex) (at Library/PackageCache/com.unity.2d.spriteshape@1.0.12-preview.1/Editor/SpriteShapeEditor.cs:252)UnityEditor.U2D.SpriteShapeEditor.HandleSpritePreviewCycle (Rect rect) (at Library/PackageCache/com.unity.2d.spriteshape@1.0.12-preview.1/Editor/SpriteShapeEditor.cs:579)UnityEditor.U2D.SpriteShapeEditor.DoRangesGUI () (at Library/PackageCache/com.unity.2d.spriteshape@1.0.12-preview.1/Editor/SpriteShapeEditor.cs:501)UnityEditor.U2D.SpriteShapeEditor.OnInspectorGUI () (at Library/PackageCache/com.unity.2d.spriteshape@1.0.12-preview.1/Editor/SpriteShapeEditor.cs:288)UnityEditor.UIElements.InspectorElement+<CreateIMGUIInspectorFromEditor>c__AnonStorey2.<>m__0 () (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorElement.cs:333)UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
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
Add comment