Blender FBX Export/Import Bone detachment #94018
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#94018
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?
System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77
Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-11-01 19:48, hash:
blender/blender@75f5edcaf3
Worked: (newest version of Blender that worked as expected)
Short description of error
Problem since forever in blender - importing fbx make it bones detached that prevents from use any sort of IK. Even if file was created in blender, fully rigged with controls and working IK, after exporting it, and importing in the same blend file whole rigg is imported wrong and not connected.
Exact steps for others to reproduce the error
Make model, make armature, rig it, make IK, export it to fbx, import it and thats all
Cant put blend file because nda but its simple to do and it never worked.
Added subscriber: @DrPhil
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs User Info'
I can not replicate the issue on a simple file. So can you attach a minimal file that reproduces the issue?
Does the issue happen only when there is an IK constraint? Is the offset in the hand the issue you are talking about?
After import FBX into Blender I believe importer doesn't load data about children-parent connection. There is force connection that we can select but it work more like a guess than real data import. Simply when we do armature we describe what is parent and what is child and how IK should behave. If we import same file into blender its not importing this data.
Right. I don't think Blender supports constraints like IK for FBX regardless, so this is more of a limitation.
Is the issue about such limitations or something more?
This one is major that don't allow many users to use 3rd party models right away without spending additional time to reconnect and repair armature. Another one is that sizes and orientation of the bones are not correctly imported. I created topic about it here: https://developer.blender.org/T72386
Changed status from 'Needs User Info' to: 'Needs Triage'
Changed status from 'Needs Triage' to: 'Needs User Info'
There is a long list of known issues and limitations for FBX IO #68575, so it is unlikely that new additions like IK constraints will be added soon.
If there is an issue that is unrelated to constraints, we require a minimal blend file to replicate the issue and investigate it. Can you do that?
If not, we will just consider this to be a to-do and will be handled outside of this bug tracker.
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.