AutoMovie API
    Preparing search index...

    Variable HUMANOID_GAITSConst

    HUMANOID_GAITS: Record<
        "walk"
        | "run"
        | "sprint"
        | "sneak"
        | "march",
        IAutoMovieGait,
    > = ...

    The five canonical humanoid gaits, the locomotion the locomote verb's gait enum names (walk/run/sprint/sneak/march), as ready IAutoMovieGait data a host drops into an actor context. Same role as the engine's other canonical humanoid tables (ROM, joint axes): the shapes are fixed, a body is what varies.

    Every gait is tuned to sit inside the humanoid ROM, which is the whole reason neutral exists. Knees (flexion [0, 150]°, no hyperextension) swing about a bent center; and the faster gaits carry the hips forward too: a sprint's ±amplitude swing would cross the hip's −30° floor without a forward neutral. Slower is calmer: sneak crouches (a high knee center) and holds the ground longer (high duty); march throws the knees high; sprint is all reach and little contact (low duty).

    Left/right limb pairs are a half-cycle out of phase, and each upper arm shares the opposite upper leg's phase for contralateral counter-swing. These rows drive hips, knees and upper arms; performShot's later stance stage owns ground-contact IK.

    locomote carries the authored gait as fullBody. Layer safety is decided from the root/bones/expression the synthesized clips actually carry after masking, not from the broad region names: this counter-swing can layer with a head-only look, but correctly conflicts with a simultaneous arm gesture.

    Periods are seconds, phases are turns and angular channels are degrees. These are conventional schematic performance targets rather than measured anatomical motion capacities. Module-owned rows are shared by every profile context; the engine validates and samples them. Fixed table construction happens once and retains no per-frame task or host resource.