- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper tackles automatic UV seam placement. MeshQuery is a training-free framework where a VLM queries a preprocessed relational mesh database in SQL and writes its seam plan as a DSL program over aggregate edge-selection operators, refined from UV metrics. The innovation is the agent interface rather than new geometry, keeping token cost near-constant with mesh size. It gives 3-4x fewer charts and 1.6x shorter seams than PartUV, preferred by annotators in ~80% of comparisons.
Critical strengths
- A scalable agent interface. The VLM never touches raw geometry: SQL queries plus aggregate edge operators keep tool calls and tokens near-constant (36k vs 230k for OBJ), enabling ~300k-face meshes.
- Clear and accessible writing. The pipeline figure, the DSL example, and the appendix implementation details make a fairly intricate system easy to follow and, in principle, reimplementable.
Critical weaknesses
- Limited practicality: the method needs clean quad meshes, yet production assets often have irregular connectivity from which no reliable edge loops can be extracted.
- Core contribution unablated: no experiment shows that the queryable representation and DSL, rather than the VLM's intrinsic capability, drive the gains on this task.
Questions for authors
- Connectivity requirement. How does the method's performance degrade when the input mesh has poor edge flow?
- Semantic resolution. Was K = 8 ever varied? How do seam quality and failure rate change on assets with many parts, such as characters, garments or multi-part props?
- Role of the visual channel. What do render_view, get_pick_view, pick_points and preview return, and when are they invoked? How much do the metrics change if all image inputs are removed?
- FlattenAnything configuration. Figure 4 shows roughly 14k charts, which contradicts that method's low-chart design. Are the reported sampling and iteration counts its official defaults at this scale, and can you reproduce its published behavior on its own evaluation assets before transferring the configuration here?
5 comments
Answers to wYAV
Q4. FlattenAnything configuration.
FAM run with the original configuration of 10,000 iterations, and we re-ran it with the recommended
clean mesh() preprocessing (which we previously avoided as it alters the input mesh). We
reproduce the test script with per-vertex UVs agreement of 5·10−9. In Table 8, we also reproduced
evaluations on libigl library meshes (camel-head, cow, fandisk, fertility) using published values.
Substance meshes may contain multiple sub-meshes, justifying FlattenAnything chart count higher
than 1.0. In Table 9 we report our updated values for FlattenAnything on our dataset.
□ We will update Table 1 of the main paper with these values.
Table 8: Conformal distortion of FlattenAnything on reproducing four models of its paper. We use public libigl versions of the meshes.
| Model | Paper reported | Our rerun |
|---|---|---|
| camel-head | 0.088 | 0.147 |
| cow | 0.210 | 0.329 |
| fandisk | 0.105 | 0.124 |
| fertility | 0.166 | 0.222 |
Table 9: FlattenAnything on TOYS4K-50 and SUBSTANCE-50 10,000 iterations, with additional
preprocesssing clean_mesh() (n) denotes the number of successful runs within the 30-minute
time budget. FlattenAnything produces 1 UV island per mesh; therefore, seam quality metrics are
unavailable. Substance meshes may contain multiple sub-meshes, justifying an average chart count
higher than 1.0.
Toys4K-50
| Input (n) | UV charts ↓ | UV seam ↓ | 3D seam ↓ | AO ↑ | Non-disk ↓ | Compact. ↑ | Convex. ↑ | Jagged. ↓ | Texel spread ↓ | Area dist. ↓ | Conf. dist. ↓ |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Published (49) | 13974.4 | 108.1 | 159.2 | 0.499 | 0.002 | 0.509 | 0.984 | 0.91 | 0.761 | 1.596 | 17.187 |
| Welded rerun (50) | 1.0 | — | — | — | 0.940 | — | — | — | 1.419 | 4.177 | 11.709 |
Substance-50
| Input (n) | UV charts ↓ | UV seam ↓ | 3D seam ↓ | AO ↑ | Non-disk ↓ | Compact. ↑ | Convex. ↑ | Jagged. ↓ | Texel spread ↓ | Area dist. ↓ | Conf. dist. ↓ |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Published (50) | 19.7 | 17.0 | 5.9 | 0.545 | 0.298 | 3.042 | 0.902 | 0.58 | 1.703 | 4.067 | 43.716 |
| Welded rerun (37) | 2.4 | — | — | — | 1.000 | — | — | — | 1.697 | 4.501 | 58.199 |
We kindly let the reviewer know we have uploaded the revised PDF, incorporating the additional experiments and clarifications discussed in our responses. We would be grateful for the reviewer's view on whether our response to the weaknesses addresses the concerns. We recognize reviewers are busy, and we appreciate the time already spent on our submission.
Answers to wYAV
W1, Q1. Limited practicality / Connectivity requirement.
While our method leverages quad meshes (the default in industry DCC pipelines), we show that it extends to irregular triangle meshes (Fig. 14) by replacing topological loop operators with SeamCut (Lucquin et al. 2017) at the cost of additional time. Across five triangle meshes, on average, 44.40% of interior vertices deviate from the regular valence of 6, while 9.62% of faces have minimum angles below 10◦, indicating irregular connectivity and poor triangle quality.
We kindly refer to our General Comment for conclusions and action items related to this comment.
W2. Core contribution ablated.
We ablate the core contribution by providing the VLM backbone with the prompt “We want to UV-unwrap this mesh most professionally. List indices of the edges that we should mark as seams.”, the OBJ path and an offline shell with Blender (no queryable representation, labels, DSL, MCP tools, images, evaluator feedback or gates). We report the three Toys4K-50 quad meshes subset. We see that frontier Opus 5 can provide a seam plan for the task without our framework. However, it is less efficient, slower, and more expensive. On the opposite, Qwen3.8-27 B cannot solve the task without our framework: no final answer contains an edge list. We conclude that the proposed framework enables the frontier Opus 5 backbone at a reduced cost, and enables smaller non-frontier Qwen backbone.
These findings are further extended with other backbones and ablations, merging multiple comments, as discussed in our General Comment. We therefore include conclusions and action items in the General Comment.
Q2. PartField K Variation for Text Semantic Resolution.
We explore varying PartField K ∈{4,8,16} tested on opus 5 in Table 13 over three random Toys4K- 50 subset meshes. The framework is robust to different values of K, and all metrics remain in a comparable range. We conclude that frontier backbones are more robust to text-prior quality and benefit in speed. From the core ablation in the general comment, smaller VLM backbones gain distortion performance from the textual prior.
□ We will include this ablation analysis in the appendix.
Table 13: PartField K ablation over three quad meshes.
Q3. Role of the visual channel.
In Table 12, we ablate the visual channel on three random toyz4k-50 meshes. Opus 5 remained effective, indicating strong abstraction of our mesh representation, while the smaller model Qwen3.5- 9B benefits more from visual support. We attribute this to Opus’s stronger reasoning abilities. In addition, we remark (Fig. 17, Appendix) that
get_pick_view(21) andpick_points(7) are used much less thanquery(942) among the paper’s 100 benchmark runs.get_pick_viewreturns a PNG of the mesh from a given view, andpick_pointsannotates points projected into the figure for a geodesic seam.□ We will include this ablation in the appendix.
Table 12: Opus 5 and Qwen3.5-9B visual feedback ablation.