← Back to project

3D Data · Material-Import Bug Audit (renders_cond)

Detecting assets whose conditioning render lost its materials · 1.1M scanned · 2026-07-09
data-qualitymaterial-bugready_v4filtering

TL;DR

91,814 assets (8.4%) have a material-import bug: the Blender-3.0.1 conditioning render (the model INPUT) came out grey/untextured, while the object's real PBR material (the SUPERVISION) is colorful. Input and supervision disagree.
Detected by comparing two saturations per asset: cond_sat (render foreground) vs gt_sat (decoded PBR base_color). BUG = render grey AND material colorful. This separates true bugs from the 231,673 (21%) assets that are legitimately untextured.
The bug is not a Blender-version fault — re-rendering the same GLB (even with 3.0.1) restores the material; the original run had a transient material-import failure. Fix = re-render the flagged 91,814.

1 · Bug rate by subset

① Material-bug rate per subset. Sketchfab-sourced sets (TexVerse, SketchfabV1) carry almost all of it.

2 · Detection logic

② Each point is an asset. The red top-left quadrant (grey input, colorful material) is the bug; the dashed lines are the thresholds.

3 · The bug, seen

③ 16 flagged bugs. The grey render on the left is the training input; the colorful projection on the right is the material it was supposed to show.

4 · How the GT was recovered (the enabling trick)

5 · Next step

Detector: cond_sat (renders_cond webp) vs gt_sat (PBR base_color via shape_dec->tex_dec). 2x H200 nodes + 1 CPU node, ~4h. Scores at /fsx/home/weikai.huang/3dgen/data/material_bug_flags.jsonl