- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
LoomMesh reconstructs a textured triangle mesh from two posed images in a single forward pass, trained end-to-end from images only. Each pixel of a DepthSplat-style feature is unprojected to a 3D vertex with SH color; a candidate graph links pixel neighbors and cross-view reprojection neighbors. A topology reasoning operator runs a gated GRU exchange over the graph: each edge carries a conductance combining a coplanarity evidence term with a learned vote. Face opacity is the minimum conductance of its three edges. The same conductance weights message passing and makes faces differentiably deletable by the photometric loss; inference binarizes opacities so the exported mesh is what was rendered. The paper claims this is the first "feed-forward mesh splatting" method, demonstrates SOTA mesh-rendered NVS on RealEstate10K/DL3DV versus TSDF-meshed feed-forward Gaussian baselines and per-scene MeshSplatting, and ablates the operator.
Critical strengths
-
Joint depth–connectivity reasoning is well motivated and ablated. App. B.1 precisely explains why naive end-to-end mesh training stalls, and Fig. 5 shows the matcher stays trainable only with the operator. Table 3 (a) 19.29 → (g) 22.09 dB isolates its value at 0.03% extra parameters. This is the paper's most convincing, reusable contribution.
-
What is trained is what is exported. The renderer (analytic ray–triangle hits with exact per-ray ordering; soft band outside the triangle, no annealing schedule unlike 2DTS/MeshSplatting) makes the exported mesh identical to the rendered one. The Blender/Bullet demo is a concrete mini-deployment check. Measured efficiency is large: best mesh-rendered NVS (22.22 dB @ 256² RE10K; 18.92 dB zero-shot DL3DV) with ≈15–27× fewer vertices than the TSDF-meshed baselines (Tables 1–2). This advantage over TSDF-converted baselines is well established; its distinctiveness relative to other native-mesh feed-forward models remains to be shown (see Weakness 1).
Critical weaknesses
-
The "first feed-forward mesh splatting" claim is contradicted by existing public work. The paper frames its problem definition as its contribution ("a novel, more promising 3D reasoning problem"; "the very first solution"). Public work already exists: TriSplat (arXiv:2605.26115, May 2026; code and checkpoints released) — a feed-forward network whose native representation is oriented triangle primitives, directly exporting simulation-ready meshes with no intermediate extraction, trained/evaluated on the same RealEstate10K + DL3DV — and FTSplat (arXiv:2603.05932, Mar 2026) — feed-forward prediction of continuous triangle surfaces from calibrated views, no per-scene optimization or post-processing. Both predate the ICLR 2027 submission window and are uncited. TriSplat is also the stricter counterexample: it works in the more general unposed setting (camera poses are predicted jointly rather than given), and it makes the same argument the paper uses for its export-fidelity advantage — Gaussian baselines lose quality under lossy TSDF fusion, while a native-mesh model does not — so that advantage is not unique to LoomMesh either. What remains novel is narrower than claimed: learned, shared-vertex connectivity (gated faces) versus their point-map + normal-anchored triangles with export-time vertex merging — an incremental mechanism on an existing problem, so the vertex-for-Gaussian swap and pixel-adjacency prior (range-image meshing, Turk & Levoy 1994) cannot carry the framing the abstract and contributions rest on.
-
Every baseline number in Tables 1–2 is TSDF-degraded; the baselines' actual quality is absent. All Gaussian competitors are evaluated solely after depth-TSDF fusion + marching cubes (DepthSplat 16.13 dB, MVSplat 16.44, MeshSplat 16.55 on RE10K), whereas their original published two-view Gaussian rendering on RE10K is far higher: MVSplat 26.39 dB, DepthSplat 27.44 dB — levels comparable to or above LoomMesh's own mesh-rendered 22.22 dB (not a direct comparison: different test subset and mesh-vs-splat rendering, which is exactly why a reference column is needed). The "all methods evaluated as meshes" protocol is internally consistent, but "outperforms Gaussian-based methods in visual fidelity" is not inspectable without each baseline's original splatting-quality number beside the meshed one — especially since the paper itself criticizes TSDF conversion as a lossy separate step whose output is not what the network rendered. The per-scene MeshSplatting baseline is likewise taken outside its many-view operating regime and granted only two views.
-
The coplanarity gate caps representable protruding (convex) geometric detail. Eq. 5 cannot distinguish a depth discontinuity from a sharply raised detail: with the learned vote at initialization g_e = 0, any edge whose endpoints exceed each other's tangent plane by more than ρ* = 4 resolvable units is cut as a "boundary" — so small bumps are flattened by default. The gate therefore faces a dilemma between boundary identification and geometric detail: the only escape, the learned tolerance widening (up to ≈218 units), conversely keeps spurious faces across true boundaries (the App. B.1 failure mode). No experiment probes protruding/high-frequency geometric detail, and App. D's limitation list (image-grid mesh growth, occluded regions) does not mention this dilemma.
Questions for authors
-
Given TriSplat (arXiv:2605.26115) and FTSplat (arXiv:2603.05932), please (a) justify the "first"/"new problem" claims or withdraw them, and (b) provide a quantitative head-to-head with TriSplat under matched settings on RE10K/DL3DV — since TriSplat already claims the same TSDF-degradation argument used for your export-fidelity advantage, only a matched comparison can establish what learned gated connectivity adds over native triangle primitives.
-
Please add each Gaussian baseline's original (pre-TSDF) NVS numbers as a reference column in Tables 1–2, so the mesh-vs-original trade-off each method makes is visible.
-
With g_e forced to 0 (pure geometric gate), what fraction of edges at sharp convex details (e.g., a small bump spanning a few pixels) is cut? A small probe would pin the representation ceiling that Weakness 3 asserts.
-
For the baselines with different backbones (3DGS, 2DGS, MVSplat), how much of the geometry-metric gain comes from the coupled Depth Anything V2/V3 + DINOv2 priors rather than the mesh formulation (e.g., weaker-backbone ablation, or evaluation on a GT-mesh dataset such as DTU/ScanNet)? I recognize the DepthSplat comparison is backbone-matched and already controls for this factor.