Material Texture Generate
Outcome
Create coherent material maps whose physical interpretation survives engine import.
Required inputs
- surface brief and rights-cleared references
- target shader workflow
- resolution, texel density, tiling scale, and compression budget
Ask for missing information only when it changes the route materially. Otherwise
state conservative assumptions and proceed with read-only analysis.
Workflow
- Define material class, real-world scale, lighting assumptions, map channels, color spaces, and packing convention.
- Choose a licensed generation route compatible with available hardware.
- Generate source maps without replacing existing project textures.
- Validate seamless tiling, albedo range, roughness response, normal orientation, height continuity, and channel packing.
- Preview on representative geometry under neutral and production lighting, then test engine import and compression.
Expected artifacts
- material specification
- source and packed maps
- sphere and plane previews
- engine material instance
- provenance record
Workflow-specific gates
- Treat base color as color data and linear maps as non-color data.
- Never infer legal reuse from a reference image being publicly visible.
- Flag baked lighting, inconsistent scale, edge seams, clipping, and implausible metallic values.
Production completion gate
Before recommending production use, complete and report all seven gates:
- Rights, consent, code/model/dataset/output license, and generation-provenance checks.
- Technical format, naming, scale, color, metadata, and target-import validation.
- Visual and temporal consistency review across representative views and states.
- Runtime memory, frame-time, draw-call, streaming, and asset-budget checks.
- Playability and interaction smoke tests in the target runtime.
- Screenshot, capture, diff, or artifact-regression evidence with reproducible settings.
- Human approval before replacing source assets or promoting generated output.
Unknown rights, missing consent, unsupported hardware, conflicting host adapters,
or failed quality gates block production promotion. Preserve originals and make
fallbacks explicit.
1---2name: material-texture-generate3description: Generate and validate tileable, color-managed PBR material sets for a specified engine shader and texel-density budget.4---56# Material Texture Generate78## Outcome910Create coherent material maps whose physical interpretation survives engine import.1112## Required inputs1314- surface brief and rights-cleared references15- target shader workflow16- resolution, texel density, tiling scale, and compression budget1718Ask for missing information only when it changes the route materially. Otherwise19state conservative assumptions and proceed with read-only analysis.2021## Workflow22231. Define material class, real-world scale, lighting assumptions, map channels, color spaces, and packing convention.242. Choose a licensed generation route compatible with available hardware.253. Generate source maps without replacing existing project textures.264. Validate seamless tiling, albedo range, roughness response, normal orientation, height continuity, and channel packing.275. Preview on representative geometry under neutral and production lighting, then test engine import and compression.2829## Expected artifacts3031- material specification32- source and packed maps33- sphere and plane previews34- engine material instance35- provenance record3637## Workflow-specific gates3839- Treat base color as color data and linear maps as non-color data.40- Never infer legal reuse from a reference image being publicly visible.41- Flag baked lighting, inconsistent scale, edge seams, clipping, and implausible metallic values.4243## Production completion gate4445Before recommending production use, complete and report all seven gates:46471. Rights, consent, code/model/dataset/output license, and generation-provenance checks.482. Technical format, naming, scale, color, metadata, and target-import validation.493. Visual and temporal consistency review across representative views and states.504. Runtime memory, frame-time, draw-call, streaming, and asset-budget checks.515. Playability and interaction smoke tests in the target runtime.526. Screenshot, capture, diff, or artifact-regression evidence with reproducible settings.537. Human approval before replacing source assets or promoting generated output.5455Unknown rights, missing consent, unsupported hardware, conflicting host adapters,56or failed quality gates block production promotion. Preserve originals and make57fallbacks explicit.
frabcd