- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes Daedalus, a framework that generates a 3D object as separate mesh parts following a user-given part list. Given a reference image and a whole-object mesh, an agent first builds a bounding box for each part. SAM3.1 segments rendered views, a VLM checks the masks, and the accepted masks are mapped to mesh triangles to fit the boxes. A flow-matching generator then produces all parts jointly, and each part can use its own mix of conditions. A verifier finds problems, and the agent re-extracts, re-boxes, or resamples the affected part while other parts stay fixed.
Critical strengths
Letting the agent do choice while geometric tools compute the box coordinates is a reasonable design. It avoids directly asking a language model to guess 3D coordinates. Treating the part layout as something the system can revise, rather than a fixed user input, is an interesting view for part generation. The generator accepts different controls for different parts and supports both single instances and instance sets.
Critical weaknesses
-
The method takes a complete mesh as input and fits boxes from its triangles, so the task is close to directly segmenting the mesh and then completing each part. The paper does not compare with such a baseline. Furthermore, boxes also come only from visible triangles, so hidden or internal parts get no spatial guidance.
-
The verifier mainly checks whether each mesh is valid, such as whether it is empty, has holes, or breaks into fragments. These checks cannot tell whether a part has the right shape or meaning. The only signal tied to the user's intent is whether a part fits its box. But the box itself may be wrong. This makes it unclear how the system separates control errors from generation errors. Furthermore, the paper also gives no experiment on how the loop behaves in practice.
-
The large gains in Table 1 come from boxes. These boxes already reveal how the reference object is split into parts, and the image-only baselines receive no such input.
Questions for authors
-
How does Daedalus compare with HoloPart or X-Part given the same mesh and the same masks? How are hidden parts handled when they have no mask support?
-
What exactly are the predicted boxes in Table 2? How much does the VLM review add over raw SAM3.1 masks?