- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper presents FaceFlow, a two-stage diffusion framework for generating artist-like triangular meshes directly in face space. The authors identify the assignment ambiguity arising from variable face counts, permutation invariance, and non-uniform spatial distributions as a key challenge in face-based diffusion models.
To address this issue, the proposed Point Sink Flow first generates a sparse set of face centers from a dense point representation using a VAE and a flow-matching DiT. These predicted centers provide both the number and spatial locations of face tokens. In the second stage, Face Flow incorporates the predicted centers as spatial positional embeddings to guide face-latent generation. A Face VAE then decodes the generated latents into discrete vertex coordinates, enabling parallel mesh generation.
The method is trained on approximately 230K meshes containing fewer than 5K faces and evaluated primarily on 210 Toys4K samples. The reported results demonstrate improved geometric reconstruction and point-conditioned generation performance over several existing approaches, including autoregressive and diffusion-based mesh generation methods.
Critical strengths
Strength 1: Effective spatial guidance for parallel face generation
The paper identifies a meaningful challenge in face-based diffusion: establishing correspondences between noisy face latents and target faces when their spatial distributions are non-uniform. The proposed spatial guidance provides a practical solution. Table 3 shows that incorporating face-center positional information substantially improves performance over ZYX sorting, reducing CD-L1 from 11.80 to 7.73 and HD from 8.24 to 2.74 in the reported scaled units. This suggests that explicit spatial information is useful for learning face-latent distributions and represents a meaningful improvement over purely sorting-based alignment.
Strength 2: Strong geometric reconstruction and generation results
The proposed Face VAE achieves competitive reconstruction performance, outperforming the evaluated baselines in Table 1. The complete FaceFlow framework also achieves the best reported CD, HD, and NC scores among the compared methods on Toys4K. These results demonstrate the potential of face-level latent diffusion for generating geometrically accurate meshes without autoregressive token-by-token decoding.
Critical weaknesses
W1. Questionable architectural design and insufficient validation
The necessity of introducing face centers as an intermediate representation is not sufficiently justified. For typical triangular meshes, the number of faces is approximately twice the number of vertices, potentially making face-level diffusion less computationally efficient than vertex-based approaches such as Nexus.
Furthermore, Point Sink VAE uses a fixed set of 10,240 sampled points to represent a variable number of face centers, raising concerns about its scalability across different mesh densities. The paper also lacks direct evaluation of face-center prediction accuracy, including Precision, Recall, F1-score, and face-count errors for both the VAE and DiT.
Another fundamental concern is topological continuity. The Face VAE independently predicts vertex coordinates for each face without explicitly enforcing shared-vertex consistency. Even with discrete coordinate prediction, adjacent faces may fail to connect, resulting in cracks, disconnected components, or invalid topology. The authors acknowledge this limitation, but provide insufficient quantitative evaluation. Unlike connectivity-aware representations such as SpaceMesh or Nexus, the proposed decoder offers no explicit guarantee of consistent face connectivity.
W2. Limited scalability and insufficient topological consistency evaluation
The experiments are restricted to meshes with fewer than 5K faces, primarily evaluated on only 210 Toys4K samples. In contrast, Nexus has already demonstrated generation of meshes with up to 20K faces. The paper provides no convincing evidence that FaceFlow can scale to higher face counts, nor does it report inference time or memory consumption across different mesh complexities.
More importantly, the practical significance of the proposed framework remains unclear. Two compelling applications would be retopology of dense meshes containing hundreds of thousands or millions of faces (e.g., meshes generated by Tripo) and image-conditioned artist-like mesh generation. However, the current experiments demonstrate neither capability, relying instead on point clouds sampled from ground-truth meshes with normals. Without stronger scalability experiments or more realistic application scenarios, the advantages of this relatively complex architecture over existing approaches remain unclear.
Questions for authors
Q1. Necessity of Face-center Representation.
What are the advantages of face-center-based generation over vertex-based approaches such as Nexus? Given that triangular meshes typically contain approximately twice as many faces as vertices, could the authors provide a direct comparison under matched conditions to justify the computational efficiency and necessity of this representation?
Q2. Point Sink Flow Accuracy and Fixed-length Representation.
Could the authors report Precision, Recall, F1-score, and face-count prediction errors for the generated face centers, evaluating the Point Sink VAE and DiT separately? How does the fixed 10,240-point representation affect performance across meshes with substantially different face counts and densities?
Q3. Topological Consistency.
Since the Face VAE independently predicts vertex coordinates for each face, how does the model ensure connectivity between adjacent faces? Could the authors report quantitative metrics on cracks, disconnected components, and non-manifold edges, and clarify whether additional post-processing is required?
Q4. Scalability and Practical Applications.
Could the authors demonstrate generation on denser meshes (e.g., 10K–20K faces or more), including inference time and GPU memory consumption? Additionally, could they demonstrate dense-mesh retopology (e.g., from meshes generated by Tripo) or image-conditioned generation to establish the practical value beyond the current GT point-cloud setting?
Q5. LOD and Face-count Controllability.
Can FaceFlow generate different levels of detail for the same input geometry without retraining? Specifically, how does changing the initial noise latent sequence length affect the number and spatial distribution of predicted face centers? Can users explicitly control the target face count?
2 comments
Thank you for your response and for acknowledging our rebuttal. We hope that the following response addresses your remaining concerns.
First, regarding the newly added image-conditioned results, as emphasized in the manuscript, there is a gap in vertex and normal distributions between the conditioning inputs used during training and those generated by Tripo3D during inference. This gap is particularly pronounced in the lack of smoothness of the normals. Specifically, watertight meshes typically contain 500K–2M faces, and the normals of point clouds sampled from their surfaces exhibit more irregular orientations. Without targeted engineering optimizations, such as introducing normal perturbations during training to simulate the normal distributions of watertight meshes, inference quality deteriorates as the number of conditioning points increases. This is because sampling more points leads to a larger gap in normal distributions. These observations also indicate that deploying FaceFlow in practical applications requires additional time and corresponding engineering optimizations. The current experiment is used to indicate that FaceFlow will be able to support image-based generation and retopology with engineering efforts. We will incorporate these optimizations as part of our future open-source efforts to enable such applications. Nevertheless, we believe that these engineering challenges do not diminish the value of FaceFlow in enabling parallel inference for mesh sequences.
Second, regarding the scalability tests at 10K–20K faces, it is difficult to guarantee that the Point Sink Flow stage generates 10K–20K face centers. Therefore, we o. Meanwhile, Point Sink Flow uses a DiT with a fixed latent sequence length of 1,024 and has the same number of parameters as the Face Flow stage. Therefore, if the Face Flow stage can run with 20K faces, Point Sink Flow with a sequence length of 1,024 must also be able to run. We therefore manually construct a specified number of face centers and use 81,920 conditioning points to evaluate the Face Flow stage. To address this concern, we additionally test the inference time and peak memory consumption of the full pipeline on a mesh containing 40K faces.
| Input V | Input F | Condition Points | Generated Face Centers | Point Sink Time | Face Generation Time | Total Inference Time | Peak Memory |
|---|---|---|---|---|---|---|---|
| 56,924 | 39,962 | 81,920 | 9,076 | 27.23 s | 23.35 s | 50.58 s | 14.42 GiB |
Thank you for the detailed rebuttal and additional experiments. I appreciate the efforts to address my concerns.
However, my main concerns regarding scalability and practical significance remain unresolved. The newly added image-conditioned results involve only very simple shapes, and the quality appears to degrade with denser conditioning inputs. Moreover, the 10K–20K face scalability experiments only evaluate the Face Flow stage with predefined face centers, rather than demonstrating successful end-to-end generation of complex meshes.
The authors also acknowledge that explicit LOD and face-count control are not currently supported. Additionally, the updated topology statistics still reveal noticeable connectivity issues.
Overall, while the additional experiments are helpful, they do not sufficiently demonstrate the generalization and practical scalability of the proposed architecture.