- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes Latent Bridge, which maps generated video latents to the feature space of a frozen VGGT-Ω model. It thereby predicts cameras, depth, and point clouds without decoding the latents to RGB and re-encoding the frames for geometry. The authors train separate Wan2.1 and V-RAE bridges through feature distillation, without ground-truth geometry or executing the downstream geometry heads during bridge training. On CO3Dv2 and WildRGB-D, the bridge pathway gives point-cloud results close to an RGB-to-Geometry pathway and reduces latency. The Wan2.1 variant also has the lowest reported end-to-end latency among the compared systems.
Critical strengths
-
The frozen feature interface is a practical way to reuse a pretrained geometry model without training its aggregator or prediction heads. The supervision and trainable modules comparison in Table 6 shows a substantial reduction in per-step training time and memory when the bridge is trained at the feature level.
-
The paper evaluates two distinct video latent representations. With the generated latents and VGGT-Ω backend held fixed, the proposed bridge maintains broadly comparable reconstruction quality while reducing inference time. These controlled comparisons provide convincing evidence for the effectiveness of the proposed interface. Furthermore, Table 1 demonstrates a clear system-level latency advantage for the Wan2.1 variant under the reported experimental setup.
Critical weaknesses
-
The technical novelty is limited. Gen3R already aligns VGGT-derived geometry latents with video latents, while VIST3A stitches video latents to a pretrained 3D model. This paper’s main distinction is feature-only alignment to a frozen VGGT-Ω interface. Table 4 shows that the full Bridge outperforms a simple variant in matching teacher features and depth, but does not establish a matched parameter budget. It is therefore unclear whether the gain comes from the proposed design or greater model capacity. The ablation also does not show whether this gain improves point-cloud reconstruction from generated videos.
-
Limited evidence for generalization under challenging conditions. The paper claims that the Bridge can be reused across generators sharing the same video latent space, but provides only qualitative results for this claim. Its reconstruction performance on videos generated with more challenging camera trajectories and on longer sequences also remains unclear. Quantitative point-cloud results in these settings, compared with the RGB→VGGT-Ω route on the same generated videos, would strengthen the evaluation. For longer sequences, the authors should also clarify how they are processed and assess geometric consistency.
Questions for authors
-
Novelty. Gen3R and VIST3A have already connected video latents with 3D reconstruction representations. Beyond mapping to a fixed VGGT-Ω feature interface while keeping the geometry model frozen, what is the key technical novelty of the proposed Bridge relative to these methods?
-
Architecture versus capacity. Are the simple Bridge baseline and the full Bridge in Table 4 matched in parameter count and computational cost? Could you provide a capacity-matched comparison, including geometry results on generated videos, to distinguish gains from the architecture from gains due to model capacity?
-
Effect of the geometry backbone. Gen3R uses VGGT, whereas your method uses VGGT-Ω. Could you provide a controlled quantitative comparison using the same geometry backbone? For example, evaluating Gen3R with VGGT-Ω or applying your method to VGGT.
-
Generalization. Could you report quantitative point-cloud reconstruction results for more challenging camera trajectories, longer sequences, and other compatible generators? How does the method handle longer sequences and maintain geometric consistency? In these settings, how does the Bridge compare with the RGB→VGGT-Ω route on the same generated videos?
Thank you for your review. We have conducted additional experiments to address your concerns and provided detailed responses. We look forward to your further feedback!
W1&Q1: Key technical novelty of the proposed Bridge relative to these methods
Our core innovation lies in aligning the generative latent space with the reconstruction (DINO) latent space, rather than jointly generating RGB and geometry or training an entirely new geometry decoder, as illustrated in Figure 1 of the main paper.
Difference from GEN3R: Our method follows a fundamentally different paradigm. GEN3R jointly generates RGB and geometry tokens, as illustrated in Figure 1 (a) of the main paper, whereas our method trains a model to bridge the two representations.
Difference from VIST3A: VIST3A selects a stitching layer for each model pairing and adapts the downstream geometry network via LoRA. In contrast, our method focuses on learning a mapping from video latents to the geometry feature space. This offers two advantages: (1) training requires neither the geometry aggregator nor the prediction heads, reducing computation and GPU memory usage; and (2) the pretrained geometry model’s parameters remain unchanged, avoiding adaptation-induced changes to its pretrained capabilities while enabling reuse of the aligned features for other downstream tasks with compatible DINO feature interfaces.
W1&Q2: Architecture versus capacity.
Thank you for raising this concern. We have extended Table 4 to report parameter counts and downstream 3D reconstruction results.
The interpolation and Simple variants have approximately 8.83% fewer parameters, primarily because replacing the learned temporal upsampling module with parameter-free interpolation necessarily reduces the parameter count unless additional capacity is introduced elsewhere.
In terms of reconstruction quality, the interpolation variant and Simple baseline each perform better on one dataset but worse on the other, whereas Full offers a more balanced trade-off across the two datasets. Moreover, Table 4 shows that Full achieves the best depth-fitting metrics while maintaining competitive feature alignment.
Q3: Effect of the geometry backbone.
We use VGGT-Ω because its visual encoder and V-RAE are both based on DINOv3, whereas the original VGGT uses DINOv2. This choice provides a more compatible feature space for alignment. We additionally train a V-RAE Bridge to align with the original VGGT, with the results shown below:
As shown in the table, the VGGT-based variant performs better on CO3D but slightly worse on WildRGB-D, suggesting that VGGT and VGGT-Ω achieve broadly comparable performance within our framework. Adjusting the training-data mixture may enable the VGGT-based variant to achieve more balanced performance across both datasets, but time constraints prevented us from conducting additional training experiments.
W2&Q4: Generalization.
Since our original model was trained on fixed-length sequences of 49 frames, inference on longer, more complex sequences requires further fine-tuning on longer sequences. We conducted experiments by fine-tuning on sequences of 100 and 150 frames, with the results shown in the table below.
The results show that, after fine-tuning on longer sequences, our method still achieves geometric reconstruction quality comparable to that of the RGB decoding pathway, indicating that Bridge can scale to longer sequences with fine-tuning. In fact, other methods, such as GEN3R, also struggle to support longer sequences and require more costly fine-tuning. Since our method only requires fine-tuning the Bridge, the training cost is lower, further highlighting its advantage.