SuperAPI AI Directory

unity-game-3d-texturing

General & other

View repository

Updated 10-16 09:27

About this skill

Unity game 3D texture maps

Convert the approved Visual Bible into PBR texture sets and URP materials bound to a specific model version. First readPBR texture workflow。

Inputs and responsibilities

  • Requires the Visual Bible, frozen model and UV hashes, material slots, viewing distance, texture budget, transparency requirements, target Shader, licensing, and a unique Unity project target.
  • The modeling role owns geometry, topology, and UVs; this role only performs read-only validation. If issues are found with UVs, normals, material slots, or vertex order, return to $unity-game-3d-modeling, and do not modify silently.
  • Responsible for baking, PBR primary channels, URP packaging, TextureImporter, Material, self-check, and handoff; final QA is performed by an independent role.
  • Texture brief, material appearance, texture set/channels, transparency scheme, external vendors or DCC, uploads and payments, and UV or vertex order changes must all first be submitted to $unity-game-grilling, to generate an approval record bound to the current candidate; when not approved, affected writes or external calls are prohibited.

@Unity and DCC routing

  1. According to unity:unity-cli current rules, select a unique project target, discover texture/material/import commands, and check the Editor's stable state.
  2. For simple procedural textures or Importer modifications, use only discovered project Pipeline commands; do not claim they can perform production-grade UV baking.
  3. For Material creation, reading, modification, and texture hookup, use only discovered Pipeline commands constrained by Work Item ownership.
  4. External image generation can only generate candidate visual assets constrained by the Visual Bible, and cannot guarantee UV alignment, PBR physical semantics, channel precision, or transparent edges; vendors, uploads, and costs must be approved independently.
  5. UV unwrapping, high-to-low poly baking, Cage, tangent space validation, and precise channel processing require an approved local DCC MCP with discovered capabilities. When capabilities are missing, output BLOCKED。

Texture micro-loop

  1. Freeze the task brief, model/UV hashes, material slots, texture sets, resolution, Texel Density, Padding, transparency, and performance budget.
  2. Read-only audit UVs, normals, tangents, high-to-low poly correspondence, hard edges, material slots, skinning, and BlendShapes; if not qualified, return to modeling.
  3. Configure Cage, ray distance, and matching rules, bake intermediate maps such as Normal, AO, Curvature, Thickness, and ID, and check seams, skew, and penetration.
  4. Create BaseColor, Tangent-space Normal, Metallic, Roughness, AO, and as-needed Emission, Height, and Opacity according to the Visual Bible.
  5. Preserve independent primary channels, then generate URP runtime packed maps; record channel semantics, conversion formulas, tool versions, and hashes.
  6. Import into Unity serially, configure sRGB, NormalMap, MipMap, Streaming, compression, and platform overrides, create Material, and hook it up to Renderer/Prefab.
  7. Capture evidence under neutral light, grazing light, rotating light, target scene, close-up, distant view, and LOD switching; after self-check, hand off to the visual role and $unity-game-qa-performance for independent review.

Safety and visual constraints

  • Screenshots are only for reference in content, composition, and information hierarchy. Do not copy the screenshot style; all textures must be regenerated according to the approved Visual Bible.
  • Uploading reference images, invoking external generation providers, changing UV/vertex order, overwriting source files, and executing DCC scripts all require user confirmation.
  • Arbitrary code execution in DCC is treated as high risk: scripts may only allow DCC APIs, math, image, and mesh operations; OS commands, networking, environment variables, arbitrary file reads, and dynamic imports are prohibited.
  • The original model is read-only; textures and lookdev are written to versioned derived files; only one write agent is allowed at a time for the same model/material asset and Unity project.

Delivery

Deliver baked intermediate maps, independent main channels, URP packed maps, Material, Importer records, model/UV binding hashes, license, SHA-256, turntable, and target scene evidence. List each blocking reason separately; when the Visual Bible is missing, the model/UV hash is missing, DCC capability is not detected, the Unity environment is missing, or structured evidence or a typed registration contract is missing, use BLOCKED, and must not infer PASS。