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
- Crash on mono_dump_native_crash_info when changing a Particle System Renderer’s Material Shader to Standard Unlit
- VFX Prefab doesn’t have Preview icon in Project window and Preview window is empty in Inspector window
- Visual Effect Graph error message does not disappear and lasts forever until the Visual Effect Graph is reopened even when the error causing connection/node is deleted and Visual Effect Graph is saved
- Terrain Layers don't use icons when viewed in the Project Browser
- “RenderSettings customReflection texture has invalid type” error keeps getting thrown even when Environment Reflections was set back to Skybox from Custom with an invalid texture
Add comment