- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes a new representation for native mesh generation. It first generates a triangle soup of disconnected triangles using a combination of BVH and octree structures, then stitches these triangles together through a post-processing method to obtain the final mesh. During stitching, validity checks, including mesh manifoldness checks, are applied to ensure the quality of the resulting mesh.
Critical strengths
- The idea of generating triangles first and then stitching them into a mesh is very interesting. In particular, the triangles are not generated directly in a straightforward manner; instead, the method combines BVH and octree structures. The ablation results in Table 4 also demonstrate the effectiveness of this representation.
- I like the rendering style and presentation of the paper, and the diagrams are clear and easy to understand.
- The triangle-stitching module appears relatively independent of the main generation pipeline. It seems that it could be packaged as a standalone module for use with other triangle-soup generation methods.
Critical weaknesses
- The paper does not describe the detailed design of the VAE or clearly explain its relationship to TRELLIS.2’s SC-VAE and OctFormer. This may make it difficult for the community to reproduce the network architecture.
- It is unclear why the authors sort triangle vertices by their coordinates during preprocessing. Since a triangle’s orientation depends on its vertex ordering, this encoding scheme appears to discard face-orientation information.
Questions for authors
- Could the authors provide a more detailed description of the VAE architecture? For example, which components from TRELLIS.2 are incorporated into an OctFormer-based architecture, or, conversely, which components from OctFormer are incorporated into TRELLIS.2’s SC-VAE? Additionally, does the flow model use the architecture of the original TRELLIS.1 or TRELLIS.2?
- Could the authors explain the rationale for sorting triangle vertices by their coordinates? Could the original vertex order be preserved when generating triangles to ensure correct face orientations in the generated mesh?
- The triangle-stitching module appears relatively independent of the main generation pipeline. I believe it could be packaged as a standalone post-processing module for triangle soups, making it applicable to a broader range of triangle-soup generation methods. I would be interested in hearing the authors’ perspective on this possibility.
2 comments
Response to rebuttal
I thank the authors for their clarifications and for the additional experiments on face orientation and EdgeMatch. The response addresses my main concerns, so I will maintain my current rating and lean toward acceptance. I encourage the authors to include a discussion of potential extensions of the approach in the camera-ready version.
Response to Reviewer mTL3
Thank you for recognizing our face-first approach, OctBVH representation, and visual presentation, as well as for your constructive questions on network architecture, face orientation, and standalone stitching.
1. VAE and Flow Model Architectures (W1, Q1)
2. Vertex Coordinate Sorting and Face Orientation (W2, Q2)
Following previous works, including MeshGPT (Siddiqui et al.), MeshAnything / V2 (Chen et al.), MeshRipple (Lin et al.), and MeshFlow (Sun et al.), we sort triangle corners canonically by coordinates so that the three predicted vertex slots match the ground-truth order one-to-one. This provides deterministic regression targets and prevents inconsistent vertex ordering (or taking the minimum loss over cyclic vertex permutations) from destabilizing triangle coordinate supervision. Preserving cyclic order starting from the lexicographically smallest corner is also a viable option to retain winding, while in our pipeline we recover consistent orientation during stitching as described below.
Prior methods, such as MeshAnything V2, BPT (Weng et al.), DeepMesh (Zhao et al.), and MeshFlow (Sun et al.), recover face orientation in post-processing via Trimesh's
fix_normals(). However,fix_normals()only propagates orientation across adjacent faces and cannot resolve Möbius-like non-orientable loops that can form when stitching disconnected triangles.Motivated by your question, we extend EdgeMatch with a relative winding check during stitching without retraining. Because each shared manifold edge fixes the relative orientation of its two incident faces regardless of input triangle orientation, EdgeMatch rejects merges that would close non-orientable loops. We then apply
fix_normals()to unify face winding within each component. Adding ~0.5 s per mesh, this achieves 100% winding-consistent outputs on Toys4K while leaving geometric metrics virtually unchanged:fix_normalsfix_normals+ Winding Checkfix_normalsfix_normals+ Winding Check3. Application of EdgeMatch to Other Face-first Methods (Q3)
Since EdgeMatch operates solely on triangle soup without relying on upstream latents, it can serve directly as a standalone stitcher. Motivated by your suggestion, we applied our frozen EdgeMatch (without retraining or fine-tuning) to raw triangle soups generated by MeshFlow (Sun et al., 2026), comparing against MeshFlow's own post-processing: (1) Vertex Merging (merging quantized coincident vertices), and (2) Denoiser + Vertex Merging (refining coordinates with MeshFlow's pretrained vertex denoiser before vertex merging). Following MeshFlow's ShapeNet evaluation protocol across four categories (bench, chair, lamp, and table; 800 generated meshes), we report topology and distributional quality (1-NNA):
EdgeMatch eliminates non-manifold edges and vertices, substantially reduces open boundaries and disconnected components, and preserves generation quality (1-NNA)—whereas vertex merging, even with MeshFlow's denoiser, leaves the mesh largely disconnected and introduces non-manifold defects. This confirms EdgeMatch's effectiveness as a plug-and-play stitcher for external triangle-soup generators.