- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
Easy-3Dfy separates single-image 3D scene construction into object generation and layout estimation. It extracts partial object point clouds from a predicted pointmap and uses an RPF-based registration module to establish correspondences with complete object meshes. It then estimates a rotation, translation, and uniform scale for each object to assemble the scene. The registration module is trained on object-level data without complete scene supervision. Experiments on Scene-Maker and 3D-FUTURE200 show improved layout metrics and compatibility with different upstream models.
Critical strengths
1.The modular design has practical value. Mesh and point-cloud interfaces connect object generation with layout estimation, making it easy to replace generators, including commercial APIs. Experiments with multiple generators support this flexibility. 2.The main comparison isolates the contribution of layout estimation. Using the same object meshes as SAM-3Dfy allows improvements in scene metrics to be attributed to layout estimation rather than asset differences. Scene-CD, Scene-FScore, and BBox IoU improve on both datasets.
Critical weaknesses
1.The advantages over existing registration methods remain unclear. The method follows the RPF architecture and training objective, while CAST already generates corresponding points and then fits similarity transforms. The modular design is useful, but comparisons with other registration methods under matched conditions are missing. This makes it difficult to assess what the task-specific adaptation adds. The method also uses 50 flow inference steps without clearly reporting the inference hardware, batch size, or peak GPU memory usage. Without comparisons, it remains unclear whether the accuracy gains justify the computational cost. 2.The effects of input errors, generated-asset differences, and inter-object relationships are not sufficiently evaluated. The paper includes pointmap and generator comparisons, geometric augmentation, and failure cases, but does not systematically test different levels of depth distortion and shape mismatch. The final uniform scaling also cannot correct differences in object aspect ratios. 3.The registration module discards RGB to avoid interference from appearance differences. Table 8 supports this choice under the current geometric metrics, but does not assess the cost of losing appearance cues—for example, whether geometrically symmetric objects are oriented consistently with the input image. 4.Objects are also registered separately, without explicit constraints between them. Claims of reduced floating and interpenetration rely mainly on qualitative examples, without quantitative results on contact, support, or penetration. Although the authors discuss metric limitations, these claims still need more direct validation.
Questions for authors
1.What specific improvements does the task-specific adaptation provide over CAST and other registration methods with appropriate scale handling? Can they be compared using the same meshes, pointmaps, and evaluation protocol? 2.What are the registration module’s latency, throughput, and peak GPU memory usage under specified hardware, batch size, and input point count? Compared with other registration methods, do its accuracy gains justify any additional computational cost? 3.Can the effects of pointmap errors, aspect-ratio differences, and local shape changes on layout accuracy be quantified? For geometrically symmetric objects with distinct textures, does discarding RGB affect orientation estimation? 4.Are there quantitative results on penetration, contact, or support relationships that support the claimed improvements in inter-object spatial relations?