Hello! I have a question regarding spine assets generation on import. I want to be able to download spine assets at runtime, and then generate all the materials, SkeletonData, etc on the fly. I found that SkeletonData and SpineAtlasAsset have methods to create them. But I'd like to avoid reconstructing all the logic calling these, do you know which class is making use of these, or what is called when an asset is imported to the project? Or even if there is a cleaner way to do this. The main goal for me is to be able to update spine exports to a CDN and then download them and use them without havingo to go through unity to generate these extra files first
Spine assets from CDN
Ended up manually loading the Textures and TextAssets to call the runtime instantiation methods in the SkeletonData and SpineAtlasAsset classes. It worked, the only thing to keep in mind is when loading the textures from disk you have to assign the same name they had from the spine export, otherwise they do not match the ones in the atlas and it doe not work
@kadak Sorry for the late reply, just came back from a short vacation. Glad you've figured it out.
The main UnityEditor import procedure is located in AssetUtility.cs, method ImportSpineContent(). Nevertheless, you don't have the Unity Editor functionality available for asset creation and manipulation, so you need to resort to different means at runtime.
kadak It worked, the only thing to keep in mind is when loading the textures from disk you have to assign the same name they had from the spine export, otherwise they do not match the ones in the atlas and it doe not work
I'm not sure of how exactly you are assigning Textures and creating the AtlasAsset, but the names of the atlas page texture files are referenced in the .atlas.txt file, so these have to match.
No worries. I ended up just manually loading stuff from streaming assets using the proper protocols depending on the platform (normal file system or web requests for android and webGL). Then I used the SkeletonData and SpineAtlasAsset methods to generate runtime assets. Thew thing I mentioned about textures is just a reminder because I went ahead and tried to match the naming convention of the spine assets with all the other CDN assets we have. Not a good idea XD, as you pointed out they should be properly named from export.