File may be corrupted or was serialized with a newer version of Unity.

Unity Engine
1

I’m using the Aseprite importer to bring in my characters and their animations, but every time I try to set up the animation rules in the ‘Animator,’ it gives me this error. I’ve searched everywhere and can’t find a solution. Please help me!

“Failed to load ‘C:/Users/Marlon/Warrior’s Souls/Assets/Sprites/player/idleFront.aseprite’. File may be corrupted or was serialized with a newer version of Unity.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)”

9449492--1326407--upload_2023-11-4_1-28-2.png
9449492--1326407--upload_2023-11-4_1-28-2.png1040×80 14.3 KB

9449492--1326407--upload_2023-11-4_1-28-2.png
9449492--1326407--upload_2023-11-4_1-28-2.png1040×80 14.3 KB

2

Hello,
The Animator generated by the Aseprite Importer is read only. If you wish to create a read/write Animator, please follow these steps: Frequently asked questions | 2D Aseprite Importer | 1.0.1

2 Likes
3

Hi,
I just ran into this same issue and thankfully stumbled upon this thread. Could the editor could be updated to disable the animator in such cases as this? I don’t think the user should even be allowed to make edits to a read only asset.

4

Does Unity have even native support to Aseprite files?

5

Yes? There’s an package with an importer for them that is included by default with any new 2D project.

6

Nice. This means Aseprite is really mainstream tool.

7

I agree with you. We are looking into ways to streamline this and make it more user friendly. It requires larger changes though, so it will take some time before we have something ready.

8

You can read more about it here: https://docs.unity3d.com/Packages/com.unity.2d.aseprite@1.1/manual/index.html

9

Unity 2022.3.3f1 Tried with old and brand new aseprite files, happens 100% whenever I try to add a blend tree to the animator

10

*Note: forgot to mention in the previous post, this still occurs even after exporting and editing a fresh animator controller.

11

@dead_byte_dawn could you file a bug report so we can take a closer look?

12

Thank you, looks like the fix to the issue is simply to create a new animator

1 Like
13

I ran into this issue too. I exported the controller and animations like in the documentation sent above, but I still have the issue. I tried reimporting the aseprite file, and I didn’t change a thing, and I still get the issue. How do I solve this?

14

There isn’t a lot of information in this thread about what actually goes wrong. Do file a bug report so we can take a closer look, thanks!