Commit Graph

2 Commits

Author SHA1 Message Date
type-two
d6af7b3ebe fix: FBX take name actually works (was still 'Armature|Scene' after the last attempt)
The previous fix renamed the baked ACTION, but Blender's FBX exporter builds the
AnimStack name from scene.name (io_scene_fbx/export_fbx_bin.py), so every clip
still exported the take 'Scene' -> imported back as 'Armature|Scene'. Verified
failing on wan_dig_t3.fbx, which was built AFTER that commit.

Now sets bpy.context.scene.name = name before export. Both stated acceptances pass:
  strings clips_out/wan_dig_t3.fbx | grep wan_dig_t3  -> 6 hits
  Blender import                                       -> 'Armature|wan_dig_t3'
Re-exported wan_walk_t1 + wan_dig_t3; takes are distinct, so they can no longer
collide in the 24-track female_game bank.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-25 21:40:45 +10:00
type-two
c918ac3dcd lane C+D: retarget + mocap CLI + docs; fix: FBX take carries the clip name (was Armature|Scene for every clip — bank collisions in take-addressed consumers)
First generated-footage clip proven through the full chain: Wan2.1 T2V (m3ultra, prompt-engineered to CAPTURE.md rules) -> ./mocap -> wan_walk_t1.fbx -> merge_anims bank (49 tracks). PROGRESS.md bug closed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 14:06:38 +10:00