NEOLearn

Animation

The NEO engine's animation - clips, graphs and players for any property, glTF skeletal animation and morph targets - and NEO's character animation stack on top.

Updated October 20, 2026

On this page

NEO has two layers of animation. The engine core's animation system plays clips through graphs on any entity: a skinned character from a glTF file, a door's transform, a UI node's colour. On top of it, NEO's character animation stack does what a third-person game needs: motion matching, foot placement and IK, rigs, physical animation and cinematics.

The engine's animation system#

PieceWhat it is
AnimationClipAn asset: curves over time, each targeting one property of one entity, plus events at given times.
AnimationGraphAn asset: a tree of clip, blend and additive nodes with weights. Even one clip plays through a graph.
AnimationPlayerA component on the root entity: which graph nodes are playing, their time, speed, weight and repeat.
AnimationGraphHandleA component next to the player, pointing at its graph.
AnimationTargetId + AnimatedByComponents on each animated entity: which curves are theirs, and which player drives them.
AnimationTransitionsAn optional component that cross-fades from one animation to the next.

glTF files bring all of this with them: loading a skinned model spawns the player and targets, and its animations load as clips. The animation plugin is in DefaultPlugins, with glTF animation and morph targets on in NEO's builds.

Pages#

PageWhat it covers
Animation clipsBuilding clips in code, animatable properties, events.
Animation graphs and playersPlaying, pausing, seeking, blending, additive layers, masks and transitions.
glTF animationPlaying the animations in a .glb or .gltf file on its skinned meshes.
Morph targetsBlend shapes: animating and setting their weights.
Curves and easingEasing functions, curves and moving values smoothly without a clip.

NEO's character animation#

NEO games built on the gameplay kit animate their characters with NEO's own crates, not with clips on an AnimationPlayer:

PartWhat it does
Motion matching (neo_motion_matching)Picks the pose that best continues the character's movement from a library of motion clips, every frame, and blends between them. Its libraries are .mmlib files. It also handles montages, traversal warping, foot placement and leg IK, orientation and stride warping, and interactions between two characters.
Animation graphs (neo_anim)Graphs as data: clip players, blends, 1D and 2D blend spaces, state machines, layered blends and additives, with motion-matching and rig nodes. Clips can be NEO's compressed .neoanim format, imported from glTF, FBX and BVH.
Rigs (neo_rig, neo_rig_vm)Procedural rigs written in a small rig language: IK (two-bone, FABRIK, CCD), aim and constraints, and spring dynamics, run after the animation on the pose.
Physical animation (neo_physics_control)Articulated rigid bodies driven toward the animated pose: active ragdolls, hit reactions and get-ups.
ECS components (neo_anim_ecs)MotionMatching, LegIk, RigController and PhysicalAnimation components, run in that order, for games that put these pieces on their own entities.
Sequencer (neo_sequencer)Cinematics as .neoseq files: transform, property, visibility, event, audio, camera-cut and animation tracks, with a SequencePlayer.

The character kit runs all of this for you; see Gameplay kit. Its camera side is on Camera.

Next steps#