- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper proposes CRAFT, a native 3D texture-generation framework that addresses intra-voxel or cross-surfaces texture bleeding between touching or intersecting surfaces by augmenting voxel coordinates with surface identities derived from a pre-provided UV-chart connectivity.
It further introduces visibility-routed reference conditioning, using first-hit visibility to associate the input reference-image features with the corresponding visible surfaces while preserving surface-specific texture representations.
Experiments demonstrate improved reference-view fidelity and occluded-region texturing, with support for surface separation, recombination, and image-guided texture editing.
Critical strengths
The practical motivation of the two new designs is valid: texture bleeding caused by limited spatial resolution and ambiguous surface identity. . The idea of preserving surface-specific texture features and routing reference-image features using visibility is intuitive and technical possible, despite for some major concerns as listed below.
Critical weaknesses
I have two major concerns over the fundamental assumptions of the work. 1. It relies on artist-created UV charts to define meaningful surface identities, which are often not available in typical AI-based 3D shape generation pipelines. 2. the first-hit visibility does not guarantee correct semantic correspondence between the reference images and the target geometry, and the results do not yet convincingly demonstrate practical effectiveness. More details can be found in below elaborations.
-
Regarding the restrictive dependence on artist-created UV charts. The method assumes that the UV-chart induced connectivity is available to provide meaningful surface identities, either based on geometry feature or semantic feature. This is a significant restrictive assumption for current AI-based 3D shape generation pipelines using VAE+diffusion or flow matching. Typically, the texturing step often follows the 3D geometry (mesh or voxel) generation, for which artist-authored UV layouts are not be available. In fact , the obtained shape is often a monolithic unsegmented shape, and I suspect the method proposed in this paper does not work at all for automatically generated UV-chart such as via X-Atlas. Moreover, to segment a mesh to semantically meaningful isolated meshes required significant cognitive burden , once done, half of the task of 3D texturing is also completed.
-
Establishing reference-image correspondences may be a very challenging task, especially for the scenarios targeted in this paper. For instance, the visibility-routing mechanism assumes that visible reference surfaces can be reliably associated with the target 3D mesh using calibrated cameras and first-hit visibility, despite that the reference images may depict different object configurations, viewpoints, or surface layouts. Since the target 3D scene can be significantly different (see the teaser image), visibility alone can not be easily detected, and moreover it does not guarantee semantic correspondence. As a result, the reported texture quality also appears insufficient and not convincing.
Overall, while the two proposed mechanisms are potentially promising, their relevance and effectiveness depends on very restrictive input assumptions and reliable surface correspondences; this dependence as well as its limited demonstrated texture quality raise substantial concerns about generality and practical applicability. To conclude, the contribution and quality of the paper is far from meeting the standard for ICLR.
Questions for authors
Some critical questions related to the above major weaknesses:
-
How does CRAFT perform when artist-authored UV charts are unavailable, or when automatically generated UV charts do not align with meaningful geometric or semantic surface boundaries?
-
Can your method handle monolithic meshes produced by standard 3D generation pipelines without manual UV authoring?
-
How robust is visibility-routed conditioning when the reference images and target 3D geometry differ significantly in camera pose, part configuration, or semantic surface correspondence?
-
3D Native texture generation becomes a new trend, as you mentioned Why you did not compare your method with any of the STOA methods such as NaTex , LaFiTe and TEXTRIX , which also based on structured latent voxel-based native texture generation ?
4 comments
Author response to Concern #2: Can CRAFT handle monolithic meshes produced by standard 3D generation pipelines without manual UV authoring?
Concern #2. Can CRAFT handle monolithic meshes produced by standard 3D generation pipelines without manual UV authoring?
Author response to Concern #2: Yes. To address reviewer’s concern, we add a new Section 4.4 to illustrate our method can be integrated as a texture refinement module in standard 3D generation pipelines.
Specifically, we selected monolithic meshes from Tripo3D’s curated collection, used its part segmentation tool to identify semantic parts, and applied its part completion tool to close holes in the separated components. The original textures appeared coherent when the meshes were assembled. Separating the parts, however, revealed contact imprints at component interfaces and abrupt color changes on previously occluded surfaces (Fig. 7, Input Texture).
We illustrate CRAFT can be applied as a texture refinement module in the standard 3D generation pipelines. To refine the imprints and abrupt color, we render six views of the original assembled mesh to condition CRAFT and compare its results with those of other methods that accept multiple input views. The examples show that CRAFT fills the exposed contact regions with colors consistent with the surrounding texture on each part. We can also refine a selected part by holding the tokens of all other parts fixed, preserving their original high-resolution textures. Also, this setup required no manual UV authoring.
Author response to Concern #3: How robust is visibility-routed conditioning to differences in camera pose, part configuration, or semantic correspondence?
Concern #3. How robust is visibility-routed conditioning to differences in camera pose, part configuration, or semantic correspondence?
Author response to Concern #3. CRAFT addresses texture bleeding between contacting surfaces given an aligned reference image and a known camera pose. For each reference pixel, first-hit visibility identifies the target surface intersected by its camera ray and routes the image feature to that surface’s token. TEXGen uses a similar evaluation setup, rendering its conditioning image from a known viewpoint and passing the corresponding camera matrix to the texture generation model.
We apologize for the misleading impression our teaser may have given. We perform visibility routing and generate the texture with the parts in their original assembled configuration. We separate them only afterward to inspect the generated textures on previously occluded surfaces. The reference image and target mesh therefore share the same part configuration during visibility routing.
Section 4.4 illustrates how this setting arises in a modern 3D generation pipeline. We render the assembled mesh from six known viewpoints and use automatically predicted part IDs as surface groups. CRAFT then refines textures at contact regions while preserving the original textures of unselected parts.
As discussed in our response to Concern #1, we evaluated CRAFT with different surface groupings, including automatically generated partitions that do not necessarily align with semantic part boundaries. These experiments test how changes in surface grouping affect texture quality while the reference image and target mesh remain aligned.
Ablation under calibrated alignment. We evaluated the contribution of visibility routing and other components on the original 105-asset ablation set. The first table reports PSNR, SSIM, and LPIPS over the full reference-view rendering.
| Method | PSNR ↑ | SSIM ↑ | LPIPS ↓ |
|---|---|---|---|
| Ours | 27.176 | 0.9567 | 0.0554 |
| w/o surface-address packing | 25.016 | 0.9483 | 0.0582 |
| w/o BP. Ref. Injection | 24.766 | 0.9500 | 0.0622 |
| w/o visibility | 24.932 | 0.9482 | 0.0643 |
| w/o SA surface-isolation | 24.211 | 0.9438 | 0.0632 |
| w CA across surface | 23.973 | 0.9458 | 0.0636 |
The second table reports PSNR, MAE, and RMSE on newly exposed surfaces, using masked pixels in the exploded view and masked texels in UV space.
| Method | UV mask PSNR ↑ | UV mask MAE ↓ | UV mask RMSE ↓ | Explode mask PSNR ↑ | Explode mask MAE ↓ | Explode mask RMSE ↓ |
|---|---|---|---|---|---|---|
| Ours | 19.979 | 0.07470 | 0.11725 | 18.439 | 0.09126 | 0.14415 |
| w/o surface-address packing | 16.756 | 0.11538 | 0.16373 | 16.120 | 0.12072 | 0.17495 |
| w/o BP. Ref. Injection | 15.597 | 0.12581 | 0.18540 | 14.939 | 0.13765 | 0.20164 |
| w/o visibility | 15.974 | 0.12134 | 0.17778 | 15.464 | 0.12978 | 0.19068 |
| w/o SA surface-isolation | 14.291 | 0.15128 | 0.20892 | 14.032 | 0.15561 | 0.21578 |
| w/ CA across surfaces | 14.918 | 0.14246 | 0.20038 | 14.593 | 0.14488 | 0.20523 |
Removing visibility routing reduced reference-view PSNR from 27.176 to 24.932 dB. On newly exposed surfaces, PSNR fell from 18.439 to 15.464 dB in the exploded view and from 19.979 to 15.974 dB in UV space. These results support the contribution of visibility routing when the reference and target are aligned.
We also added Pixal3D as a baseline in the revised manuscript. CRAFT was inspired by Pixal3D’s approach to back-projecting reference-image features into a 3D representation. To control for camera pose, we provided Pixal3D with the same ground-truth reference camera pose used by CRAFT at inference. On the 158 held-out assets, CRAFT achieved a reference-view PSNR of 26.105 dB and LPIPS of 0.0321, compared with 25.726 dB and 0.0365 for Pixal3D. After part separation, Figure 4 shows that moving a white book reveals a white imprint on the wooden tabletop in the Pixal3D result. CRAFT reduces this imprint, illustrating its ability to limit texture bleeding between contacting surfaces.
If the reference image and target mesh depict different part configurations, first-hit visibility alone cannot establish semantic correspondence. For example, if a book appears in different positions in the reference image and target mesh, a pixel depicting the book may project onto the tabletop, causing its feature to be routed to the table.
Author response to Concern #4: 3D Native texture generation becomes a new trend, as you mentioned Why you did not compare your method with any of the STOA methods such as NaTex , LaFiTe and TEXTRIX , which also based on structured latent voxel-based native texture generation?
Concern #4: 3D Native texture generation becomes a new trend, as you mentioned Why you did not compare your method with any of the STOA methods such as NaTex , LaFiTe and TEXTRIX , which also based on structured latent voxel-based native texture generation ?
Author response to Concern #4:We could not evaluate NaTex, LaFiTe, and TEXTRIX because its code and checkpoint were unavailable. Direct quantitative comparisons with these three methods therefore remain open.
Our evaluation includes TRELLIS.2, and the revision adds both quantitative and qualitative comparisons with Pixal3D. These two methods are also voxel-based native texture generation methods. Pixal3D is particularly relevant because it also back-projects image features into a 3D representation.
As mentioned in the response to Concern #3, we provided Pixal3D with the same ground-truth reference camera pose used by CRAFT at inference. On the 158 held-out assets, reference-view PSNR was 26.105 dB for CRAFT, 25.726 dB for Pixal3D, and 22.014 dB for TRELLIS.2. On newly exposed pixels in the exploded view, the corresponding scores were 14.362, 14.283, and 11.611 dB. In the revised manuscript, Figure 4 in the revised manuscript further illustrates the practical difference at a contact surface: moving a white book reveals a white imprint on the wooden tabletop in the Pixal3D result, while CRAFT reduces the imprint.
We made every effort to include all relevant native 3D texture generation methods for which we could obtain runnable inference code and checkpoints. We hope the comparisons with TRELLIS.2 and Pixal3D provide a convincing evaluation of our work.
Author response to Concern #1: How does CRAFT perform when artist-authored UV charts are unavailable or do not align with meaningful surface boundaries?
We sincerely appreciate your insights and would like to address the concerns you raised regarding the practical effectiveness.
Concern #1: How does CRAFT perform when artist-authored UV charts are unavailable or do not align with meaningful surface boundaries?
Author response to Concern #1: We apologize that our original description gave the impression that CRAFT requires artist-authored UV charts at inference. We use UV-chart connectivity during training because it provides surface groups directly from textured meshes without additional annotations. At inference, CRAFT uses a surface ID to identify surfaces that should exchange texture information. These IDs can come from semantic labels, automatic part segmentation, or geometric partitioning.
In Appendix A, we evaluate five surface grouping strategies using the same trained model on 158 held-out PartObjaverse-Tiny assets. The table reports reconstruction in the reference view and completion on UV texels exposed by part separation.
At approximately 12 groups per asset, completion PSNR for the three automatic strategies ranged from 12.44 to 13.15 dB. Reference-view quality was relatively stable across the five strategies at the tested granularity of roughly 8–12 groups per asset on average. Completion on newly exposed surfaces was more sensitive to the partition.
To address the reviewer’s question about automatically generated UV charts, we use XAtlas to generate charts directly from each mesh. We keep these charts fixed and vary how they are merged to obtain 12, 32, 64, 128, or 256 surface groups per asset. We evaluate reconstruction in the reference view and texture completion on UV texels corresponding to surfaces revealed by part separation.
Reference-view PSNR varied by less than 0.13 dB across all five settings. Completion on newly exposed surfaces was more sensitive to fragmentation. As the group count increased from 12 to 256, UV-space PSNR fell at every step, from 12.44 to 11.68 dB, and MSE rose from 0.09208 to 0.10220.
These results show that CRAFT can use automatically generated XAtlas groups at inference, although fine partitions can separate an occluded region from the visible texture cues that guide its completion. We therefore recommend avoiding excessively fine partitions at inference, particularly when completing textures on occluded surfaces.