Search Issue Tracker
Fixed
Fixed in 1.1.4
Votes
0
Found in [Package]
1.1.4
Issue ID
DANB-654
Regression
Yes
Aseprite Import Settings do not appear in the Inspector when Aseprite file is selected
Reproduction steps:
1. Open the attached “AsepriteBug.zip“ project
2. Select “F_Average.aseprite” in the Project window
Expected result: Inspector shows settings for Aseprite Import
Actual result: Inspector shows no settings for Aseprite Import
Reproducible with: 1.1.4 (2022.3.37f1)
Not reproducible with: 1.1.3 (2022.3.37f1), 1.1.4 (2021.3.41f1, 2022.3.39f1, 6000.0.12f1)
Fixed in: 1.1.4 (2022.3.38f1)
Reproduced on: macOS Sonoma 14.5 (Intel)
Note: Inspector settings appear after successful code compilation but disappear again after clicking on any other file in Project window
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
Add comment