Control
Generated
Part-level cubes (ours)
Object-level control

The hour and minute hands of a clock need to turn at different rates. One rigid motion for the whole clock forces every part into the same rotation. Because the hands point in different directions, this averaged rotation does not match either hand. The generated hands spin erratically and lose all resemblance to normal clock motion. With part-level cubes, each hand has its own cube and rotates independently at its own rate.

Control
Generated
Part-level cubes (ours)
Object-level control

In the first frame the ball is right in front of the batter. Object-level labels come from detecting and segmenting whole objects, and when two objects overlap like this, they can be merged into one object with a single box. One rigid motion then carries the batter's cubes away with the ball as it flies out. The generated batter is dragged toward the edge of the frame, the body stretches and breaks apart, and the batting motion is completely lost. With part-level cubes, the ball has its own cubes that fly away while the batter's cubes stay in place, so the batter follows through naturally.

Control
Generated
Part-level cubes (ours)
Object-level control

With one rigid motion per fencer, the leg cubes are translated together with the torso. There is no way to express a stepping motion in the control. The generated fencer on the left slides forward without any footwork, and the model hallucinates an extra leg to fill the gap. With part-level cubes, the legs have their own cubes and move independently, so the fencer steps into a natural lunge.