- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
The paper proposes a 3D OBB layout conditioned part-level shape generation work. It takes in a set of OBB and a global text prompt as input and generates segmented shape as a occ field. The paper uses a global-local transformer to inject the part-level information to the global shape generation branch. experimentally it also shows shape editing applications that allows the user to edit the generated object by changing its layout input and text prompt.
Critical strengths
The paper's result looks promising and it shows many qualitative result backing up its superior metrics compared to the baselines. The editing applications looks very cool and versatile.
Critical weaknesses
The main concern I have is novelty. The main architectural contribution, i.e., local-global latent processing mechanism feels like a direct application of the contribution proposed by the previous PartCrafter paper. Meanwhile, the introduction calls the alternating local/global architecture a “key insight” enabling their method (ln 77-79). At least a acknowledgement of similarity is needed in the main paper. Also given the architectual similarity, the authors should clarify what has made their method work better than PartCrafter. Is the reason that PartCrafter does poorly in comparison solely due to the use of an image generator? A fair comparison is needed to justify the improvement.
Additionally, in the first technical contribution it says "We present the first method to synthesize part-separated 3D shapes directly from coarse part layouts, featuring a novel conditioning technique that ensures strong adherence to the user’s input layout, and a high degree of control over individual object parts."
This is a sigificant overclaim. For example, CoPart, which the paper cites, already takes in 3D bounding boxes as input conditioning for shape generation. Older works such as SALAD, Difffacto, SPAGHETTI all has explicit part-level shape conditioning as part of their pipeline. So it would be a fairly straightforward extension of their methods for enabling OBB as input conditioning. Given these, it makes me question whether the authors have carefully considered the positioning of their paper among the previous works.
Questions for authors
See weakness
12 comments
3. Why does PartCrafter perform poorly at the layout-to-parts generation task? (W2)
We first want to establish that our comparison with PartCrafter is fair:
- It receives the same layouts and text prompts as our method. Since it only accepts images, each layout is rendered from a canonical viewpoint and turned into an image that follows the layout and the prompt.
- Since PartCrafter allows it, we also supply the ground-truth number of parts in the layout.
- This image is produced by Nano Banana Pro, a proprietary model that was, to our knowledge, the strongest available for this task at the time of submission.
- It is not penalized for generating a different number of parts: it is given the ground-truth number of parts at inference time. The layout provides one bounding box per part, so it generates exactly as many parts as the ground truth.
- It is not penalized for a global misalignment: each output is scored under 25 canonical orientations, and we keep the best one.
- In the GPT-4o study, each comparison is run in both A/B orders, and the judge is told to treat boxes as loose bounding volumes rather than shapes to fill.
Our main point is that PartCrafter is not designed for structure-to-3D generation, so the image generator is only part of the explanation for its results:
- PartCrafter only sees the layout through an image, which Nano Banana cannot generate reliably and which loses occluded parts and depth.
- Layout control comes from how boxes are encoded, not from the local/global architecture: within our architecture, an MLP on box parameters reaches a Part-IoU of 0.289, against 0.729 with our encoding (Table 5).
- PartCrafter's outputs suffer from artifacts, which degrade both visual quality and layout following. This is a known failure mode, reported by subsequent part-generation papers comparing to PartCrafter (e.g., "fragmented parts" in FullPart, and parts with "ambiguous boundary" in X-Part).
4. Positioning with respect to CoPart, SALAD, DiffFacto and SPAGHETTI (W3)
We thank the reviewer for raising this point, which gives us the opportunity to clarify how CompoSE relates to these works.
SALAD, DiffFacto and SPAGHETTI. The reviewer quotes our main claim: "We present the first method to synthesize part-separated 3D shapes directly from coarse part layouts." However, these methods do not synthesize part-separated 3D shapes: SPAGHETTI and SALAD decode a single implicit field for the whole shape, and DiffFacto outputs labelled point clouds.
CoPart. CoPart does claim to take 3D boxes and text prompts as input. However, it is still unclear to us how well it follows an input layout:
- It reports no IoU, at the object or part level, and no other measure of adherence to the input boxes. Its quantitative evaluation (their Table 1) only reports text-alignment scores (CLIP and ULIP), alongside a user preference study (their Table 2).
- This only quantitative evaluation follows the text/image-to-3D protocol of CLAY, and the paper does not state whether boxes were provided, or where they came from.
- No part-based method is compared quantitatively, and no evaluation on a test set of input layouts is reported.
- Its figures do not show input layouts and prompts alongside the generated outputs on a test set.
- Part editing is very limited: it is shown on a single object (their Fig. 5a, a two-part hammer), where the head is edited twice through its text prompt (one texture edit and one geometry edit). No part addition, removal or resizing is shown, and no input boxes are displayed.
- Its code and weights are not released (the repository has announced "Code is coming soon" since July 2025), which prevents any comparison.
In contrast, we evaluate layout adherence quantitatively against the input boxes (Part-IoU, Object-IoU, Voxel-IoU) on a held-out test set, compare against both proxy-guided and part-based methods, and evaluate the preservation of untouched parts after editing.
Revised claims. Nevertheless, to avoid any potential overclaim, we have revised our main claim in the manuscript as follows:
| Before | After |
|---|---|
| "We present the first method to synthesize part-separated 3D shapes directly from coarse part layouts…" | "We present the first method to synthesize part-separated 3D shapes from a global text prompt and a layout of coarse oriented boxes…" |
Summary of revisions
All changes made in response to this review are highlighted in purple in the revised manuscript. Changes also requested by the other reviewers are highlighted in yellow instead.
- Explicit attribution of alternating local/global blocks to prior work (VGGT, MVGGT, HoloPart, PartCrafter, X-Part) (Section 1 above).
- A component-level comparison with PartCrafter (Section 2 above).
- Revised claims in the introduction and conclusion (Section 4 above).
We thank the reviewer again for the thoughtful comments, which have clearly improved the paper. We hope these additions address the reviewer's concerns, and we would be grateful if the reviewer would consider raising their score. We would be happy to clarify any remaining questions.
We sincerely thank the reviewer for the careful review. We are glad that the reviewer found our results "promising", supported by "many qualitative result[s] backing up [our] superior metrics compared to the baselines", and our editing applications "very cool and versatile". We address each concern below. All new experiments and clarifications have been included in our revised manuscript.
1. Attribution of the general local/global design in DiTs (W1)
We agree that alternating local and global blocks is common in 3D, both in reconstruction (VGGT, MVGGT) and in part generation and decomposition (to our knowledge first in HoloPart, then in PartCrafter, X-Part and many other works). We would like to clarify that this alternation itself is not listed among our contributions (Sec. 1), which cover layout-conditioned synthesis of part-separated shapes, compositional editing, and our data pipeline.
What the "key insight" sentence in the introduction (Sec. 1) describes is how we adapt this alternation for layout-conditioned generation: local stages bind each part to its own box, while global stages, conditioned on the enclosing box, keep the parts mutually consistent. To remove any ambiguity, we have revised this sentence and now explicitly attribute the local/global design to prior work in Sec. 3 of our revised manuscript.
2. What mainly differentiates CompoSE from PartCrafter (W2)
We thank the reviewer for this question. Just like PartCrafter, we also build from the TripoSG backbone. However, while PartCrafter is focused on image-to-3D part decomposition, i.e., recovering the parts of the object shown in an input image, CompoSE is designed for part-conditioned generation and editing, where the user directly specifies the parts through a text prompt and a 3D layout. This leads to substantially different additions to the backbone.
From TripoSG, PartCrafter:
In our case, from TripoSG, we:
In common with PartCrafter, we:
We have updated the appendix of our revised manuscript (Appendix H.5) with this breakdown clarifying our contribution.