- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
They introduce a training-free T2I method that uses a VLM to convert prompts into scene graphs and object layouts, then controls attention during denoising to improve consistency with these structures. Experiments report improvements over base FLUX and some other baselines.
Critical strengths
The idea of using object relations in the scene graph to guide attention between interacting regions is well-motivated.
The control-horizon ablation clearly shows the degradation caused by excessive control.
Critical weaknesses
-
Given the cost of VLM-based prompt rewriting and graph construction, together with the warm-up procedure in Appendix A.5, reporting total computation and time per image is necessary but not reported.
-
Further ablations are needed to show how much each component contributes. It is not clear that how much improvement comes from VLM-based prompt refinement, layout guidance, and relation attention control. In particular, comparisons should include FLUX with the same refined prompt, layout-only control using identical prompts and boxes, and the full method. Also, it is not clear how well the method transfers to other backbones (e.g. models with fewer sampling steps).
-
The evaluation reports custom VLM-based scores on T2I-CompBench prompts. Results using the standard T2I-CompBench (or GenEval) evaluation protocol are not reported.
Minor notes (not affecting the score):
-
Writing: “Attend-and-Excitep” should be corrected at L133 and in Tables 1–2. Empty citations appear at L204 and L295. The method is sometimes named Graph2Scene and sometimes GraphExecutor.
-
Reproducibility: The correspondence between the manuscript and the released implementation is a bit unclear. The repo includes a complexity-based control-horizon policy and several attention modes, which makes it difficult to understand which parts correspond to the paper.
Questions for authors
-
I could not find the name of the VLM in the manuscript, although Qwen-VL-Max appears as the default in the released code. How accurately does the planning VLM extract relations and predict layouts? How closely do the objects in the generated images follow the given boxes?
-
Which methods in Table 1 use the same backbone? When the backbones are different, it is difficult to know how much improvement comes from the method itself.