Search Issue Tracker
Fixed
Fixed in 7.0.10, 9.0.6, 10.0.1
Votes
2
Found in [Package]
7.0.6
9.0.1
10.0.0-pre.2
10.0.0
Issue ID
DANB-422
Regression
Yes
Sprite Shape is not filled when "Closed Sprite Shape" is enabled and "Detail" is set to "High Quality"
How to reproduce:
1. Open the "URPTest" project
2. Select the "Closed Sprite Shape" GameObject
3. In the Inspector enable "Fill Teselattion (C# Job)"
4. In the Inspector change "Detail" to "High Quality"
5. Observe the “Closed Sprite Shape” in the Scene view
Expected result: Sprite Shape is filled
Actual result: Sprite Shape is not filled
Reproducible with: 7.0.4 (2021.2.16f1), 7.0.6 (2021.3.21f1), 9.0.1 (2022.2.12f1), 10.0.0 (2023.1.0b9), 10.0.0-pre.2 (2023.2.0a5)
Not reproducible with: 5.3.0 (2020.3.46f1), 7.0.3 (2021.2.15f1)
Reproducible on: Windows 11
Not reproducible on: Windows 10 Pro
Note: also reproducible in Player
Comments (1)
-
Enrique48k
Mar 22, 2023 17:00
I wanted to add that in the test project I sent, if you select all the points of the SpriteShape and move them to another position, sometimes it is filled and other times it is not.
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 10.0.1):
Fix for this issue will be available on 2D SpriteShape package 10.0.1 and above
Resolution Note (fix version 9.0.6):
Fix for this issue is available on 2D SpriteShape package 9.0.6 and above
Resolution Note (fix version 7.0.10):
Fix for this issue is available on 2D SpriteShape package 7.1.0 and above