YENRA MOTION-CYCLE REVIEW CHECKLIST
Use with the source animation and the exported clip in its target engine.
Record length units explicitly; compare the same event one full cycle apart.

Clip / rig / export version:
Authoring tool version / target engine version:
Frames per second:
Cycle start / corresponding repeat frame:
Number of frame intervals:
Duration in seconds = intervals / frames per second:
Distance traveled per cycle (meters or explicitly named project units):
Average speed = distance / duration:
Root-motion policy (which system applies translation/rotation):
Left-foot contact interval:
Right-foot contact interval:
Loop sampling convention / duplicated endpoint:

[ ] Several repeats play cleanly at the intended speed.
[ ] Position and motion through the boundary are continuous as intended.
[ ] Planted feet remain appropriately anchored in world space.
[ ] Scale and root-motion settings match the target controller.
[ ] Blends into and out of the cycle are checked in the target scene.
[ ] One-variable changes are compared with an original reference.

SYNTHETIC EXAMPLE (not a measured character):
24 intervals / 24 frames per second = 1.00 second.
1.20 meters / 1.00 second = 1.20 meters per second.
For a 1.80 m/s controller, initial rate experiment = 1.80 / 1.20 = 1.5x.
This aligns average speed only; inspect contacts and style afterward.
Frame 1 to frame 25 spans 24 intervals. Verify exporter endpoint behavior.

Observed issue:
One change tested:
Result / next check:

Guide: https://yenra.com/faster-motion-cycles/
Research context:
https://la.disneyresearch.com/wp-content/uploads/Authoring-Motion-Cycles-Paper.pdf
Prepared September 19, 2026.