#Cocos creator animation with data update
#Cocos creator animation with data skin

Although the two systems can be switched seamlessly at runtime, try to do this as less frequent as possible, because each switch involves the reconstruction of the underlying rendering data. It is recommended that you only use the real-time calculated system if you clearly feel that the performance of the pre-baked system cannot reach the standard. Selection and best practice of two systemsĪfter importing all model assets, all prefabs use the pre-baked system by default to achieve the best performance.

Explicit procedural control over any joint tranformations.

Mixing and masking of any number of Animation Clips.

This provides the fundamental support for all the following functions: Extract the transformation data from joint node tree, do frustum culling, upload the complete joint transformation information of the current frame to UBO, and complete the skinning in the GPU.

Each Skinning Model Component ( SkinnedMeshRenderer) holds a common Skinning Model class ( SkinningModel).

#Cocos creator animation with data skin

Users and any other system can affect the skin effect by manipulating this node tree.Animation data will be output to the skeleton node tree of the scene.All animation data are calculated dynamically according to the current global time.The current runtime process is roughly as follows: The dominant purpose of this system is expressiveness, ensuring the correct display of all details, and complete program control capabilities. Real-time calculated Skeletal Animation System

#Cocos creator animation with data update

Based on the bounding box information pre-baked in the same way to do frustum culling, update the UBO, and get the current data from the texture atlas on the GPU to complete the skinning. Each skinning model component ( SkinnedMeshRenderer) holds a pre-baked skinning model class ( BakedSkinningModel).Each Skeletal Animation Component ( SkeletalAnimation) is responsible for maintaining the current playback progress, stored in the form of UBO (a vec4).Depending on whether the operating platform supports floating-point textures, the corresponding texture format will be RGBA32F, or automatically fallback to RGBA8 if not available (The rendering results should be identical, it is only the fail-safe approach for really low-end devices, and shouldn't be of any concern for game developers).All animation data will be pre-sampled in advance according to the specified frame rate and baked onto a global-managed joint texture atlas.

Cocos Creator has made many low-level optimizations in a targeted manner. The dominant purpose of this system is performance, and some sacrifices in expressiveness are also considered acceptable. To use SkeletalAnimation, please refer to the SkeletalAnimation API. when enabled, the pre-baked system will be used, or the real-time calculated system if otherwise. Seamless switching between these two systems can be as simple as toggle the useBakedAnimation switch on SkeletalAnimation, even at runtime. Two different systems are provided, Pre-baked Skeletal Animation and Real-time calculated Skeletal Animation, each is optimized for different purposes. Skeletal Animation is a common but special type of animation.

Resource Management Considerations - meta files Creating Animation Components and Animation Clipsīuild a Scene Image Using the Scene Panel