← Back to project

AgiBot X2 v4 robot movement-speed audit

New reference gallery, synchronized old-vs-v4 motion, and matched robot translation speeds vs the 0.9-scale corpus · 2026-07-24
AgiBot X2GMRHoloMotionretargettoe targetdata audit

1 · Headline

The v4 robot moves 11.7% slower in translation. Across the 452 matched clips with meaningful movement, horizontal pelvis/root path speed is typically 11.7% slower than the previous 0.9-scale corpus (median v4/old = 0.883). This is close to the nominal leg-scale ratio 0.787 / 0.9 = 0.874. The corrected toe target also changes how the legs realize that movement, so the observed ratio is not exactly a scalar copy.

Robot movement speed is defined here as horizontal root path length divided by seconds, in m/s. For motions that stay mostly in place, the gallery also reports mean Cartesian travel speed over the robot’s physical link frames. Matching frame count and FPS is used only as a control so both versions are compared over the same elapsed time.

2 · Synchronized old vs v4

Left is the previous 0.9-scale corpus; right is v4 with 0.787 measured leg scale and sole-point toe targets. Both use the same source frames and timestamps. The model, camera, and viewport are held constant, so displacement per second is directly visible; only the retarget reference changes.

Sideways walk · root travel -11.9%, mean link travel -10.9%. Same source frames at 25 fps playback.
High jump · root travel -8.9%, mean link travel -8.4%. Same source frames at 25 fps playback.
Hip-hop box step · root travel -13.3%, mean link travel -5.5%. Same source frames at 25 fps playback.

3 · More v4 X2 data

Nine diverse v4 references rendered on the physical-head, 29-DOF X2 model. Each strip shows three moments from the most active six-second window, or the full clip when shorter.

v4 references: locomotion, jumps, dance, crouching, exercise, gesture, and stretching. Toe markers are not robot geometry and are not present in this training model.

4 · How fast does the robot move?

The matched sample was selected deterministically from 121,486 v4/previous 0.9-scale basenames available when this report was built. Root speed uses 452 clips above 0.02 m/s to avoid unstable ratios on stationary motions. Its v4/old ratio has median 88.3%, mean 90.4%, and a 10th–90th percentile range of 87.3%–96.7%.

ClipOld root m/sv4 root m/sRoot changeOld body m/sv4 body m/sBody change
Sideways walk0.4040.356-11.9%0.4290.382-10.9%
High jump0.1260.115-8.9%0.3740.343-8.4%
Hip-hop box step0.4860.422-13.3%0.8520.805-5.5%
Pirouette0.2240.236+5.1%0.7010.690-1.6%
Crouch and operate0.0540.052-4.3%0.1960.198+1.0%
Exercise0.0940.076-18.4%0.6970.707+1.4%
Clap0.0180.016-7.9%0.0770.075-3.0%
Body stretch0.0870.075-14.2%0.2170.211-2.7%
Salsa side step0.1420.138-3.0%0.2850.294+3.1%
Matched robot translation speed in m/s and its ratio. Points above the diagonal are faster in v4.
Same-clip examples: root travel captures locomotion, while mean link travel captures visible whole-body movement in in-place motions.

5 · What the toe fix actually changes

v4 targets two virtual sole points located at [0.10, 0, -0.073] in the ankle-roll frames. They are massless, jointless, geometry-free GMR IK markers. The output remains root plus 29 actuated DOFs; the MotionLib schema and training URDF/MJCF contain no toe marker slots.

In the gallery sample, the largest knee/ankle-pitch pose change is right_ankle_pitch_joint at 11.5° mean absolute difference. The correction propagates through hip, knee, and ankle pitch because the solver now matches the physical sole point instead of treating the ankle frame as the foot endpoint.

Fourteen joints with the largest old-v4 pose differences across the nine-clip gallery.

6 · GMR v4 vs SOMA

Neither route is a physics simulation. Both generate kinematic reference trajectories. They do not prove torque feasibility, contact stability, dynamic balance, or policy trackability.
PropertyGMR v4SOMA X2 port
Robot information usedX2 link transforms, joint axes and configuration limits; measured 0.787 lower-body scale; sole-point IK targetsX2 morphology and kinematic mapping, with a custom port from the public G1-oriented path
Physics information used in retargetNo dynamics rollout. The MJCF is loaded for FK/IK, but mass, inertia, torque, friction, and contact balance are not optimized. GMR velocity limits are disabled in this pipeline.No downstream physics tracking guarantee; output is still a kinematic reference
Observed X2 resultValidated 29-DOF schema and model match; toe-target geometry fixes the ankle-as-foot-endpoint errorLower body was plausible, but the tested port produced unusable upper-body behavior around the X2 elbow/shoulder setup; the route was rejected after sufficient testing
Current decisionActive retarget pathRejected; do not revive or graft

Thus “more suitable for X2” means a better X2-specific kinematic target and a cleaner data contract. It does not mean GMR has become physics-aware. HoloMotion training and rollout evaluation provide that next evidence layer.

7 · Why a controlled SONIC retry is warranted

The previous SONIC run was trained against the 0.9-scale reference regime with incorrect foot endpoints. Faithful tracking could leave feet about 6.6 cm above the floor at the median, while a separate subset penetrated the floor. The learned policy compensated with conservative step reach and higher cadence, horizontal drift was visible in separate rollout probes, but it was never an official success result.

Prior evidenceInterpretation for v4
Anchor reward tuning improved horizontal displacement attainment from 0.70 to 0.91; that diagnostic did not define official success. A historical released-default common-v4 replay scored 104/126 = 82.54%; the audited primary 512-motion 50k result is 480/512 = 93.75%.Reward pressure helped, but could not remove the reference geometry ceiling. Keep the proven anchor recipe while changing only the data.
A blanket 0.7-scale experiment reached the requested speed but caused 29/39 falls and only 5–8% success.v4 is not a global slowdown: it uses measured X2 lower-body scale plus correct sole targets while preserving the rest of the embodiment contract.
The v4 reference itself translates about 11–12% slower than the old 0.9 baseline.A retry must report absolute m/s as well as policy/reference speed ratio, otherwise an easier target could look like a controller improvement.
Active test: the audited v4 lineage trains from random initialization, so it is not a data-only A/B against the warm-started historical 50k policy. Rank its checkpoints on the frozen 512-motion primary ruler and separately compare absolute root m/s, reference-normalized speed, contact quality, falls, and both MPJPE scopes.

8 · Scope and caveats

Generated from x2_native_full (previous 0.9 scale) and x2_native_v4 (0.787 leg scale + toe targets) · metrics and videos use identical basenames and timelines