Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.1.8
1.2.3
Issue ID
DANB-877
Regression
No
Changing "Import Mode" of Asperite in the Inspector window throws error and breaks Aseprite Asset
*Steps to reproduce:*
1. Open the attached "AspriteProject" project (Google Drive)
2. Select “Birt_anim_01” Asperity in the Project window
3. In the Inspector window > General > Import Mode change from Animated Sprite to Sprite Sheet
4. Click “Apply”
5. Change Import Mode back to Animated Sprite
6. Click “Apply”
7. Observe the Asperite in the Project window and observe Console window
*Actual results:* Error is thrown in the Console and Asperite Asset is broken
{code:java}
Failed to import file Assets/bird_anim_01.aseprite. Error: Index was outside the bounds of the array.
at UnityEditor.U2D.Aseprite.AsepriteImporter.OnImportAsset (UnityEditor.AssetImporters.AssetImportContext ctx) [0x001df] in ./Library/PackageCache/com.unity.2d.aseprite@ca048e7ac308/Editor/AsepriteImporter.cs:240
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /Users/bokken/build/output/unity/unity/Modules/IMGUI/GUIUtility.cs:219)
{code}
*Expected results:* No errors thrown in the Console, Asprite Asset is not broken
*Reproducible with versions:* 1.1.8 (2021.3.50f1, 2022.3.60f1, 6000.0.43f1), 1.2.3 (6000.1.0b11, 6000.2.0a7),
*Tested on (OS):* Apple M1 Max, Sequoia 15.2
-
Resolution Note:
Duplicate of DANB-875
Duplicate of another internal issue: DANB-875: Aseprite file become unusable when changing it's Layer Import Mode from Merge Frame to Individual Layers and back
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
This is a duplicate of issue #UCW-212990-875