Search Issue Tracker
Feature Request
Feature Request in 1.0.X
Votes
0
Found in [Package]
1.0.0
Issue ID
DANB-510
Regression
No
Custom Physics Shape isn't applied to sprite when using the Aseprite Importer
How to reproduce:
1. Open the attached “Bug Report.zip“ project
2. Open the “BugScene“ Scene
3. Open the Scene view
4. Select the “tree_0“ GameObject in the Hierarchy
Expected result: The Collider Shape is the same as the Sprite Editor Custom Physics Shape
Actual result: The Collider Shape is different from the Sprite Editor Custom Physics Shape
Reproducible with: 1.0.0-pre.4 (2021.3.25f1), 1.0.0 (2021.3.29f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b7, 2023.3.0a2)
Reproducible on: macOS 13.4.1 Ventura (Intel)
Not reproducible on: No other environment tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This is not a bug, but rather a gap in the feature set of Aseprite Importer. We have this feature on our radar and are considering it for future versions of the package.
Thank you for bringing this to our attention.
Resolution Note (1.0.X):
This is not a bug, but rather a gap in the feature set of Aseprite Importer. We have this feature on our radar and are considering it for future versions of the package.
Thank you for bringing this to our attention.