- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes FAMesh, an autoregressive framework for high-poly mesh generation that aims to reduce error accumulation and cross-part structural inconsistencies in conventional part-based generation.
Critical strengths
1.The paper is clearly written, with well-explained equations and notation. The method overview is also intuitive and easy to follow.
2.This paper addresses an important problem in high-poly autoregressive mesh generation: cross-part structural inconsistencies caused by the accumulation of errors from previously generated parts. I think this problem is meaningful, and the proposed approach is both well-motivated and reasonably novel.
Critical weaknesses
- Minor Issues with Presentation
Some symbols and text labels in Fig. 3 overlap, making the figure somewhat difficult to follow. I suggest revising the layout to improve readability. Since the proposed method targets high-poly mesh generation, the generated meshes contain a large number of faces, making it difficult to inspect their topology even when zooming in on the figures, particularly in Fig. 5. The teaser includes several close-up views of individual parts, which are helpful. However, the faces in some regions are still too dense to clearly distinguish their arrangement. The wireframe rendering also resembles a typical MeshLab visualization, which is not a clear way for rendering wireframes. In addition, the rendering quality and resolution appear to be inconsistent across different parts(e.g. the zoom-in images of the teaser), with some close-ups looking noticeably clearer than others. At present, the teaser is probably the only figure where I can reasonably assess the model's topology generation quality and the generated topology seems less regular than that of some previous autoregressive artist-mesh generation methods. I understand that this paper primarily focuses on scalable high-poly mesh generation rather than retopology. Therefore, I do not consider this a major weakness of the work. Nevertheless, clearer visualizations would make it easier to assess the actual quality of the generated meshes.
- See the Questions part.
Questions for authors
-
The data curation process establishes a fixed part ordering during training. However, it is unclear how Scafor identifies part boundaries within the flattened TopoScaf sequence during inference. Could the authors clarify how the model determines where one part ends and the next begins during inference?
-
Intuitively, PSAI introduces a trade-off between training&inference efficiency and generation quality/information preservation by compressing token features into structural summaries through gated aggregation. However, Table 3 shows that PSAI not only substantially reduces training time but also improves several geometric quality metrics. In TopoDec, PSAI mainly compresses the scaffold features of previous parts, while in ScafPAR, it compresses global TopoScaf features to reduce cross-attention costs. Both operations reduce access to fine-grained topological information and will cause accumulated error. I would therefore appreciate a more detailed explanation of why such compression can improve generation quality rather than merely preserve it. Is there any theoretical justification or empirical analysis that could help explain this behavior?
-
Why did the authors choose EdgeRunner as the mesh tokenizer? Based on the results in Fig. 5 and my experience with the open-source EdgeRunner code, it is not a good method for information preservation which suffers from many artifacts(e.g. missing faces), but I didn't see these issues in the results presented in this paper. Moreover, more recent tokenization methods(e.g.BPT and DeepMesh) have introduced block-wise and patch-wise compression strategies that achieve more compact mesh representations and their results are more stable after broad test in the 3D generation community. I hope authors discuss why these alternatives were not considered. If they can be adapted to the proposed framework, a comparison or ablation study using different tokenizers would help clarify whether EdgeRunner is particularly suitable for the proposed traversal-consistent generation framework.
-
In practical part-based mesh generation, it is often desirable to keep the contact regions between adjacent parts open, rather than generating unnecessary closing faces for each part independently. I could not find a discussion of this issue in the paper. So I hope author s can discuss more about it.
-
The paper reports using approximately 85K mesh assets for training. In my experience, this is a relatively modest dataset size for part-based mesh generation, particularly considering the quality of assets in Objaverse and the wide range of face number. However, the reported results are surprisingly not bad. I was particularly impressed by the last row of Fig.5, where the model appears to recover some Chinese character structures. Although the characters are not reproduced perfectly, the result is still interesting given the training data scale. I am wondering if the author do some extra practice e.g. data cleaning or data augmentation. I am truly interested in how the authors achieved this quality and apparent generalization with a relatively small number of mesh assets.
-
Do the authors plan to release the training code and the processed dataset?
4 comments
Q4: Why choose EdgeRunner over BPT or DeepMesh, and how does tokenizer choice affect the framework’s performance?
Compatibility with coarse–fine traversal alignment:
The QEM collapse history assigns fine faces to coarse-face regions, which are processed in coarse traversal order. EdgeRunner’s L/R adjacency transitions and BOM restarts let us enforce this order without changing its vocabulary or decoding rules.
BPT and DeepMesh form patches around central vertices, whereas SATO [3] constructs strips. These groups may cross coarse-face boundaries. Adapting them is possible in principle but would require region constraints and potentially splitting patches or strips. EdgeRunner thus provides a more direct implementation of our alignment mechanism.
Different tokenizers use distinct serialization grammars, so direct substitution would cause a training–inference mismatch. These ablations therefore require retraining the model with each tokenizer. We are willing to include these experiments in the camera-ready version.
Tokenizer comparisons:
To assess information preservation, we compare four tokenizers, with results shown below.
R1-Table 1. Tokenizer comparisons. All methods use the same GT inputs.
| Method | Mean token length | Mean decoded faces | HD ↓ | ↓ | F1 ↑ | ECD ↓ | EF1 ↑ |
|---|---|---|---|---|---|---|---|
| DeepMesh | 88,708.470 | 33,399.470 | 0.013 | 0.005 | 0.659 | 0.001 | 0.636 |
| BPT | 32,104.170 | 15,931.730 | 0.017 | 0.007 | 0.472 | 0.002 | 0.468 |
| SATO | 196,308.800 | 58,836.270 | 0.011 | 0.006 | 0.662 | 0.001 | 0.637 |
| EdgeRunner | 220,389.730 | 52,219.430 | 0.014 | 0.004 | 0.661 | 0.001 | 0.633 |
EdgeRunner achieves geometric fidelity comparable to DeepMesh and SATO and better than BPT in this evaluation. The newly added Fig. 11 in Appendix further shows that EdgeRunner, DeepMesh, and SATO preserve overall shape but exhibit local degradation in fine structures, such as facial details. This degradation is not unique to EdgeRunner and is consistent with a shared limitation of coordinate quantization: nearby vertices can map to the same position, collapsing short edges and creating degenerate triangles. SATO’s official implementation also acknowledges this limitation. Together, these results and its compatibility with our alignment mechanism support our choice of EdgeRunner.
Q5: Why are contact regions between adjacent parts closed rather than left open?
We thank the reviewer for raising this point. Whether contact regions should remain open depends on the part definition and downstream use. In line with the independent part modeling approach of BANG[4], FAMesh represents each part sequence as an independent watertight mesh, intentionally retaining closed contact surfaces. This allows topological closure within each part during autoregressive generation, without requiring boundary stitching between parts. Geometric coordination between parts is guided by the contours, layout, and contact relationships provided by TopoScaf. Meanwhile, complete surfaces also support independent use, repositioning, and reassembly, reducing the need to close and repair exposed boundaries when assembly relationships change. We have added this discussion to Section 3.1.
Q6: How does FAMesh achieve good quality and generalization with 85K assets, and were data cleaning or augmentation used?
We thank the reviewer for highlighting the missing training details.
Pretraining and data preparation:
Both TopoDec and ScafPAR are initialized from the EdgeRunner checkpoint, retaining its base architecture and serialization while incorporating our proposed modules. We use Objaverse-XL assets filtered by TRELLIS [5,6], with random rotations, point-cloud noise, image degradation, and topology-preserving scaffold perturbations.
The fine-mesh training set was subsequently expanded to 120K assets. TopoDec uses 200K assets simplified to approximately 4.5K-face scaffolds. The shorter sequences reduce training costs, allowing a larger dataset to broaden structural coverage and improve scaffold stability. For context, the base models of TreeMeshGPT [7], and FACE[2] also use training datasets of comparable scale. We have added the relevant details to Section 4.1.
Scaffold guidance reduces the burden of topology inference:
TopoDec establishes a compact global structure, and ScafPAR refines individual parts, limiting each prediction to the current part’s sequence. Aligning coarse and fine traversals provides explicit topological trajectories and cross-part structural cues, reducing the need to infer topology from surface geometry alone. The marked degradation without traversal consistency (Table 4) supports this design. This also helps explain the “武” example in Fig. 5: the scaffold provides the main stroke layout and structural cues, helping ScafPAR reconstruct geometric details more reliably.
Q7: Do the authors plan to release the training code and the processed dataset?
We thank the reviewer for their interest in our work. It would be our pleasure to make our training code, processed dataset, and preprocessing scripts publicly available upon acceptance to support further research.
[1] Scaling Artist Mesh Generation via Local-to-Global Assembly.
[2] FACE: A Face-based Autoregressive Representation for High-Fidelity and Efficient Mesh Generation
[3] Strips as Tokens: Artist Mesh Generation with Native UV Segmentation
[4] BANG: Dividing 3D Assets via Generative Exploded Dynamics
[5] Structured 3D Latents for Scalable and Versatile 3D Generation
[6] Native and Compact Structured Latents for 3D Generation
[7] TreeMeshGPT: Artistic Mesh Generation with Autoregressive Tree Sequencing
Dear Reviewer,
I hope this message finds you well. As the discussion period is nearing its end, I wanted to ensure we have addressed all your concerns satisfactorily. If there are any additional points or feedback you'd like us to consider, please let us know. Your insights are invaluable to us, and we’re eager to address any remaining issues to improve our work.
Thank you for your time and effort in reviewing our paper!
We sincerely thank the reviewer for the detailed and constructive feedback. We appreciate your recognition of the paper’s clarity and of the importance, motivation, and novelty of addressing error accumulation and cross-part structural inconsistencies in high-poly mesh generation.
We believe our response has addressed most of your concerns and we respectfully ask if you're comfortable to re-consider the rating in light of our efforts and dedication. Below, we provide detailed responses to all the comments:
Q1: Overlapping labels and unclear, inconsistent wireframe renderings hinder readability and assessment of topology quality.
Thank you for the feedback. We revised Fig. 3 to resolve overlapping labels and re-rendered all visualizations using a unified pipeline to improve wireframe clarity and image consistency.
We identified meshes with poor topology before receiving the reviews. While awaiting the reviews, we refined the data filtering, expanded the training set to 120K meshes, and completed retraining. We updated Figs. 1, 5 and Tables 1–2 accordingly, with additional examples in Appendix Fig. 9.
Q2: How Scafor identifies part boundaries within the flattened TopoScaf sequence during inference
During training, we append EOS to each TopoScaf part subsequence and an additional EOS to the full sequence. At inference, TopoDec predicts these markers autoregressively: EOS ends the current part, a subsequent traversal-start token (ID 5) begins the next part, while a second consecutive EOS terminates the sequence.
Q3: Why does PSAI’s compression improve generation quality, and what theoretical or empirical evidence supports this?
We attribute the gains in Table 3 to task-aligned interaction granularity: fine-grained modeling within parts and structural summaries across parts. This lowers interaction costs and may reduce interference from redundant details and local prediction errors.
For TopoDec, parts are watertight connected components with independent vertex indices, assembled directly after generation. Fine-grained topology modeling therefore primarily serves connectivity within parts, while cross-part conditioning only needs to coordinate relative placement and geometric contact without requiring shared vertices. MeshMosaic [1] likewise weakening the influence of cross-part information, providing a rationale for concentrating fine-grained modeling only within parts.
For ScafPAR, each face comprises multiple tokens. Aggregating local tokens in topology traversal order can thus be viewed as forming face- or patch-level representations that providing explicit cues about position, surface shape, and orientation. Moreover, Hscafn compliments additional topology information for the current part. FACE [2] offers related theoretical support: it encodes each face’s coordinates into a single token, shortening sequences while achieving high-quality reconstruction.
Aggregation versus scaffold resolution. Aggregation learns representations from an existing scaffold, reducing its resolution may remove essential geometric cues. The degradation in Table 7 underscores the need for sufficient scaffold resolution.
Notably, although one token error can damage multiple associated faces, the mild local scaffold corruption in Fig. 10 (second row) does not reappear after refinement. This observation is consistent with aggregation improving tolerance to local token errors.