- Rating
- 3(+1)
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
SpatialFactory is an agentic framework that generates compositional 3D scenes from text and floorplan instructions through top-down visual planning, geometric lifting, asset generation, and iterative spatial refinement. Its contributions include this integrated pipeline, a benchmark of 111 professionally crafted scenes across 12 indoor categories, and a toolkit for rendering and exporting generated scenes. Validation includes baseline comparisons using a common foundation model, spatial-understanding experiments across seven models, component ablations, and a preference study, with reported improvements in instruction following and perceived scene quality.
Critical strengths
Strengths are:
-
Effective integration of visual planning and 3D refinement. The framework combines a global top-down visual plan with geometric lifting and iterative object/layout correction. Its experiment results suggest that this combination is useful for generating detailed scenes from complex spatial requirements.
-
Substantial evaluation and a useful benchmark. The 111-scene benchmark includes structured layouts and ground-truth meshes, supporting evaluation beyond visual appearance. Comparisons using a common foundation model, spatial-understanding ablations, and a 43-participant human study provide complementary evidence for the reported improvements.
Critical weaknesses
My major concersn are as follows:
-
The contribution of the proposed framework is not sufficiently isolated. The shared-backbone comparisons and lifting ablations provide some evidence of benefit, but they do not establish how much of the full scene-generation improvement comes from the proposed design rather than the capabilities of pretrained models. This limits confidence in the framework’s methodological contribution and its value as foundation models improve.
-
The positioning against closely related methods is incomplete. The paper should more clearly distinguish its contributions from agentic approaches and discuss recent image-based scene-generation methods such as I-Scene. A comparison with I-Scene under compatible inputs would help evaluate the image-to-3D realization stage. Without this discussion and appropriate comparisons, the claimed advances in compositional generation and generalization remain insufficiently established.
-
Insufficient validation of physical stability and difficult relations such as containment and placement underneath objects and lack of runtime estimates by object counts.
Questions for authors
- The introduction states that the pipeline does not require specialized detection, segmentation, or depth-estimation models. However, the proposed method use cropped object image for asset generation. Please clarify which stages require segmentation and whether this optional procedure was used in the reported experiments.
- The paper describes orientation, scale, and layout correction, but their individual effectiveness remains insufficiently evaluated. How much does each component improve spatial relations, and physics such as collision / stability? Please also clarify whether collisions during refinement are detected through geometric computations or inferred from visual feedback.
- Although the representation supports “inside,” “below,” and support relations, their correctness is not evaluated separately. The metric use 3DBB/2DBB to evalaute, how valid containment and support contacts are distinguished from collisions? Mesh-based collision and floating metrics are useful, but do the generated scenes remain physically stable after simulation?
- Table 3 supports a benefit from the proposed pipeline, but the improvement from 3D lifting becomes smaller with GPT-6 Astra. Do the other proposed components still provide meaningful gains with stronger foundation models?
- The paper acknowledges missed small or occluded objects and distortions in generated assets. How reliably does the crop-to-image-to-3D process preserve the intended object’s shape and details?
- Using the same Gemini backbone makes the main comparison more controlled. However, asset-generation components differ, and SceneWeaver’s retrieval initialization was removed. How do these changes affect the results, and how much of the improvement can be attributed specifically to the proposed framework?