- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
Feed-forward prediction of triangle soups from up to 24 unposed input images. Input images are DINOv2 encoded, and three heads predict camera poses, triangles, and pointmaps, respectively. The architecture looks very similar to VGGT with the addition of a Primitive Head, predicting triangles.
The method is efficient, and predicts textured meshes in 1s. Compared to related work, it produces higher quality geometry and NVS on exported meshes (Table 2). With native primitive rendering, the quality is worse (Table A).
Limited novelty: Adapts VGGT to also predict triangles, and regularizes the triangles with normals derived from the predicted point cloud and a monocular normal estimator.
The approach beats similar splatting methods (in the unposed image setting), but the resolution is too coarse to be useful in games or most simulation tasks. I would tone down the simulation-ready aspects, as the method predicts a triangle soup, not watertight, manifold meshes.
Critical strengths
The method is efficient, and directly predicts textured triangle soups from unposed images in 1s.
Visual quality improves significantly in mesh-rendering comparisons against related unposed splatting work.
Critical weaknesses
Limited novelty: Adapted VGGT to also predict triangles, and regularize the triangles with normals derived from the predicted point cloud and a monocular normal estimator.
Limited resolution: One triangle per pixel at 224x224 or 224x448 if I have understood the approach correctly.
The resolution limit and the fact that the output is a triangle soup, not manifold meshes makes the actual simulation or game applications very limited.
Questions for authors
I would like to see more details about the "Local-Global Attention" block. How large is it, how many blocks? Is it trained from scratch or finetuned? The left part of the proposed architecture looks very similar to VGGT with the addition of the Primitive Head for triangle prediction, so I would recommend discussing the differences in architecture and contrast this to VGGT. For example, was the number of features or attention blocks changed to incorporate the additional Primitive Head?
Out of interest, how do the predicted pointmap and camera poses compare against VGGT?
How are the number of views varied? Is there one model trained for each of 6, 12, and 24 views, or can the same model encompass all three view counts?
For simulation and game application, the low resolution output is a severe limitation. Does the method scale higher resolutions, and what would be the limiting factors?
In Table 2, I am a bit confused why NVS quality decreases with more views (for most methods)?
In Table 2, what appearance model is used? Is this mesh rasterization with SH shading?
Notation: Several equations are repeated in the text with different notation. This should be easy to clean up.
Response to follow-up comments on GGGS and PGSR
Thank you for suggesting GGGS and PGSR. We additionally evaluate both methods under the same setup as Q7, using 24 input views on 20 held-out DL3DV scenes. All metrics use primitive rendering. Time measures 30K steps of pure optimization for GGGS and PGSR, and one forward pass for TriSplat.
TriSplat achieves better results across all three rendering metrics with substantially lower computation time. We have added these results to Appendix E.5, Table M, and included references to both methods in the revised paper.