Complex armature with bone constraints - setting PoseBone matrix_basis may not influence another bone's matrix as expected as not calculated yet (possible bug, definite FBX export bug!) #53202
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#53202
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Not sure if this is a bug - the only way to get the correct PoseBone's matrix after setting another PoseBone's matrix_basis (which in some way influences the former bone) is to call scene.update() after applying matrix_basis to one or many PoseBones.
At the very least, this should be noted in the Gotchas section on docs.blender.
Taking this into account - I have spotted a definite bug in the FBX export addon.
Looking through the FBX export addon file export_fbx_bin.py, I noticed the coder had tripped up with this same misconception.
After both instances of:
scene.update() needs to be called immediately afterwards.
Assuming bake_anim_force_startend_keying = False and there are multiple actions being exported, the last frame of the previous action will influence the following action if one of the keying bones was not keyframed on the first frame.
This is very noticable when exporting a rigify rig for example, and creates bad exports.
Please see attached blend file for simple example (with code).
bugfbxexportpose2.blend
Changed status to: 'Open'
Added subscriber: @hedgehog90-3
Added subscriber: @mont29
Having to call scene.update in such cases is expected (you have same issues when e.g. manipulating meshes from bpy API, if you need actual resulting data of those manipulations, you'll have to enforce an update yourself, as the one triggered by regular scene refreshing from UI will likely not happen soon enough).
So this totally sounds like an FBX exporter bug, thanks for reporting, will check asap.
This issue was referenced by
4e84d14771
This issue was referenced by
0b286650b3
Changed status from 'Open' to: 'Resolved'