360 Secure SkillHub
360 安全技能中心

texture-state-animation

该 Skill 提供纹理状态动画的设计规范与验收流程:先对齐并归一化各纹理状态,再按图层分别选择过渡方式,避免整帧交叉淡化与纹理跳变,最后检查导出格式能否复现动画;并附带一个生成过渡方案、标记整帧淡化风险的 Python 脚本。

RobLe3
热度 0.00
最近更新 2026-10-19 02:52:34
分类:创作依赖:MCP 服务 / 代码执行 / 读写文件应用场景:品牌素材 / 视频编辑 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add roble3/cc-blender-skill/texture-state-animation
Metadata
name
texture-state-animation
description
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.
allowed-tools
Read Bash Glob Grep mcp__blender__execute_blender_code mcp__blender__get_scene_info mcp__blender__get_object_info mcp__blender__get_objects_summary mcp__blender__get_object_detail_summary mcp__blender__render_viewport_to_path mcp__blender__search_api_docs mcp__blender_official__execute_blender_code mcp__blender_official__get_objects_summary mcp__blender_official__get_object_detail_summary mcp__blender_official__render_viewport_to_path mcp__blender_official__search_api_docs

MCP backend

Use when: Texture state animation, texture morphs, material state transitions, image sequence planning, masked wipes, glow reveals, texture registration, avoiding bad crossfades, GLB-compatible texture animation planning.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

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, shape keys, object transforms;
    • image sequence only if target supports it;
    • avoid Blender Python handlers for final GLB unless the target runtime will recreate them.
  5. Render a contact sheet and flicker report before calling the animation acceptable.

Acceptance gates

  • Each texture state is registered to the same bbox/landmarks.
  • No full-canvas crossfade is used unless state registration and semantics match.
  • Avatar silhouette remains stable unless the story explicitly calls for a morph.
  • Context/aura elements are separate from the avatar material.
  • The exported format can reproduce the animation, or limitations are documented.

Scripts

  • scripts/texture_transition_plan.py creates a transition plan from source states and flags risky whole-frame crossfades.