- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper presents AO-Flow, a framework for improving single-image 3D asset generation by better utilizing and optimizing video-generated multi-view observations. The proposed method consists of two main components. First, it introduces a cross-stage regional conditioning mechanism for TRELLIS.2. The Sparse Structure (SS) stage processes 49 generated video frames and records region-specific source identities and attention weights, which are subsequently reused by the Shape stage with its own content attention and spatial priors. The two stages are adapted sequentially to ensure consistent information transfer. Second, the authors introduce an asset-oriented video post-training strategy based on Flow-GRPO. By freezing the adapted 3D receiver and optimizing the video generator using final 3D asset rewards, the framework aims to improve geometric completeness and hidden-surface reconstruction. Experiments on Objaverse-derived objects and GSO demonstrate improvements in geometric reconstruction metrics, particularly hidden-region F-score, compared with several existing 3D generation approaches.
Critical strengths
- The paper is well-written and easy to follow.
- The paper addresses a practically relevant problem by preserving region-specific multi-view evidence for fine-grained 3D reconstruction.
- The framework coherently combines regional source selection, sequential receiver adaptation, and asset-level video optimization guided by final reconstruction quality.
- Extensive comparisons, ablations, and efficiency analyses provide useful insights into source selection, spatial priors, training objectives, geometry, and input-view preservation.
Critical weaknesses
- The methodological novelty and specific contribution of cross-stage regional memory remain unclear, as gains over alternative routing strategies are small and may partly result from retained attention mass or spatial priors.
- Statistical reliability is insufficient because several conclusions rely on small improvements without multi-seed results, confidence intervals, or significance tests.
- Asset Flow-GRPO provides only marginal gains over Asset-DPO despite higher computational cost and slightly worse input-view preservation, weakening its practical justification.
- Generalization to real photographs and imperfect generated views remains underexplored, particularly under viewpoint drift and geometric inconsistencies.
- The complete pipeline’s computational overhead is unclear because reported efficiency excludes video generation and other shared stages; an end-to-end comparison is needed.
- Figures 2 and 3 are overly dense and difficult to read. Clearer vector-based diagrams, larger text, and simplified layouts would improve technical communication.
Questions for authors
- Could the authors better isolate the contribution of cross-stage source memory from attention mass, spatial bias, and source allocation through matched controls?
- Are the improvements of Region-4 over Shape-selected-4 and Flow-GRPO over Asset-DPO statistically significant across multiple seeds and inference draws?
- What practical advantage does Flow-GRPO offer over the cheaper Asset-DPO? Please provide compute-matched comparisons and analyze reconstruction–fidelity trade-offs.
- How robust is regional source selection to camera errors, temporal inconsistencies, and hallucinated geometry? Would training with generated videos improve robustness?
- Could the authors report complete image-to-3D runtime and peak memory, including video generation and encoding, and evaluate on real photographs?
- Could Figures 2 and 3 be redesigned with larger text, simpler layouts, and clearer data flows and optimization scopes?
2 comments
Reply to Authors
Thank you for the additional experiments. I found the comparison with Shape-selected-4 particularly helpful. Reusing the sources selected by SS gives a small gain in hidden-region F-score while reducing both runtime and memory. This addresses my main concern about the value of cross-stage reuse.
I also read the other reviewers’ comments and share the concern raised by Reviewer DHKb about the reliability of generated views as a geometric prior. The robustness tests and real-photo results are encouraging. However, the real-photo comparison evaluates the full system, so it remains difficult to tell how much of the gain comes from the generated views and how much comes from adapting the TRELLIS.2 receiver. I also found the compute-matched comparison informative. Flow-GRPO produces a useful checkpoint earlier, but its final advantage over Asset-DPO remains uncertain.
The rebuttal has strengthened my assessment of the regional conditioning method. My remaining concerns about the video prior and the added value of Flow-GRPO lead me to maintain my original rating of 2 (weak rejection).
Response to Reviewer M6XT: results for the six requested controls
Thank you for the concrete list of controls. We ran all six. Unless marked single-seed, H-F averages 3 training seeds × 4 inference draws, with paired bootstrap 95% CIs over 454 objects, so values can differ slightly from single-run tables.
Q1 (W1). Contribution of cross-stage memory
Each row removes one factor from Region-4:
Region-specific frame identity is the largest factor, ahead of spatial bias, allocation and mass. Removing the bias from both Global-4 and Region-4 leaves a 0.022 gap, so it does not explain the regional gain. These per-region mass rows replace Table 12 (reply to L12K). Region-4 adds 0.8 s of receiver time over Global-4 (Table 2).
UMI3D, ROAR-3D and Stream3D choose views within one stage or with a separate probe. AO-Flow reuses the choice SS makes on its 16³ grid as the prior for Shape's 32³ cells, which the last row isolates. Against Shape-selected-4, which probes all 49 frames at every Shape step, reuse gains 0.006 H-F at 98.2 vs. 118.6 s and 32.0 vs. 38.4 GB.
Q2 (W2). Significance
Region-4 over Shape-selected-4 excludes zero, as do the other interface, reward and system contrasts. GRPO over DPO does not, and Q3 shows where they differ in practice.
The revised tables report these means and CIs.
Q3 (W3). Flow-GRPO vs. Asset-DPO
Rows below 1,000 updates are checkpoints of the same GRPO runs.
At equal compute the two are level (0.667 at 778 GPU-h vs. 0.666 at 790). They differ in when compute pays off. DPO spends 690 of its 790 GPU-h on its pool before the first update (Table 13), while GRPO improves throughout. GRPO reaches 0.664 at 518 GPU-h, before DPO would have started training.
The preservation weight λ_o sets the reconstruction–fidelity trade-off. From λ_o = 0 (Table 4) to 4, input IoU rises from 0.873 to 0.911 while H-F falls from 0.678 to 0.666, and at λ_o = 4 GRPO matches DPO on both.
Q4 (W4). Robustness and training on generated videos
Region-4 leads under each error type, and tuning Shape on generated videos helps most where videos are worst. Single-seed, same runs as our L12K and DHkb replies:
Tuning adds 0.017 under large drift and 0.008 on clean videos, where the same budget on GT renders gives 0.642 (Table 10). For hallucinated geometry, a wrong part repeated in 4 adjacent frames (8% of the video) drops to 2% of Shape's sources, and Region-4 degrades no more than Full-49 (reply to DHkb).
Q5 (W4, W5). End-to-end cost and real photographs
Table 2's receiver times run from DINO encoding to mesh export (App. I), so we now add video generation (one H200, batch one). Real photos are 200 OmniObject3D objects, with the scan as reference.
On real photos AO-Flow leads Pixal3D, the strongest Table 1 baseline, by 0.015 H-F, and the 8-step sampler keeps the lead at 38% less runtime. The extra time over single-stage generators is mostly video generation, which takes 64% of runtime and sets the 68 GB peak (the receiver needs 32 GB). The table is now in Sec. 4, and 50 in-the-wild results are at 4:20 in the video.
Q6 (W6). Figures 2 and 3
Both are redrawn as vector graphics with text of at least 8 pt. Fig. 2 shows S1, S2a → S2b and S3 as separate panels and marks what each stage trains. Fig. 3 drops the repeated 49-frame strip and traces one path from SS capture to Shape rereading.
All six points are addressed in the revision. If these results resolve your concerns, we would welcome an updated rating.