BVH armature import error #45621
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#45621
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?
Importing the attached bvh file into blender creates a armature with the root of each bone moved to the center of the armature. I am able to play and edit this bvh file within XSI, 3ds max, Endorphin and bvhacker.
This is what it should look like: bvhacker
Here is what it looks like in blender: [octahedral ]] [ http:*i.imgur.com/YWZLTmM.jpg | stick
animation.bvh
Changed status to: 'Open'
Added subscriber: @bevels
System Information
Windows 7 SP1 (x64)
Blender Version
Broken: 2.75a c27589e
Exact steps for others to reproduce the error
Import the attached file as an armature (default settings)
Added subscriber: @Blendify
Added subscribers: @ideasman42, @Sergey
@ideasman42, seems this one is for you.
Yep, seems were applying absolute locations when we shouldn't, however in most BVH files only the root bones translate so this went for some years unnoticed.
Added subscriber: @duststorm
This is related to the issue #44690 I reported a while back.
I attached a patch in that issue, could you verify that this solves your issue?
Added subscriber: @BrendonMurphy
was there a resolution here?
Changed status from 'Open' to: 'Archived'
Archived, duplicate/sub issue of #44690