- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper presents incremental work building on VGGT and Reloc3r. Given multi-view images with known poses, the goal is to estimate the pose of a query image. The authors propose injecting the known camera poses into the camera tokens of VGGT and reducing the VGGT output head to predict only the camera parameters. The model is initialized with VGGT pretrained weights and fine-tuned on mixed datasets similar to those used by Reloc3r. Experiments show degraded performance on image pairs but improved performance with multi-view inputs and ground-truth pose inputs.
Critical strengths
- The idea of injecting known poses into VGGT to improve accuracy is valid.
- The results of visual localization in indoor and outdoor scenes are superior to those of several baselines.
Critical weaknesses
- Limited novelty and insufficient method tailoring.
This work is largely incremental, and the method section essentially builds on / reviews VGGT and Reloc3r. It would be helpful to emphasize the unique improvements over VGGT, Reloc3r, and OmniVGGT [A]. The design is not carefully tailored to the problem, e.g., it predicts intrinsics (focal lengths) but does not use them, and it injects only pose but not intrinsics. The intrinsics indeed have an impact on camera pose estimation, but this is not analyzed in the paper.
- More importantly, the paper suffers from overclaimed and incomplete experimental evaluation.
(a) The claim that the method outperforms both non-pose-regression and pose-regression approaches is not supported. In the pairwise setting, it is noticeably worse than prior methods such as Reloc3r and VGGT (Table 1). This is surprising and suggests that the proposed pose injection may even hurt VGGT. Moreover, the comparison is unfair: the multi-view series uses 10 additional images and their ground-truth poses as input.
(b) The claim of performance comparable to non-regression methods is not convincing. Non-regression methods typically achieve 8–14 cm error, whereas the proposed method has about 29 cm error (Table 2).
(c) Comparisons with state-of-the-art methods are missing. For example, the proposed method can be regarded as a simplified version of OmniVGGT [A], but this is neither discussed nor compared. For non-regression methods, comparisons with concurrent works such as RoMa v2 [B] and LoMa [C] are missing. Since the paper addresses multi-view pose estimation, multi-view feature matching methods such as CoMatcher [D] should also be considered and compared.
(d) Compared with pairwise methods (e.g., DUSt3R and Reloc3r), the proposed method relies on global attention over multi-view images, which incurs O(N^2) complexity and GPU memory usage with respect to the number of images. However, GPU usage is neither reported nor compared.
[A] OmniVGGT: Omni-Modality Driven Visual Geometry Grounded Transformer. CVPR 2026.
[B] RoMa v2: Harder Better Faster Denser Feature Matching. ECCV 2026.
[C] Loma: Local Feature Matching Revisited. ECCV 2026.
[D] CoMatcher: Multi-View Collaborative Feature Matching. CVPR 2025.
Questions for authors
-
It is surprising that injecting camera pose hurts performance in the pairwise setting. Why?
-
Can the authors verify the claimed advantage over OmniVGGT?
Minor points and suggestions
-
L014: The motivation regarding “unfamiliar and ever-changing environments” is not actually studied in this work.
-
The term “unseen scene” appears to be used to mean “no training.” However, visual re-localization is not an unseen scene problem: it requires a database of images and pre-extracted features (e.g., NetVLAD), and the query image is captured during a revisit. Therefore, “unseen” is inaccurate in the problem definition.
-
L117: It is unclear why the method is described as a “two-stage re-localization framework.” Is image retrieval considered the first stage before VGGT? Or is scale recovery regarded as a second stage after VGGT?
-
L231: What is the “L-th transformer block”? The last layer's output?
-
Fig. 1: The features “No per-scene training” and “Zero-shot generalization” appear to refer to the same feature. The training is actually mixed-scene training.
-
Fig. 2 is somewhat misleading: why does scale recovery use an additional camera view, as shown in the figure? Please clarify.
Rebuttal response for reviewer DQdY
We thank reviewer DQdY for their thoughtful feedback and for noting that our visual localization results in indoor and outdoor scenes are superior to several baselines. We address each of their questions below.
Q1. Why does injecting camera pose hurt performance in the pairwise setting?
In the pairwise setting, no informative pose is injected. With a single reference image, the reference pose defines the coordinate frame and is therefore always the identity, while the query pose is predicted by the model. The model thus receives no pose information and operates analogously to Reloc3r or VGGT in this setting. Consistent with this, MultiLoc performs on par with or better than VGGT on ACID and MegaDepth, and trails it only on ScanNet-1500 under the pairwise setting. We attribute this gap to the training data, as VGGT is trained on ScanNet, so ScanNet-1500, although held out, is in-domain for VGGT, whereas MultiLoc is fine-tuned on ScanNet++, which shifts it away from the ScanNet domain.
Furthermore, we include the pairwise results in Table 1 for completeness. The main contribution of the paper is the multi-view pose regressor, where pose injection is informative. The main paper's Table 2 and Figure 5 show that accuracy improves as more posed reference images are provided compared with running pairwise inference. Therefore, we do not believe that the camera pose hurt performance in the pairwise setting, as there is no 3D sub-scene context formed for grounding the query, and thus it should just be treated as a plain image-only variant similar to VGGT for completeness, which is not the claim of our work.
Q2. Can the authors verify the claimed advantage over OmniVGGT?
We evaluated OmniVGGT, a concurrent work, on visual re-localization and camera pose estimation using the same reference-query sets as MultiLoc, with inputs prepared following OmniVGGT's official pipeline (see Table R1 below). MultiLoc outperforms OmniVGGT on all the mentioned benchmarks. We note that OmniVGGT was evaluated in its strongest configuration, with both intrinsics and extrinsics provided, whereas MultiLoc uses extrinsics only, and that OmniVGGT is trained on a substantially larger dataset collection. We attribute such improved performance to our architecture, which is designed specifically for the re-localization task. We will further add this comparison to the revised paper.
Table R1: Comparison with OmniVGGT. Median pose error (cm // ∘, ↓) averaged over all 5 Cambridge scenes and all 10 WaySpots scenes, and AUC@5 // AUC@10 (↑) on ACID. Bold denotes the best result.
Q3. The claim of performance comparable to non-regression methods is not convincing.
We believe the mentioned comment only points to a limited evaluation metric on a single benchmark of the Cambridge dataset. Our results per benchmark are:
Because of these observations, we believe our balanced claim of being comparable is justified here.