- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces MeshRepair, a prefix-LM for repairing generated mesh topology through autoregressive face deletion and addition. It bidirectionally encodes the draft, uses pointer heads to select faces and vertices, and generates new vertices when needed while preserving unedited connectivity. Experiments on scripted defects and generated drafts show improved face F1 and fewer non-manifold edges, with gains primarily driven by deletion.
Critical strengths
- Practical relevance and appropriate problem formulation. Repairing generated meshes through sparse face edits addresses a meaningful problem while preserving satisfactory regions that full regeneration could alter. The explicit edit sequence also makes the modifications inspectable.
- Well-motivated model design. Bidirectional prefix attention provides full draft context, while autoregressive decoding captures dependencies between edits. The specialized pointer heads appropriately distinguish face deletion from vertex-based face addition, and the ablation results support their advantage over coordinate-based prediction.
Critical weaknesses
- Limited realism: Evaluation drafts use ground-truth vertices and generators seen in training. Vertex errors in practical outputs may lead to incorrect edits. Tests with perturbed vertices and unseen generators are needed.
- Weak face addition: Gains appear largely driven by deletion; addition recall is only 0.093 on MeshCarve and 0.024 on LATO2. Boundary edges also increase on LATO2, suggesting incomplete restoration of missing connectivity. These results support the method as an effective cleanup stage more strongly than as a complete topology-repair solution.
Questions for authors
- Robustness to vertex errors. How does repair performance change when draft vertices are displaced or missing? Can you report results under controlled perturbations and clarify how often the NEW mechanism recovers missing vertices?
- Generalization across generators. Since both evaluated generators are represented in training, have you tested MeshRepair on drafts from an unseen generator? If not, what aspects of the method do you expect to transfer?
- Contribution of face addition. Using the same trained model, how do the final face F1 and boundary-edge statistics compare between deletion-only output and the full deletion-plus-addition output? This would clarify the net benefit of the addition phase.
- Performance across topologies. Can you stratify results by mesh complexity and, where well-defined, genus and number of boundary components?
5 comments
Dear Reviewer,
Thank you again for your detailed review. As the discussion period closes on Nov. 18, we would greatly appreciate it if you could take a look at our response and the revised PDF. If our response addresses your concerns, we would be grateful if you could consider updating your rating. We are happy to clarify any remaining questions before the deadline.
I thank the authors for the additional experiments, particularly the deletion-only comparison. However, the presented examples appear to focus on relatively simple, local defects, whereas missing connections across large planar regions are, in my experience, a major challenge in AI-generated meshes. Without evidence on such cases, I remain uncertain about the method’s practical utility and maintain my Weak Rejection.
We thank the reviewer for the detailed questions.
W1 / Q1 / Q2. Vertex errors and unseen generators. For perturbed vertices, we displace 5% of the vertices at random by 1 to 5 voxels. MeshRepair raises face F1 from .827 to .843 on MeshCarve and from .281 to .325 on LATO2, and reduces the non-manifold edges per draft from 183.7 to 15.2 and from 406.2 to 20.2 (Section 4.4 of the revised PDF). For missing vertices, we punch holes into the MeshCarve drafts: connected face patches covering 5% of the faces are removed, and vertices whose faces are all removed leave the draft. MeshRepair recovers 50% of the missing vertices within one voxel on the MeshCarve drafts and 57% on the scripted-defect drafts. Around the holes that lost vertices, MeshRepair closes 60% of the open edges on the MeshCarve drafts and 68% on the scripted-defect drafts (Section 4.4 of the revised PDF). At the same time, it avoids closing intended openings that can only be semantically determined: on the drafts of Table 1, its output covers 11.4% of the boundary edges of the reference (the openings the artist made) for MeshCarve and 0.6% for the scripted defects, fewer than the draft itself and than every hole-filling tool (trimesh, Blender, PyMeshLab). The details are in Table 4 of the revised PDF. For unseen generators, we evaluate MeshRepair qualitatively on meshes from Tripo and Meshy, i.e., commercial models, which generate their own vertex positions from an image. We include the visual samples in the revised PDF (Appendix D). Overall, MeshRepair repairs the topology of these meshes: it repairs overlapping faces and removes redundant faces, i.e., the repair ability is transferable.
W2 / Q3. Addition and boundary edges. The addition phase gives a net benefit: for the same model, the full deletion-plus-addition output has higher face F1 and fewer boundary edges than the deletion-only output on both generators (Table R1). Regarding the addition recall, the edit metric of Table 1 requires an exact triangle match: when an artist quad is split along the other diagonal, the surface is the same, but the addition is counted as wrong. Scored consistently with the face-set and edge columns (Table 5 in the revised PDF), the addition recall of MeshRepair is .299 on MeshCarve and .138 on LATO2. In addition, we believe that the addition recall itself is a limited measure of the additions, and we regard it as a reference only. In the hole-punching experiment above (W1 / Q1 / Q2), MeshRepair closes most of the open edges around the holes that lost vertices, and a closure that uses triangles other than the artist's can be equally valid, but under the exact match the addition recall does not count it.
Table R1. Same model, Table 1 drafts. Face F1 and boundary edges as a share of all edges.
Q4. Stratified results. We stratify the Table 1 drafts by the reference mesh. MeshRepair has the highest face F1 gain in every stratum on all three sets (Table R2).
Table R2. Face F1 gain over the draft, ours / best repair tool (MeshFix excluded, as in Table 1). Genus is computed on the edge-manifold references.