- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
StateFlow is a framework built around an editable 3D world with three components: State Construction, State Evolution, and State Access. Current image and video generation methods all directly output the results from the prompt, which provides limited support for local editing, long-horizon evolution, and scene revisitation. StateFlow can support accurate control for generation. It splits the whole generation process into state generation and rendering, which makes sense.
Experiments show that StateFlow achieves high scores in scene reconstruction, object consistency, camera control, and background stability. The qualitative results are amazing.
Critical strengths
The paper proposes a complete framework for future visual generation, providing accurate control and convenience for creation. For the visualization, the qualitative results are amazing.
The workload involved in this work is substantial.
Critical weaknesses
I have to say that this paper seems more like an engineering report than a research paper. The core idea of StateFlow is to maintain an editable 3D scene representation, but such an idea has already been explored in many previous works and is relatively common in some industrial workflows.
The 3D state representation of each object in this paper only includes its geometry, position, orientation, and semantic attributes. Therefore, StateFlow cannot adequately represent physical attributes such as density. The representation mainly consists of static geometry together with time-varying poses and discrete asset replacements, rather than a full physical or 4D world model. As stated in the appendix, the next state for non-rigid motion is also generated as a new asset, while the original text-to-video model is likewise responsible for generating the transition. I therefore do not clearly understand why the proposed approach should be superior to direct text-to-video generation in this setting. Because the separate generation of different states' images is prior not to obey the physical rule, as it lacks temporal constraints.
Questions for authors
- Among the three components, I think State Evolution is the most distinctive part of StateFlow. The authors state in the related-work section that previous methods mainly focus on initial scene construction or fixed dynamic sequences. However, selectively editing a designated object while preserving other objects can already be implemented in conventional 3D software such as Blender. Although the ablation study in the paper shows that removing the state table leads to performance degradation, I still find this design relatively trivial. Therefore, the authors should clarify the specific technical contribution of State Evolution beyond standard object-level editing.
- The experiments should more directly evaluate the effectiveness of State Evolution in multi-round revision, as the paper claims the ability. In particular, they should demonstrate whether the world state remains stable after multiple rounds of revision, including the preservation of object identity, background content, spatial relationships, and previous edits.
- The complete pipeline consists of many components, including image generation, VLM-based matching, 3D asset generation, state updates, rendering, and video generation. These stages may introduce and accumulate errors. How does StateFlow detect, prevent, or correct such accumulated errors? The experiments should report the end-to-end success rate.
- A valuable baseline would be an agent-controlled workflow based on simple white-box or proxy geometry. This would help determine whether detailed 3D assets are actually necessary for layout and camera control. GEN3C should also be included as a relevant baseline, since it uses explicit 3D geometry for world-consistent video generation and camera control.
- The reported computation time is as high as 17 minutes for a representative scene, which also raises unavoidable concerns about the practical usability of the system. Is such a pipeline truly suitable for an interactive and creator-friendly workflow, given its high latency and potentially high cost?
- In Conflict-Aware Dual-View Initialization, the two generated views may contain inconsistent evidence, which could lead to ambiguous or inaccurate scene construction. I am also not convinced that a VLM can reliably match all object instances across the two views, especially when the scene contains multiple visually similar objects.