- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
Feed-forward 3D foundation models (VGGT, Pi3) are bottlenecked by the quadratic cost of global self-attention, capping inputs at ~518p and blurring fine geometric detail. This paper proposes Hybrid-VGGT, an asymmetric dual-branch architecture: a low-resolution branch (initialized from pretrained VGGT, max side 518px) performs global multi-view reasoning and camera pose estimation, while a parallel Hybrid Detail Extractor (HDE) processes 1036px inputs with a cascade of hybrid blocks (depth-wise conv → linear attention à la Shen et al. 2021 → depth-wise conv), producing multi-scale detail features at O(N) cost. A customized multi-scale DPT head (RefineNet-style top-down path) progressively injects resolution-matched HDE features additively into the global pyramid at every stage, yielding native 1036p depth and point maps. Trained end-to-end on 16 datasets (64×A800, 160 epochs), the method reports the best mean rank on camera pose (1.62), multi-view depth (1.6), and point map estimation (1.67) versus Fast3R, CUT3R, FLARE, VGGT, Pi3, and DAGE, while running at 38.56 FPS on 1036p 100-frame clips (vs. 3.12 for VGGT) on a single RTX 5090.
Critical strengths
The problem targets real-application bottlenecks and is well-formulated.
The architectual design and illustration is clear and self-consistent.
The ablation is informative, supporting the claim that detail extraction for geometry needs dedicated local inductive biases rather than off-the-shelf semantic features.
Critical weaknesses
The difference and improvements over DAGE is not evident. Comparisons to DAGE only exists in Table 3.
For VGGT and Pi3, why evaluate them by "518p input then upsample to 1036p"? As Tab. 1 points out, it is operable for VGGT and Pi3 on 1036p, although inefficient. Using this fairer setting will demonstrate its actual improvement.
The method is instantiated exclusively on VGGT, yet newer open backbones (VGGT-, DA3, etc.) have since demonstrated stronger geometry and pose accuracy at comparable resolutions. It also bears on real-world impact as practitioners choosing a feed-forward geometry model now start from the newer ones, so a method pinned to VGGT risks limited adoption upon release. Anyway, it is a "nice-to-have" suggestion. Also, the results of VGGT-, DA3 are not included in comparison. It is unknown whether the newer backbones would surpass Hybrid's result in high resolution.
It is also suggested to include performance of your proposed module initialised with these backbones.
Questions for authors
Major Issues
Regarding efficiency, although it outperforms VGGT, how does it compare with LiteVGGT/FastVGGT/StreamVGGT/InfiniteVGGT (just pick a few) and DAGE under such high-resolution setting, and how much improvement in performance it obtained among others?
Where does 1036p depth ground truth come from for each dataset (especially 7-Scenes, whose sensor depth is 640×480)? Is GT also upsampled, and if so, how do you interpret boundary-sharpness wins against GT that contains no real high-frequency detail? I do suggest following the evaluation of DAGE (See its Tab. 1), to not strictly setting 1036p.
Figure 3 shows better details of proposed method. But I would suggest increasing point size or setting input resolution to 1036p for VGGT & Pi3, otherwise it isn't a fair comparison.
Minor Issues
The definition of "518p"/"1036p" in the paper is "resized to a maximum dimension of 518/1036 pixels," i.e., the long side. Yet in real-world, "p, progressive scan" mostly refers to short side, (e.g.: 1080p is 1920$\times$ 1080 under 16:9 aspect ratio). Please follow traditions.
I fixed the review in last minute as I found out CARVE isn't yet open-sourced, making you unable to compare. Please point it out once encountering such issue.
Citations of CARVE and DAGE are not accepted version. Please update them with CVPR 2026 published version.
Although I can not recommend acceptance with current version, I will certainly raise my score toward acceptance if the questions and weaknesses are resolved.
3 comments
Response to Reviewer 289z (Part 2/2)
Weakness 4. HDE transfer to newer backbones.
We agree that transfer to newer backbones is a valuable extension. It requires backbone-specific integration and retraining, which exceeds our available training resources, and we leave it to future work. The completed DA3 comparison addresses the immediate practical question: whether the current VGGT-based model remains competitive with a newer released model at high resolution. Its accuracy and throughput advantage on the added benchmarks supports that use case; cross-backbone transfer remains to be evaluated.
Major Question 1. Efficient VGGT variants and DAGE at high resolution.
At the same LR518 global stream and 1036 external input, Ours improves all 8 pose metrics, all 5 depth AbsRel scores and all 3 DTU metrics over DAGE. On the added Bonn test, AbsRel/δ1 is 0.0405/0.9878 versus 0.0411/0.9865. Complete inference on 100-frame CO3Dv2 clips reaches 38.56 versus 20.08 FPS (1.92×), with memory 20.11 versus 20.27 GB.
DAGE-LR252 uses a smaller global stream to reduce memory; its Bonn AbsRel is 0.0568 versus 0.0411 for LR518. The matched LR518 comparison shows our accuracy–speed advantage without reducing global-stream resolution. Against FastVGGT at 1036 input, Ours has lower Bonn AbsRel (0.0405 vs 0.0731) and 4.73× CO3Dv2 throughput.
Accuracy: Bonn, inputs 518×392/1036×784, GT 1036×784, one scale/clip; Bonn is absent from our training mixture. Resources: CO3Dv2, 100 frames, 518×294/1036×588, RTX 5090, complete inference and the same timing scope.
Table 1. Bonn accuracy / CO3Dv2 resources.
| Method/long side (px) | AbsRel↓ | δ1↑ | FPS↑ | Mem↓ |
|---|---|---|---|---|
| VGGT/518 | 0.0495 | 0.9723 | 44.69 | 17.51 |
| VGGT/1036 | 0.0734 | 0.9511 | 3.12 | 28.98 |
| Pi3/518 | 0.0421 | 0.9815 | 56.11 | 17.42 |
| Pi3/1036 | 0.0456 | 0.9800 | 5.19 | 23.35 |
| FastVGGT/518 | 0.0489 | 0.9737 | 46.58 | 17.86 |
| FastVGGT/1036 | 0.0731 | 0.9510 | 8.15 | 19.31 |
| DA3-Large-1.1/518 | 0.0687 | 0.9264 | 55.74 | 15.47 |
| DA3-Large-1.1/1036 | 0.0768 | 0.8937 | 10.91 | 20.51 |
| DAGE (LR252)/518 | 0.0559 | 0.9771 | 50.73 | 11.98 |
| DAGE (LR252)/1036 | 0.0568 | 0.9772 | 26.22 | 19.21 |
| DAGE (LR518)/1036 | 0.0411 | 0.9865 | 20.08 | 20.27 |
| Ours/518 | 0.0418 | 0.9798 | 40.09 | 19.32 |
| Ours/1036 | 0.0405 | 0.9878 | 38.56 | 20.11 |
Major Question 2. GT sources and the resolution of 7-Scenes depth.
The common evaluation grid provides a consistent reference for comparing all methods: identical GT depths, valid-depth masks and per-sequence scale alignment. GT comes from supplied rendered depth for Sintel/BlendedMVS, scans for ETH3D, sensors for 7-Scenes and registered geometry for ScanNet++. Resampling changes the scoring grid, not the information in GT. In particular, 7-Scenes depth originates at 640×480, so the current scores measure agreement with sensor-supported depth; finer boundary appearance in Figure 3 is qualitative.
We will additionally report AbsRel/δ1 at native GT resolution, keeping GT unchanged and resizing predictions to its grid (640×480 for 7-Scenes). This will test whether the accuracy comparison is preserved without GT resampling. The DTU scan-based gains already provide separate quantitative evidence of reconstruction quality.
Major Question 3. Figure 3: matched inputs and point size.
We will revise Figure 3 with actual 1036-input VGGT/Pi3 and Ours, identical viewpoints and point size, and explicit input labels. This update is pending. The completed matched-input depth and point-map experiments establish the quantitative comparison; the revised figure will align the visual comparison with that setting.
Minor Question 1. Explicit input dimensions.
We use “input long side 518/1036 pixels” and will replace the “p” suffix throughout the manuscript. Method suffixes in multi-dataset tables denote long-side pixels. Single-dataset shapes are explicit: Bonn 518×392/1036×784; CO3Dv2 resources 518×294/1036×588.
Minor Question 2. CARVE implementation availability.
CARVE inference code and checkpoints were unavailable when these comparisons were prepared. We will state this explicitly; the added experiments include the runnable DAGE, FastVGGT and DA3 baselines.
Minor Question 3. Update the reference versions.
Thank you. We will update DAGE's citation to its official CVPR 2026 proceedings version and check the remaining reference metadata.
As the discussion deadline approaches, we would appreciate your feedback on the expanded DAGE comparisons and actual 1036-input VGGT/Pi3 evaluations across pose, depth and point maps. At matched 1036 input, our method improves all eight pose metrics and all five depth scores over these baselines. We also added FastVGGT and DA3 comparisons and clarified the GT resolution and evaluation protocol. Could you let us know whether these additions address your main concerns, or which remaining issue would benefit from clarification? Thank you for your time and consideration.
Response to Reviewer 289z (Part 1/2)
Thanks for your careful and valuable comments. These comments have been of great value to my approach. We will explain your concerns point by point.
Our contribution is the geometry-oriented detail pathway and its integration with global reasoning and dense refinement. HDE combines local spatial processing with per-view context; pre-Aggregator injection allows these cues to inform camera prediction, while multi-scale DPT fusion supports dense reconstruction. This targets how efficiently high-resolution information is used within the LR/HR framework.
The original Hypersim-test ablations quantify the extractor and fusion choices: replacing DINO with HDE lowers XYZ error 0.2490→0.2262 (9.2%); removing the Feature Injector raises it to 0.2387. Separately, Tables 1–3 (Tables 2–4 in manuscript) now compare DAGE-LR518 at the same 1036 external input. Ours improves all 8 pose metrics, all 5 depth AbsRel scores and all 3 DTU metrics, with DTU completion error falling 1.811→1.562 (13.7%). These additions establish benefits across tasks beyond the original depth-only comparison.
Tables 1–3 (Tables 2–4 in manuscript) now include VGGT/Pi3 with actual 1036 inputs, including DTU. At matched input resolution, Ours improves all 8 pose metrics and all 5 depth AbsRel scores over both. The advantage therefore persists when the baselines receive the same number of input pixels. Each Ours-518/1036 pair uses the same checkpoint and protocol; only external input resolution changes.
Table 1. Camera pose (Table 2 in manuscript).
Table 2. Depth (Table 3 in manuscript).
Table 3. Point maps (Table 4 in manuscript).
The added DA3-Large-1.1 experiment shows that the current VGGT-based model remains competitive with a newer released geometry model on the Bonn test. At 1036×784, Ours achieves AbsRel/δ1 of 0.0405/0.9878 versus 0.0768/0.8937. On the separate CO3Dv2 resource benchmark at 1036×588, throughput is 38.56 versus 10.91 FPS (3.53×). VGGT-Ω evaluation awaits checkpoint access approval from hugging face; we will add it once access is granted.