Hi everyone, I tried to generate SkeletonAnimation from NewSkeletonAnimationGameObject
The time and JSON calls are just weird.

Here is my code:

public SkeletonAnimation TemplateSAInit()
{
    this.skeletonAnimation = SkeletonAnimation.NewSkeletonAnimationGameObject(skeletonDataAsset);
    return skeletonAnimation;
}

The same SkeletonDataAsset costs only 17ms by using SpawnFromSkeletonDataExample.cs
Is there something important I missed?Thanks

CleRIC a écrit

Ara, yeah. Some time ago we used JSON import.
And in game we loaded one very-heavy (30+ animations) spine-object.
Unity profiler showed 129.2 mb memory allocation and 1458ms CPU time.
After that we was tried to use binary format.
Unity profiler showed 9.7 mb memory allocation and 268ms CPU time.

So... We prefer to use binary format.

CleRIC,Thank you for telling me that binary format data is faster.
But I still don't understand why the same SkeletonDataAsset file cost different time while using the same method.
This is the same asset load by SpawnFromSkeletonDataExample script.

Pharan a écrit

The call stack from ReadSkeletonData() and downward are a json parsing and loading process, which only happens once per SkeletonDataAsset (when GetSkeletonData is called for the first time).
Ideally in a game, you'd want to do this in the loading phase/loading screen.

In your loading screen, call skeletonDataAsset.GetSkeletonData(true) for each SkeletonDataAsset you want to preload. This means it will no longer go through this process when a component needs it.

CleRIC is also correct that binary data will improve load times. Sometimes drastically, depending on the complexity of your skeleton.

Thanks Pharan,Now I see.So once wherever I call skeletonDataAsset.GetSkeletonData(true), it will keep the data for the later Initialize the whole game?
I will try to do this first when loading.