- Rating
- 2
- Confidence
- 4(+1)
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper introduces FuncRoom-Agent, which is used for generating 3D indoor scenes based on functional requirements. The method builds the scene hierarchically through recursive DSL and uses the construction trajectory generated by the agent for visual-context SFT. Then, it further optimizes through ScenePRM-guided RL. The inference stage adopts sequential feed-forward construction and no longer performs explicit test-time critique-and-repair. The experiments are conducted on SceneEval and the author's proposed Function-Room benchmark.
Critical strengths
- The generation of indoor scenes has been further expanded from visual rationality to functional completeness and usability, and the problem setting has certain practical significance.
- Recursive DSL can naturally represent the hierarchical structure among furniture, support relationships, wall objects, and nested small objects.
Critical weaknesses
- Hierarchical scene representation, DSL/code-based scene generation, execution feedback, and agent refinement have all been extensively explored in recent works (Sage, SceneWeaver, scenethesis, scenesmith). It is hoped to clarify the novelty of this paper.
- There is currently no clear ablation study conducted for different input modalities.
Questions for authors
- Are the Function-Room automatic evaluation indicators stable under different VLM evaluators? And what is the correlation between them and human ratings?
- It is not clear whether different methods use the same asset library, retrieval/generation backend, rendering setup and external models.
- It is claimed that this method has achieved an improvement in efficiency, as it avoids the iterative repair during test time. However, the complete process still takes approximately 25 minutes per scene, while the closest alternative, Code as Room, takes 33 minutes.
- The scale of the Function-Room benchmark is relatively small, with only 50 test sets.
- Function-Room metrics relies on VLM for its judgment, and ScenePRM itself also depends on GPT-based critic. There is a lack of sensitivity analysis under different VLM evaluators, as well as a correlation analysis between automatic metrics and human judgment.
Response to Reviewer z665: DSL Novelty, Input Ablations, Evaluation, and Runtime
Thank you for the constructive review. We address the critical weaknesses (W) and the questions (Q) below.
W1. Novelty of the Our DSL
Representation. Our contribution is not recursion alone: our DSL yields execution-grounded training traces. Each fragment builds one functional group from committed parents and can be executed and committed on its own. Each step records the pre-action state and render, the action, and the grounded result. Recursion defines stages for sampling K candidates from the same state.
Training. We use these traces for SFT on state–action pairs and stage-level RL with ScenePRM rewards. SAGE, SceneWeaver, Scenethesis, and SceneSmith prompt general-purpose models for scene generation.
Inference. Conditioned on the current scene state and render, our trained generator completed all 50 tasks with one candidate per step and no iterative critique or repair. SAGE, SceneWeaver, and SceneSmith use iterative feedback, and Scenethesis can replan after judging spatial coherence.
Table 3 in the main paper shows that our recursive agentic construction performs better than both one-shot construction with a flat DSL and staged construction on Function-Room.
W2. Input modality ablation
The ablations show that renders, scene state, and history each contribute to the full model’s performance. Removing renders only during RL yields 78.7 / 82.2 / 63.5 (FZC / FOC / FOP).
Q1/Q5. Evaluator robustness and human agreement
ScenePRM uses GPT-5.2. With evaluation inputs and prompts fixed, all three test VLMs gave the same method rankings for each metric.
Fifteen participants independently assessed FZC, FOC, and FOP items. We computed item-level agreement and Cohen’s κ between GPT-5.5 and each participant, then averaged across participants. For each method, we computed Spearman’s ρ between GPT-5.5 and human-derived scores across 50 scenes, then pooled the six correlations using Fisher’s z transformation.
Q2. Baseline settings
Methods shared functional requirements, local hardware, final Blender settings, and five-view evaluation. Asset backends varied.
Q3. Runtime
Excluding asset generation and retrieval, runtime drops from 23 minutes to 10 minutes, a reduction of 56.5%. Online evaluation and repair account for the 13-minute gap. FuncRoom-Agent spends 5 min more on assets and saves 24.2% end to end.
Q4. Benchmark size
We compare six methods on the same 50 human-reviewed prompts. Prior work reports 22 scenes (SceneThesis), 30 prompts (SceneCode). We also evaluate 30 SceneEval prompts and 531 held-out 3D-FRONT scenes.