- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper presents ADSL, a structured language and multi-agent workflow for generating editable 3D assets from text or images. Its main idea is to represent object parts and spatial relations explicitly, allowing the agents to generate and iteratively correct 3D programs. Experiments on text-to-shape and image-to-shape tasks show improvements over existing code-generation baselines, and ablations support the proposed spatial operators and refinement loop. The paper also demonstrates editing, articulation, memory reuse, and scene composition, although these capabilities are evaluated mainly through qualitative examples.
Critical strengths
The paper’s main strengths are its coherent system design and solid empirical performance.
- Joint agent–program design: The explicit DSL gives all agents a shared representation for planning, generation, verification, and repair, directly addressing the brittleness of low-level 3D code generation.
- Strong empirical results: The method consistently improves over code-generation baselines across several datasets, and the ablations show that both the spatial operators and iterative refinement contribute to these gains.
Critical weaknesses
The main weaknesses are the mismatch between the paper’s broad capability claims and its evaluation, and the limited isolation of the framework’s contribution.
- Insufficient structural and functional evaluation: Although the paper claims reliable support/contact relations, structural validity, mechanical function, editing, and scene composition, nearly all quality metrics are computed from rendered images. Execution success only measures whether a renderable mesh is produced. The paper provides no direct evaluation of collisions, physical stability, articulation, spatial-constraint satisfaction, or edit preservation.
- Base-model and baseline confounds: Most experiments rely on Gemini 3.1 Pro, while the cross-model analysis is small and qualitative. It is therefore unclear how much of the reported capability comes from the proposed framework rather than the underlying model.
Questions for authors
My questions are as follows: Clarification:
- Meaning of structural validity: The paper discusses support/contact, structural validity, mechanical function, functional correctness, and reducing floating or interpenetrating parts. Are these intended as geometric-placement claims or as claims of physical correctness?
- Physical verification: Beyond inspecting rendered views, does the system perform collision detection, stability analysis, physics simulation, or joint-motion validation? If not, please clarify the scope of the physical and functional claims.
- Scene-generation scope: Is scene generation a core capability of the method or only a qualitative downstream application? Figure 6 demonstrates scene composition, but the main evaluation focuses on object shapes.
- Editing mechanism: For a follow-up instruction such as adding a new object or part, does the Planner update its decomposition and constraints, or does the Coder directly rewrite the existing program? How are affected dependencies identified?
- Failure behavior: What are the most common semantic or structural failures, including cases where the system produces a renderable mesh that does not satisfy the prompt? How often does the system reach the ten-round refinement limit?
Evidence needed for current claims:
- Evaluation metrics: CLIP, VQAScore, FID, and the human study primarily evaluate rendered appearance, while execution success only checks whether a renderable mesh is produced. Can the authors provide direct measurements of spatial-relation accuracy, support/contact correctness, collision or interpenetration, articulation, and constraint satisfaction?
- Editing evaluation: Can the authors quantify whether an edit is correctly applied while preserving unaffected geometry and constraints? The current examples demonstrate parameter changes, but do not establish reliable insertion of new semantic objects or parts.
- Scene-level comparison: If scene generation is a substantive claim, how does the method compare with more recent work such as I-Scene or other agentic methods, particularly in spatial-relation accuracy, collision, stability, and scene completeness? If the tasks are considered incomparable, please explain the intended boundary of the claim.
- Backbone dependence: Since all main agents use Gemini 3.1 Pro and the GPT-6 Astra comparison is qualitative, how much of the performance comes from the proposed framework rather than the base model? Are results available using multiple backbones under matched inference budgets?