- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The authors attempted to solve the inaccurate camera prediction problem in the current feed-forward GS reconstruction methods. They leveraged DA3 as their geometry backbone and proposed an RGGA module, which is claimed to obtain better 3DGS reconstruction. Then they proposed a render-aware camera refiner for better camera prediction. Overall, it is good. But I have some concerns about the contribution of RGGA and the motivation and objective of this paper. For example, it seems the goal is to get more accurate camera parameter estimation. Then, have related works like VGGT-Omega and Pi^3 already predicted accurate camera parameters? In the experiments, the authors mostly show the rendering results, but lack camera parameter prediction experiments.
Critical strengths
- The introduction of Render-Aware Camera Refiner is interesting. It replaces standard Test-Time Training (TTO).
- The discussion in the paper is very clear.
- The experiments are mostly concrete.
- Ablations on different backbones are good.
Critical weaknesses
- The authors should show comparisons of the reconstructed GS scenes after Gaussian Head with RGGA and those predicted by the existing feed-forward 3DGS reconstruction work to demonstrate the contribution of the introduced RGGA. If the ones after RGGA are worse than the existing SOTA feed-forward 3DGS reconstruction works. Then why not skip this module and jump to the camera refiner?
- The authors should do ablation studies on the middle module shown in Figure 2 to demonstrate that this module is important.
- After reading, I feel like the camera refiner is a feed-forward alternative to TTO. If so, the authors should show comparisons with TTO methods, especially the latency. I believe feed-forward methods should be more efficient than TTO methods.
- Why don't you compare with AnySplat under posed settings? Also, E-Rayzer might be a strong related baseline?
- Lack of camera parameter comparisons.
Questions for authors
- The authors claimed in the paper that the existing methods have errors in the estimated cameras, leading to ghosting and blurred details. Then why do the authors still use the predicted camera and depth to obtain the correspondence?
- In Line159 - 161. How do you sample pixels? Like what the authors said in Line 218 - 219? If so, I suggest moving this part to the front.
- In Line 187- 189. Did you use thresholds? If so, how do you deal with the scene scale differences?
- How do you inject into graph attention? An inductive bias in global attention?
- After Gaussian Decoding, how do you supervise the outputs? If using a rendering loss, which camera did you use? The ones from the Geometry Backbone? Or GT cameras?
- Can Render-Aware Camera Refiner work without the RGGA module? Can a more powerful GS prediction backbone eliminate the requirement of the RGGA module?
2 comments
Response to Reviewer EtJp
Due to the character limit, we address your additional questions in this second comment.
5. Additional questions
(a) Great question. NVS requires precise pixel-level alignment and is sensitive to camera/depth errors. However, for patch-level correspondences, the cameras and depth predicted by large visual geometry models provide useful geometric priors (visualized in Figure 8, Appendix E.2). Table 6(a) shows that using these coarse correspondences to guide attention improves NVS quality.
(b) Yes, we use the same sampling scheme. We will move the sampling details to their first occurrence in §3.2.
(c) Appendix A.2 specifies a relative-depth threshold of 10%, so rescaling the scene does not change the depth-consistency test.
(d) RGGA performs local self-attention on G: each patch provides the query, and its graph neighbors provide keys and values. The graph edges determine which neighbors each query attends to (§3.2; Appendix A.2).
(e) Reconstruction uses rendering loss on 8 additional target views (§3.5; Appendix B.2), following YoNoSplat's mix-forcing of GT and predicted source poses. Targets use aligned GT-based poses and the same intrinsics as the source branch (Appendix B.1).
(f) Yes, the camera refiner is independent of RGGA. It uses source images, predicted cameras, and rendered RGBD to refine cameras. Our frozen camera refiner improves other GS methods' unposed NVS quality without fine-tuning (Tables 4 and 10, Appendix D.3). These gains demonstrate that the refiner generalizes across Gaussian reconstruction methods.
We hope these clarifications and additional results address your concerns. We welcome any further questions.
Response to Reviewer EtJp
Thank you for the detailed feedback and concrete suggestions for improving the paper. To address the questions in your summary, we clarify that our objective is high-fidelity novel view synthesis from unposed images, with rendering quality as the primary focus. Within HiFiNVS, RGGA is part of the Gaussian head and improves cross-view feature aggregation for reconstruction. The camera refiner is a separate stage that uses rendering feedback to improve NVS quality by correcting source-camera errors. Camera accuracy therefore serves the NVS objective, rather than being a separate goal. We address your concerns below.
1. Reconstruction comparisons and Gaussian head ablations (Weaknesses 1–2)
Our main experiments compare HiFiNVS with existing feed-forward 3DGS methods. Tables 1–2 show that HiFiNVS achieves state-of-the-art NVS quality with GT cameras (ReSplat-re uses multi-step refinement). For unposed inputs, the separate camera refiner improves rendering quality by reducing artifacts caused by errors in the backbone’s predicted cameras.
To isolate RGGA’s contribution within the Gaussian head (the middle module in Figure 2), we compare two ablated variants with the full model. We apologize for the unclear ablation labels: “w/o graph attention” in Table 6(a) corresponds to removing RGGA's reprojection-guided aggregation while retaining frame attention; “Global + frame attention” replaces RGGA's graph attention with standard global self-attention. The full model achieves better NVS quality under GT cameras, establishing the benefit of RGGA.
2. Quality and latency versus test-time optimization (Weakness 3)
Thank you for suggesting this important comparison. We use Adam with a learning rate of 10⁻⁴ to minimize a source-view rendering loss with respect to camera intrinsics and extrinsics. TTO-10 and TTO-20 use 10 and 20 camera optimization iterations, respectively. We keep the Gaussians fixed during optimization and rebuild the scene once with the updated cameras. We evaluate 140 DL3DV scenes per backbone at 480P with 16 input views. Each quality entry is PSNR (dB) / corrected AUC@5° (%) (both ↑):
In this comparison, our refiner yields higher PSNR and pose AUC at lower measured latency than both TTO variants. All variants use the same target-camera evaluation procedure. Time cost is the average runtime for camera correction and rebuilding on an RTX 5090. Our refiner has only 18.3M parameters, including an 11.7M frozen image encoder.
3. Posed AnySplat comparison and E-RayZer baseline (Weakness 4)
AnySplat's official model uses unposed inputs and has no GT-source-camera inference interface; Table 2 evaluates this native setting. E-RayZer’s released DL3DV evaluation uses 256×256 images. We found no released high-resolution checkpoint, so we exclude E-RayZer from our high-resolution comparison. We will expand Table 7 (Appendix C.1) to clarify these configurations and comparison choices.
4. Camera parameter comparisons (Weakness 5)
Table 3 reports camera accuracy alongside NVS quality; Table 8 (Appendix D.1) extends the reported comparison to 8/16/32 views across DA3, π³, and VGGT. Our additional comparison above confirms improvements in both NVS quality and camera pose accuracy.
5. Additional questions
(Due to the character limit, please see Part 2 for our responses.)