- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
The paper presents CADPalette, which uses the material latent of a pretrained 3D generative model to predict both geometric primitive types and surface-instance partitions for CAD meshes. Primitive types are encoded as fixed bits and instances as random colors. A fine-tuned material flow produces the joint representation, and color screening together with latent relation supervision reduces confusion between adjacent instances. The authors run comparisons and ablations on a CAD dataset they constructed, and show qualitative results on scan-reconstructed meshes.
Critical strengths
On the reported CAD validation set, the method is clearly better than the selected baselines at both geometric primitive-type recognition and instance segmentation. The comparisons and ablations support its effectiveness under the reported validation setup, including the added color screening and latent relation constraint.
Critical weaknesses
-
The core idea is to encode instance labels as colors and then predict the segmentation with a generative model. PartGen [1] and NaTex [2] are existing precedents. The technical route is also very close to SegviGen [3], including the reuse of TRELLIS.2, a frozen material codec, random-color instance encoding, and conditional flow prediction. The additions are mainly primitive-type encoding, color screening, and a local relation constraint. I see these changes as engineering adaptations for the CAD task, and not as a substantial methodological contribution.
In Figure 2, the pipeline is packed too tightly and the font is too small. At a normal reading scale, the flow and the key modules are hard to make out. This is the main method figure, and it should not have this basic problem. Parts of the main text are also obscure and take repeated reading to follow.
-
The paper emphasizes that the structured latent reduces dependence on how the input is discretized. The main evaluation uses only uniformly remeshed inputs, with no quantitative comparison across tessellations, mesh densities, or scan noise. The scan study shows only six qualitative examples, without metrics or baselines. The mechanism ablations use only a small training setup, which is not enough to show what the added designs contribute under full training.
[1] Minghao Chen et al. PartGen: Part-level 3D Generation and Reconstruction with Multi-view Diffusion Models. CVPR, 2025. Paper.
[2] Zeqiang Lai et al. NaTex: Seamless Texture Generation as Latent Color Diffusion. arXiv:2511.16317, 2025. Paper.
[3] Lin Li et al. SegviGen: Repurposing 3D Generative Model for Part Segmentation. arXiv:2603.16869, 2026. Paper.
Questions for authors
-
The reported ablation uses only 9k samples and 10k steps, while the main experiment uses 273k samples, roughly a 30-fold difference in sample count. Primitive-type encoding, color screening, and the local relation constraint are the main additions relative to the existing route, so gains at this smaller scale do not show that they still help in the main experiment. The paper does not report the number of steps, hardware, or runtime of the full training, and I cannot tell whether an ablation closer to the main setting is infeasible. Please provide this information. If full training is indeed too expensive, please at least compare these designs against the version without them in a setting closer to the main experiment. Otherwise, it is hard to attribute the lead in the main table to these designs.
-
The paper treats stability across discretizations as a main motivation, but the main table compares only uniformly remeshed inputs, and the scans are six qualitative examples. I therefore cannot treat “the result remains stable under a different mesh” as an established finding. Please report primitive-type recognition and instance-segmentation scores for the same CAD models under different tessellations, mesh densities, and scan noise, together with baseline comparisons. If these scores are clearly lower than those in the main table, this claim cannot count as a verified contribution.