- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper presents Lived-In by Design, a framework for text-conditioned 3D indoor scene generation that carries inferred everyday activities through scene specification, local assembly, and room-level layout. A behavior-to-asset stage converts plausible activities into object requirements and functional relations. Related objects are assembled into functional groups with behavior-dependent orientations and approximate human-use regions. A group-level search then places these assemblies while considering physical constraints, architectural relations, and access, with constrained local revision when necessary. The system builds on SceneSmith for room construction, asset acquisition, rendering, and physical post-processing. On 179 room-level prompts, the method reports higher attribute and object–object relation scores than the compared baselines, while trailing SceneSmith on count satisfaction, object–architecture relations, and collisions. A blinded five-way study with 25 participants on five selected scenes reports 82.4% preference for lived-in plausibility. The appendix also reports two component removals, although these lack a full-method control evaluated on the same subset.
Critical strengths
-
A coherent representation connecting activities, local organization, and room layout. The method addresses a relevant gap between placing plausible objects and arranging them for use. Its activity-derived requirements, persistent functional groups, support bindings, and required/preferred use regions form a concrete construction pipeline (Sections 3.2–3.4). Preserving local organization while allowing constrained revision is a sensible way to reconcile functional arrangements with room geometry.
-
Promising evidence for improved semantic organization and perceived plausibility. The 179-prompt comparison includes a strong underlying baseline, SceneSmith. ATR increases from 74.4 to 88.9 and OOR from 67.6 to 75.2, despite a lower average object count. The blinded human study also shows a substantial preference for the proposed method on all five evaluated scenes. These are meaningful positive results, even though they do not establish improvements across every dimension or across the full prompt distribution.
Critical weaknesses
-
The experiments do not isolate the contribution of the central mechanisms. Appendix A.6/Table 3 compares two component removals on an unspecified subset with full-method results from all 179 prompts; the caption explicitly states that this is not a matched-subset control. Consequently, the reported OOR gap cannot be interpreted as a component effect. Neither behavior-to-asset grounding nor functional-group assembly is independently removed. Since the system builds on SceneSmith and related work already studies functional groups and human-aware constraints, controlled evidence for the particular integration is important. Missing model configurations and search budgets further limit attribution of the gains to the proposed design rather than execution differences.
-
Evidence for broadly improved functional usability remains indirect and narrowly sampled. Table 1 reports semantic and general spatial metrics, but no object-accessibility score or aggregate validation of the proposed use-space/access diagnostics. NAV alone does not establish that the intended interaction sides are usable. Relative to SceneSmith, CNT drops from 82.9 to 66.8, OAR from 80.6 to 72.9, and COL rises from 1.2 to 7.0; these trade-offs matter for the intended application. The human study is positive and statistically analyzed, but covers only five selected scenes with an unspecified selection rule. Its participant-level intervals do not quantify generalization to new scenes, and common rendering settings across methods are not established. Thus, the current evidence supports perceived improvement on the selected examples more clearly than a general improvement in functional usability.
Questions for authors
1.How many prompts are in the ablation subset, which prompts were selected, and how does the full method perform on the same subset? Can you separately evaluate the contributions of behavior-to-asset grounding and functional-group assembly while keeping the backbone, asset-acquisition configuration, and computational budgets fixed?
2.Beyond NAV, what evidence shows that objects are easier to approach and use? Could you evaluate the existing scenes with SceneEval ACC or independently check whether the intended use regions are obstructed or inaccessible? Why does COL increase while CNT and OAR decrease relative to SceneSmith, and do the additional collisions mainly involve interactive furniture or small supported objects?
3.How were the five human-study scenes selected from the 179 prompts, and were they the same outputs used in the automated evaluation? Were rendering and scene-selection conditions comparable across methods, including the renderer, lighting, and resolution? Given the lower CNT and OAR scores in Table 1, what supports extending the strong human preference for prompt faithfulness beyond these five scenes?
4.Which reasoning and vision models and versions were used, and what were the prompt configurations and search/refinement budgets? How many scenes contributed to each metric, and how were generation or evaluation failures handled? Were baseline outputs regenerated or reused, and were all outputs assessed with the same evaluator version and configuration?
11 comments
W1. The experiments do not isolate the contributions of the core mechanisms. Differences in models and budgets also affect attribution.
We agree that the core components should be assessed in controlled experiments with clearly specified models and budgets.
We compared four configurations on the same 30 scenes. We separately removed behavior planning (NoBehavior) and functional-group assembly (NoGroupAssembly). Full scored 16.83 percentage points higher than NoBehavior on OAR. It scored 2.42 points higher on STB and 6.91 points higher on OPEN than NoGroupAssembly. These results are consistent with the respective roles of behavior planning in spatial organization and group assembly in preserving within-group structure.
Q1 gives the full results and sampling rules. Q4 gives the models and budgets. Table 3 in the revision will present these matched-prompt comparisons. The visualizations show how each component contributes to the resulting layouts.
W2. Evidence of functional usability is indirect, and a five-scene user study provides limited support for broad generalization.
We agree that functional usability and generalization across scenes require more direct evidence.
To assess local conditions for use directly, we added ACC and OPEN. Full scored 5.13 percentage points higher than NoHumanUse on ACC and 24.63 points higher on OPEN, as shown in Q2. These results support improved object accessibility and greater clearance at architectural openings.
We selected 20 additional scenes for the extended user study. Q3 gives the selection rules and rendering settings. The revision will report preference rates and confidence intervals that account for variation across scenes. Q2 also explains the trade-offs in CNT, OAR, and COL in the original table.
Q1. How many prompts were used for the ablations, and how were they selected? Can the core components be compared independently using the same models, assets, and budgets?
Thank you for this suggestion.
We compared Full and three ablations on the same 30 prompts. NoBehavior removes activity-derived planning. NoGroupAssembly removes local assembly followed by placement of each group as a unit. NoHumanUse removes feedback on human-use space.
We drew a stratified sample from SceneSmith's 179 room-level prompts using the difficulty levels and source categories in the original list. The random seed was 20261107. We selected 10 prompts at each of the three difficulty levels, covering 19 room types. The supplementary material gives the full prompt list, sampling quotas, and adjustments.
All four configurations use gpt-5.6-sol for both language and vision, Qwen-Image-2.1-Turbo to generate reference images, and SAM3D to generate 3D assets. The base budget for whole-room review is 3 rounds for Full and 5 for each ablation. The extra rounds allow the ablations to complete layout repair and export the scene after a component is removed.
The table summarizes the current results. All scores are percentages.
| Method | CNT↑ | ATR↑ | OOR↑ | OAR↑ | ACC↑ | NAV↑ | STB↑ | COL↓ | SUP↑ | OOB↓ | OPEN↑ |
|---|---|---|---|---|---|---|---|---|---|---|---|
| NoBehavior | 85.35 | 8̲1̲.̲7̲0̲ | 79.33 | 72.70 | 81.51 | 94.50 | 92.29 | 10.57 | 9̲0̲.̲5̲9̲ | 0.52 | 76.64 |
| NoGroupAssembly | 8̲8̲.̲8̲4̲ | 83.68 | 8̲2̲.̲6̲2̲ | 85.83 | 79.16 | 9̲4̲.̲9̲3̲ | 9̲6̲.̲5̲3̲ | 5.87 | 89.03 | 0.46 | 8̲6̲.̲7̲1̲ |
| NoHumanUse | 88.48 | 78.81 | 85.32 | 8̲7̲.̲9̲4̲ | 74.77 | 95.95 | 91.17 | 5̲.̲8̲3̲ | 84.86 | 0̲.̲4̲3̲ | 68.99 |
| Full | 89.52 | 81.39 | 78.95 | 89.52 | 7̲9̲.̲9̲0̲ | 94.13 | 98.96 | 5.44 | 91.34 | 0.28 | 93.62 |
Behavior planning translates activity requirements into object choices and layout constraints. Full scores 16.83 percentage points higher than NoBehavior on OAR, supporting the role of behavior planning in guiding object–architecture relations. Full scores 2.42 points higher on STB and 6.91 points higher on OPEN than NoGroupAssembly. This supports the benefit of establishing local structure before placing each group as a unit, both for stability and for clearance at room openings. Full scores 5.13 points higher on ACC and 24.63 points higher on OPEN than NoHumanUse. Although NoHumanUse has higher NAV, its object accessibility and opening clearance are lower. This shows that human-use feedback adds local constraints beyond the floor-connectivity check.
The revision includes the corresponding ablation visualizations.
Reply to Reviewer jhbT
Thank you for recognizing the connection between activities, local object arrangements, and room layout.
In response to your comments, we added a component comparison on the same 30 prompts and evaluated object accessibility and opening clearance. We also analyzed the trade-offs among count, relation, and collision scores. We clarify the differences in models and budgets, the evaluation rules, and the sources of the baseline outputs. The revision will report the user study results on 20 new scenes. We address the weaknesses and questions in turn below. We hope our responses address your concerns and look forward to your feedback.