FBX Exporter is Exporting un-keyframed Bones in Actions #33207

Closed
opened 2012-11-17 03:51:44 +01:00 by Austyn Larkin · 5 comments

%%%The FBX exporter is exporting information for un-keyframed bones. Say I only make keyframes in an action to move the mouth of a character. I then export the whole model with the animations. The resulting file will have all the keyframes for the "MoveMouth" action, but it will have single, "starting keyframes" for all other bones that weren't keyframed for the MoveMouth Action (feet, elbows, ect.) It gets these "starting keyframes" from previous actions in the action list. So, if above in the list I have the "Run" action, the "MoveMouth" animation will have the character frozen in the last frames of the Run action. The mouth still moves, but the rest of the character is stuck in the previous action's last frames.

This is only a problem when importing into Unity. I'm very certain this is a bug as I've tried multiple versions of blender (2.49b, 2.60) All that really needs to be fixed is the "taking keyframes from previous animations to fill the non-keyframed spots in the current action being exported." It should only be exporting the keyframes that were actually set by the user for that action, right? I've had this bug for almost a year now. I've tried editing the FbxExport script to try to fix it myself, but any edits I make break it for some reason. If you have any more questions or would like me to explain it further, feel free to drop me an email at (IMAUSTYN@me.com)

Mac OS: 10.6.8
Blender: 2.49b, 2.60 (Not installed at the same time, just the versions I've tested)

Blender is a great program and I'm hoping to get this fixed up so I won't have to switch software. (I really like Blender's controls) =)%%%

%%%The FBX exporter is exporting information for un-keyframed bones. Say I only make keyframes in an action to move the mouth of a character. I then export the whole model with the animations. The resulting file will have all the keyframes for the "MoveMouth" action, but it will have single, "starting keyframes" for all other bones that weren't keyframed for the MoveMouth Action (feet, elbows, ect.) It gets these "starting keyframes" from previous actions in the action list. So, if above in the list I have the "Run" action, the "MoveMouth" animation will have the character frozen in the last frames of the Run action. The mouth still moves, but the rest of the character is stuck in the previous action's last frames. This is only a problem when importing into Unity. I'm very certain this is a bug as I've tried multiple versions of blender (2.49b, 2.60) All that really needs to be fixed is the "taking keyframes from previous animations to fill the non-keyframed spots in the current action being exported." It should only be exporting the keyframes that were actually set by the user for that action, right? I've had this bug for almost a year now. I've tried editing the FbxExport script to try to fix it myself, but any edits I make break it for some reason. If you have any more questions or would like me to explain it further, feel free to drop me an email at (IMAUSTYN@me.com) Mac OS: 10.6.8 Blender: 2.49b, 2.60 (Not installed at the same time, just the versions I've tested) Blender is a great program and I'm hoping to get this fixed up so I won't have to switch software. (I really like Blender's controls) =)%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%Hi, the reason keyframes are written for all bones its that even if the bone isnt animated it may move for some other reason.

  • It may have constraints applied so other bones influence its motion or it could be driven too...

But its reasonable to detect a bone that doesnt move at all and not write any keyframes for it. assigning to myself.%%%

%%%Hi, the reason keyframes are written for all bones its that even if the bone isnt animated it may move for some other reason. - It may have constraints applied so other bones influence its motion or it could be driven too... But its reasonable to detect a bone that doesnt move at all and not write any keyframes for it. assigning to myself.%%%
Author

%%%Thanks so much!%%%

%%%Thanks so much!%%%

%%%Checked on adding this but its made more complicated that bones may not be in their rest state, currently having a keyframe at the start resolves this issure.

Moving to TODO:
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Import_Export#FBX%%%

%%%Checked on adding this but its made more complicated that bones may not be in their rest state, currently having a keyframe at the start resolves this issure. Moving to TODO: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Import_Export#FBX%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 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#33207
No description provided.