FBX setting "bake_anim_use_nla_strips": True, fails to export unique animations to each take #48631

Closed
opened 2016-06-10 10:56:51 +02:00 by Frankie Hobbins · 6 comments

System Information
win 10 960

Blender Version
Broken: 2.77a abf6f08

Short description of error
BIN7400 FBX setting "bake_anim_use_nla_strips": True, fails to export unique animations to each take

Exact steps for others to reproduce the error

When using the export settings "bake_anim_use_nla_strips": True, with "bake_anim_use_all_actions": False, to selectively export actions animations to fbx the resultant fbx has the correct action names for each take but all contain the same animation.

I have attached blend file with a template to export, you just need to fill in the exportpath.

You will see the resulting fbx has the animation data for "up" when you select the down or jiggle animations.

To fix I believe you need to change current the action to match the strip name as it loops though. I am no programmer but something like works to replace the around line 2010 in export_fbx_bin

      for strip in strips:
          strip.mute = False
        #addition begins
          for a in bpy.data.actions:
              if a.name == strip.name:
                  bpy.context.object.animation_data.action = a
        #addition ends
          add_anim(animations, animated,
                   fbx_animations_do(scene_data, strip, strip.frame_start, strip.frame_end, True, force_keep=True))
          strip.mute = True

I have attached the blend file, fbx how it currently exports and the fbx exported with the change above

test.blend

test.fbx

test_fixed.fbx

**System Information** win 10 960 **Blender Version** Broken: 2.77a abf6f08 **Short description of error** BIN7400 FBX setting "bake_anim_use_nla_strips": True, fails to export unique animations to each take **Exact steps for others to reproduce the error** When using the export settings "bake_anim_use_nla_strips": True, with "bake_anim_use_all_actions": False, to selectively export actions animations to fbx the resultant fbx has the correct action names for each take but all contain the same animation. I have attached blend file with a template to export, you just need to fill in the exportpath. You will see the resulting fbx has the animation data for "up" when you select the down or jiggle animations. To fix I believe you need to change current the action to match the strip name as it loops though. I am no programmer but something like works to replace the around line 2010 in export_fbx_bin ``` for strip in strips: strip.mute = False ``` #addition begins ``` for a in bpy.data.actions: if a.name == strip.name: bpy.context.object.animation_data.action = a ``` #addition ends ``` add_anim(animations, animated, fbx_animations_do(scene_data, strip, strip.frame_start, strip.frame_end, True, force_keep=True)) strip.mute = True ``` I have attached the blend file, fbx how it currently exports and the fbx exported with the change above [test.blend](https://archive.blender.org/developer/F316671/test.blend) [test.fbx](https://archive.blender.org/developer/F316672/test.fbx) [test_fixed.fbx](https://archive.blender.org/developer/F316670/test_fixed.fbx)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @FrankieHobbins

Added subscriber: @FrankieHobbins

Added subscriber: @mont29

Added subscriber: @mont29
Bastien Montagne self-assigned this 2016-06-10 15:49:17 +02:00

Problem comes from the new behavior of NLA editor, now if an object has an action assigned, it overwrites any action set in NLA's strips (materialized in the 'virtual' top strip of the editor). Will fix.

Problem comes from the new behavior of NLA editor, now if an object has an action assigned, it overwrites any action set in NLA's strips (materialized in the 'virtual' top strip of the editor). Will fix.

This issue was referenced by c4a79435e4

This issue was referenced by c4a79435e45610d50dadfacf2ed2c09ce595f70f

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#48631
No description provided.