BVH Exporter mishandles non-origin root bone #44690
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#44690
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?
BVHProblem.zip
Blender seems to improperly EXPORT BVH. Attached is .zip a round trip import-export pair of files that demonstrate that Blender does not return the same file it imports.
The image shows the improper consequence of import/export round trip in Blender.
Blender Exporter seems to treat frames as absolute positions not as relative to the root. It improperly displaces the root {These references all agree that the position frame channels are translations, and not absolute positions:
http://www.dcs.shef.ac.uk/intranet/research/public/resmes/CS0111.pdf
Refer to equation 3.2 on page 8 and the description next to it.
"Therefore,Tx,Ty and Tz represent the summation of abone’s base position and frame translation data."
http://research.cs.wisc.edu/graphics/Courses/cs-838-1999/Jeff/BVH.html
"The rot filesation data comes from the motion section. For the root object, the translation data will be the sum of the offset data and the translation data from the motion section"
OS Name Microsoft Windows 8.1 Pro
Version 6.3.9600 Build 9600
Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2394 Mhz, 4 Core(s), 8 Logical Processor(s)
Adapter Type GeForce GTX 780M, NVIDIA compatible
Adapter Description NVIDIA GeForce GTX 780M
Adapter RAM (1,048,576) bytes
Installed Drivers nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver Version 9.18.13.5012
Changed status to: 'Open'
Added subscriber: @RobertBaer
Added subscriber: @mont29
Code seems to be doing what's expected here...(re movement and all).
However, it seems to apply some kind of global rotation of armature somehow…
Added subscriber: @duststorm
The example file does not seem to illustrate this issue. What happens in the example file is that it rotates the entire skeleton to convert from Z up to Y up coordinates (or the other way around).
The issue I was seeing, is that BVH export copied the offset of the root joint in the X/Y/Zposition channels of the MOTION, even if the animation track in blender had no translation on that bone, only rotations.
Now, I have only tried this with Blender 2.72b so I'm not sure whether this is fixed in the meantime (which is why I outsourced investigation of this issue), but my observations are described here:
http://bugtracker.makehuman.org/issues/758#note-6
Recreating this bug should be fairly straightforward:
Create a new armature in Blender, add one bone, place this bone's head at a different position than the origin. Apply a pose to this armature containing only rotations, no translations. Export to BVH.
When observing the BVH file, the root joint will contain translation channels, and they will be non-zero. In fact they will contain the same coordinates as the offset of the root joint. This is contradictory to the literature pointed to by Rob. It also seems to contradict a variety of existing BVH implementations, for example BVHacker.
Perhaps this image will further clarify the issue.
I'm attaching two simple blend files for testing the patch.
The first contains only one bone, this is an edge case (only one bone, the root bone)
bvhtestA.blend
The second has two bones
bvhtestB.blend
The root bone doesn't have it's head at the origin, its head is at Z=0.35, its tail at Z=1.35, thus length == 1
The child bone (in the second file) has its head at Z=1.35 and its tail at Z=2, X=0.5
The things to verify are:
Added subscriber: @BrendonMurphy
Any resolution here?
Removed subscriber: @ideasman42
Changed status from 'Open' to: 'Archived'
no activity, closing as archived