- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper presents incremental work on motion generation for humanoid locomotion. The starting point is a two thread detached system with one planner (the proposed HIPC) and a low level tracker/controller (SONIC, Luo et al, 2026). This two thread setup is similar to many earlier methods. In the proposed setup these are detached and as the generation of a plan takes some time, and since actions may not be perfectly executed, the plan will always be made with an incorrect initial state, and it will also be slightly out of date when it reaches the controller. The paper describes two strategies to fix these problems, these are called: deviation delayed recovery, and history re-anchoring.
Critical strengths
- Evaluation uses mostly metrics used in the cited papers e.g. (Xie, 2026) and (Chen, 2026), but also introduces some of its own in order to test Q1,Q2,Q3.
- The experiments demonstrate the effectiveness of the proposed modifications.
Critical weaknesses
-
Although the proposed modifications make sense, I remain unconvinced that more closed-loop control like ReactiveBFM is not a better approach. E.g. Chen et al. 2026 describes approaches using a SONIC style tracker as "severely crippling its dynamic reactivity to physical feedback". I believe this weakness remains, even if the two proposed fixes are applied. Even worse, ReactiveBFM by Chen et al. 2006 is here coupled with the SONIC tracker (311), exactly the approach they complain about!
-
The details on how the datasets are used is not entirely clear. It seems as if datasets AMAS, LAFAN, HiPHI and GMR are used for training (237-239) and the entire 100STYLE for testing (not just the test set asin Chen, 2026) (361,400), together with Replica indoor scenes (410). Is this correct?
-
How were the other methods in the result tables trained? Were they retrained on the same datasets as HIPC, if so how? Or did you use their weights? If so, how about data leakage from 100STYLE?
-
The paper is quite hard to follow, due to numerous easy to fix problems with the text. E.g.
- #183 Why are horizontal quantities incremental, end vertical states direct? This is detail just hanging in the air.
- #189 "where R_t in SO(3) and W^p_t in R^3". These variables are NOT in the Eq. (2) above. Better to introduce them before Eq. 2, and describe the variables in Eq. (2) below Eq.2.
-
The related work discussion is mostly good. Missing is the OMG paper that is compared to in the results tables.
-
The result tables list methods ARDY and OMG. These are not properly cited. OMG is by S. Huang et al. (2026) and should be cited and discussed in the related work, ARDY is cited, but not referred to as ARDY in the citation nor in the related work, making the connection not obvious.
Questions for authors
Q1: Can you provide performance for ReactiveBFM and OMG using their complete systems, instead of always coupling them with SONIC (that ReactiveBFM explicitly states as a bad idea)?
Q2: Can you detail how HIPC and the other compared methods were trained? Datasets, use of public weights etc.?
Q3: The looser coupling compared to ReactiveBFM is potentially reducing the compute load. Is this the case, and if so, can it be demonstrated somehow?
2 comments
Dear Reviewer,
Thank you again for your valuable comments. As the discussion period is nearing its end, we would like to kindly ask whether our responses have adequately addressed your concerns.
Please let us know if any further clarification is needed. If our responses have resolved your concerns, we would greatly appreciate it if you could reconsider your evaluation in light of the additional evidence and clarifications provided.
Thank you for your time and consideration.
Best regards,
The Authors
We argree system comparison should be more clear, we present more experiment details as follows:
Weakness 1 & Q1: Reactivity and Full-System Comparisons
Planner–tracker coupling. We agree that universal trackers alone cannot adapt high-level motion plans to changing instructions. However, ReactiveBFM's criticism concerns this reliance on predefined references and SONIC's keyframe-in-betweening planning. HIPC addresses this limitation by replacing SONIC's original planner with a goal-conditioned motion generator. ReactiveBFM likewise employs a separately pretrained ScaleBFM tracker instead of jointly training its planner and controller. ReactiveBFM does not test its planner with SONIC, so the cited criticism does not establish that SONIC is unsuitable for closed-loop motion control.
ReactiveBFM comparison. We reproduce ReactiveBFM's Gaussian prefix-noise augmentation within our training framework. For each prefix frame t and motion dimension d, we independently sample
\quad \rho=\operatorname{clip}(s/S,0,1),$$ where s/S is the training progress and $\sigma_d$ is the dataset standard deviation of the d-th unnormalized motion dimension. Noise is added to the normalized motion prefix. We train a **ReactiveBFM baseline** using this augmentation. Both checkpoints share the HIPC planner architecture and training data, **the only training difference is Gaussian prefix noise versus deviation-decayed recovery**. At inference, we compare history construction and asynchronous execution strategies under the same SONIC tracker and 2 Hz replanning frequency. Full details are provided in Table 3. | Framework | History | Async. Strategy | E_pos (m) ↓ | Fall (%) ↓ | |---|---|---|---:|---:| | ReactiveBFM | Realized | Direct Switching | 1.386 | 85.714 | | ReactiveBFM | Realized | Temporal Ensembling | 1.397 | 76.190 | | ReactiveBFM | Hybrid | Temporal Ensembling | 0.089 | **0.000** | | ReactiveBFM | Hybrid | Latency Compensation | 0.076 | **0.000** | | HIPC | Hybrid | Direct Switching | 0.184 | 1.190 | | HIPC | Hybrid | Temporal Ensembling | 0.097 | **0.000** | | **HIPC** | **Hybrid** | **Latency Compensation** | **0.067** | **0.000** | **Results.** Realized histories produce large errors and frequent falls despite prefix-noise training, suggesting that independent Gaussian noise does not adequately capture execution-induced deviations. Hybrid histories combined with temporal ensembling or latency compensation achieve zero falls for both checkpoints, with latency compensation further improving accuracy. This is a **controlled mechanism comparison**, not a reproduction of the original ReactiveBFM–ScaleBFM system. ## Weaknesses 2–3 & Q2: Datasets, Weights, and Leakage HIPC trains on **AMASS, LAFAN, and HiPHI**, retargeted through GMR. The original evaluation used 100STYLE as test set, and **Replica** scenes served separate dynamic tracking tests. **Kimodo, ARDY, TextOp, and OMG use public weights without fine-tuning.** We additionally evaluate OMG's **native generator–HoloMotion tracker** (OMG\*). All use SONIC except OMG\*. To prevent data leakage with 100STYLE in OMG's training data, we re-evaluate on **MotionDecode**, which is not listed among the compared methods' reported training datasets. Selected results are shown below, with complete comparisons in the revised paper. Full details are provided in Table 2. | Method | PJ → | AUJ ↓ | Fall (%) ↓ | E_pos (m) ↓ | FID ↓ | |---|---:|---:|---:|---:|---:| | OMG | 1.109 | 7.327 | 22.000 | -- | 0.592 | | OMG\* | 0.522 | 4.595 | 1.333 | -- | **0.533** | | **HIPC** | 0.445 | **2.215** | **0.000** | **0.077** | 0.592 | ## Q3: Computational Cost and Coupling **Response:** ReactiveBFM, like HIPC, employs a separately pretrained, frozen tracker (ScaleBFM). Both systems incorporate execution feedback at inference time, differing primarily in **how realized states are incorporated into planner histories**. A more tightly coupled approach is Humanoid-DART, which uses simulated tracker executions to iteratively improve both the planner and tracker during training. HIPC instead focuses on mitigating execution-induced distribution shift through history re-anchoring, without controller-specific training. We claim no training or inference efficiency advantage over ReactiveBFM. If the reviewer considers ReactiveBFM more tightly coupled or more closed-loop, we would appreciate clarification of the specific mechanism underlying this distinction. ## Presentation and Citations We explain that incremental horizontal quantities ensure planar position/heading invariance, while direct vertical states preserve ground-relative height/posture (191); $R_t$ and ${}^W p_t$ now precede Eq. (2) (195). We added OMG (Huang et al., 2026) to Related Work (144), identify ARDY by name, and corrected both experimental citations (362).