Search Issue Tracker
Fixed
Fixed in 1.1.9, 1.2.4
Votes
1
Found in [Package]
1.1.8
1.2.3
Issue ID
DANB-875
Regression
Yes
Aseprite file become unusable when changing it's Layer Import Mode from Merge Frame to Individual Layers and back
How to reproduce:
1. Open the “AsepriteImporterTest“ project
2. In the Project window, click on “bunball.aseprite”
3. In the Inspector, set the Layer Import Mode to the Individual Layers
4. Click on “Apply”
5. Set the Layer Import Mode back to the Merge Frame
6. Click on “Apply”
7. Observe the “bunball.aseprite”
Expected result: The Import Mode changes successfully, and the aseprite file remains usable
Actual Result: The “bunball.aseprite” file becomes unusable, and the following error is thrown: “Failed to import file Assets/bunball.aseprite. Error: Index was outside the bounds of the array
Reproducible in: 1.1.6, 1.1.8, 1.2.3 (2022.3.61f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7)
Not reproducible in: 1.1.5 (2022.3.61f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7)
Reproduced on: Windows 10, Windows 11 (user’s)
Not reproduced on: No other environment tested
Notes:
- Deleting “bunball.aseprite.meta” in the File Explorer makes the file usable again
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment