Preload animations

Benzino

Hey,

I'm just wondering what the approach is to preload an animation, say during a loading screen. Is it simply just loading the .json file (e.g. System.IO.File.ReadAllText) or do we need to do something else with the skeleton data asset?

Thanks!

Benzino

Pharan

You can have a MonoBehaviour or ScriptableObject that looks like this:

public class SkeletonsToLoad : MonoBehaviour {
     public List<SkeletonDataAsset> skeletonsToLoad = new List<SkeletonDataAsset>();
     

 public void PreloadSkeletons () {
      foreach (var asset in skeletonsToLoad)
           asset.GetSkeletonData(false); // This will cause the json to be read if it hasn't been read already.
 }
}

Store all the references to the SkeletonDataAssets you need to load then call PreloadSkeletons. You can also just add this logic to any of your other managing classes.

Benzino

Pharan schrieb

You can have a MonoBehaviour or ScriptableObject that looks like this:

public class SkeletonsToLoad : MonoBehaviour {
     public List<SkeletonDataAsset> skeletonsToLoad = new List<SkeletonDataAsset>();
     

 public void PreloadSkeletons () {
      foreach (var asset in skeletonsToLoad)
           asset.GetSkeletonData(false); // This will cause the json to be read if it hasn't been read already.
 }
}

Store all the references to the SkeletonDataAssets you need to load then call PreloadSkeletons. You can also just add this logic to any of your other managing classes.

Perfect, thanks for the quick, excellent response!

Shekill

Talking about loading :
The loading with asset.GetSkeletonData(false); is currently done in the unity main thread, so all game freeze (including visual) during spine skeleton data. With a lot of different skeleton it can freeze for 4-5 seconds, even using binary. Did not found a way to read altas in another thread. It's a TRC break issue.
Any update on this problem?

Pharan

We can try to separate out the method calls that use the Unity API (which is not allowed to be called from Unity's main thread. It won't let you.) from the pure-C# parts.
Beyond that, managing threads need to be handled on a game-by-game basis based on your threading architecture/decisions. Again, this is because Unity API doesn't provide uniform means to do that.