Var materials = new Material įor ( int i = 0, n = pages. Void CreateRuntimeAssetsAndGameObject () ') Skeleton Animation runtimeSkeletonAnimation Lets take an example from the article on responsiveness and modify it to render on demand. It makes sense to use streaming in scenarios where only some of a texture’s mips are deemed necessary for the scene. Changes include textures or models finally loading, data arriving from some external source, the user adjusting a setting or the camera or giving other relevant input.

Skeleton Data Asset runtimeSkeletonDataAsset The general process of loading texture data on-demand, rather than upfront-all-at-once, is called texture streaming in this document, or streaming for short. Here is the prototype script that allows us to do this for now: Would it be possible to pass in argument a custom MaterialsTextureLoader to the GetAtlas method, in order to avoid these errors ? The creation of the dummy textures looks like a workaround : it would be nice to have materials without the final textures in advance, and without throwing errors at that time. Otherwise the MaterialsTextureLoader throws some errors as the given material has a null texture or a wrong texture name. Our materials are initialized with a dummy texture of 2x2 pixels with the right page name. There is still a problem: An error appears at runtime when calling the method SpineAtlasAsset.CreateRuntimeInstance(.) and more precisely when calling GetAtlas() then new Atlas(.) with the MaterialsTextureLoader.Īt the beginning we don't have the textures of the skins yet. When we want to display a particular skin, we change the corresponding texture and we update the material. We have created a script allowing to instantiate the information necessary to the runtime (SpineAtlasAsset, SkeletonDataAsset & SkeletonAnimation) with a temporary empty material during the creation of the SpineAtlasAsset.

For other cases you will need to build or load custom. BoxGeometry and BoxBufferGeometry can use 6 materials one for each face.ConeGeometry and ConeBufferGeometry can use 2 materials, one for the bottom and one for the cone.CylinderGeometry and CylinderBufferGeometry can use 3 materials, bottom, top, and side. We have alredy read those both threads around that topic : It should be noted though that not all geometry types supports multiple materials. We're trying to implement a skin system with texture loading on demand (using adressable textures later).

Load textures on demand