class

FPoseDriver

UE's AnimNode_PoseDriver: a joint's own rotation picks which stored poses fire, so a shoulder lifted to 90 degrees pulls in the corrective authored at 90 degrees without anything in gameplay knowing the pose exists.

Module
Animation
Header
#include "Animation/PoseAsset.h"
Namespace
Mowo

The RBF targets are NOT a second authored list: each pose in the asset already stores that driver bone's rotation, so the pose IS its own target. That is UE's "copy target rotations from pose asset" made the only path — a separately authored target list is a second copy of the same rotations, and the two drift the moment a pose is re-exported.

Public functions

ReturnsNameDescription
floatKernel
floatAngleDegreesAngle between two rotations, in degrees.
voidSolveWeightsFills outWeights (one per pose) from how close sourceRotation is to each pose's own rotation on track trackIndex.

Function details

Kernel

C++
static float Kernel(EPoseDriverKernel kernel, float distanceDegrees, float radiusDegrees)

AngleDegrees

C++
static float AngleDegrees(const Quat& a, const Quat& b)

Angle between two rotations, in degrees. Sign-insensitive: q and -q are the same orientation, and a driver that read them as 180 degrees apart would drop a corrective the moment a sampler happened to flip a key.

SolveWeights

C++
static void SolveWeights(const FPoseAsset& asset, int32_t trackIndex, const Quat& sourceRotation, float radiusDegrees, EPoseDriverKernel kernel, bool normalize, std::vector<float>& outWeights)

Fills outWeights (one per pose) from how close sourceRotation is to each pose's own rotation on track trackIndex. A track index outside the asset leaves every weight at zero — a driver naming a bone the asset does not track has nothing to say and must not invent a pose.

Generated from Animation/PoseAsset.h via animation.json · Oct 26, 2026Version 1.0.0