blender-motion-state-inspection

Topics in the source

• Blender Motion State Inspection
• When to Use
• Core Principle
• How It Works
• Inspection Workflow
• Recommended Report Shape
• Examples
• Walk Cycle With Foot Sliding

A Blender character looks twisted, mirrored, flattened, offset, or foot-sliding in an animation. A user asks whether an imported avatar, armature, or retargeted motion matches an expected pose. You need to compare rendered evidence with structured facts such as bones, bounding boxes, contacts, and facing vectors. A workflow depends on deciding whether a model is a character, prop, proxy mesh, control rig, or broken import. Do not judge animated 3D assets only from screenshots. Screenshots are review evidence, but they hide axis conventions, bone names, object scale, local transforms, parented meshes, material slots, and frame-by-frame contact state. First extract structured Blender state, then use viewport screenshots or renders to confirm what the facts imply. 1. Establish the clean scene and asset baseline before judging motion. 2. Extract structured facts from Blender using an exporter or Blender Python run inside Blender's own interpreter. 3. Sample the frames most likely to expose contact, orientation, scale, and retargeting errors. 4. Compare the measured facts against the user's expected pose, direction, ground plane, and render goal. 5. Return a concise report that separate

This is an excerpt. Refer to the complete source and its current requirements.