← ClaudeAtlas

texture-state-animationlisted

Design and validate texture-state transitions for Blender animations without ugly whole-image crossfades, texture popping, misregistered morphs, or target-engine-incompatible Python-only swaps. Use when animating between multiple source textures, mascot/logo states, style states, lightmaps, decals, or UI skins.
MAX-786/claude-3d-harness · ★ 6 · Web & Frontend · score 74
Install: claude install-skill MAX-786/claude-3d-harness
# Texture State Animation This skill exists because “crossfade several full images” usually looks bad. Texture animation must be designed like motion graphics: registered states, constrained transition channels, and preview gates. ## Failure modes to avoid - Whole-frame crossfades between unrelated crops/compositions. - Python frame handlers as the only playback mechanism when export/runtime support is needed. - Texture swaps that change silhouette, camera crop, or scale at the same time as decorative motion. - Mixing aura/background/HUD pixels into the avatar surface texture unless that is the intent. - Morph pulses that break accepted geometry constraints such as constant depth. ## Workflow 1. **Register states first**: crop, scale, align, and color-normalize all source states into one canvas and one semantic mask. 2. **Classify pixels/layers**: - avatar surface/base; - facial decal/features; - glow/emission accents; - background/aura/context; - HUD/circle elements. 3. **Choose transition type per layer**, not one global blend: - avatar surface: hold, shimmer, subtle value/roughness pulse, or masked dissolve; - face features: hold or short opacity fade; - glow accents: emission pulse / traveling highlight; - aura/HUD: independent orbit/dash/dot animation; - background: separate plane/compositor, never baked into avatar unless requested. 4. **Use export-compatible channels when needed**: - keyframed material values, opacity, UV transform