Incorrect mesh deformation behavior when using deform bones from multiple armatures #44081

Closed
opened 2015-03-21 23:32:20 +01:00 by pjmendes · 4 comments

System Information
Windows 7 64bit, AMD Radeon 5770

Blender Version
Broken: 2.74 rc2 1f547c1
Worked: never

For a mesh using multiple armatures (at least two) with bones that deform it, and weight painted to bones in both armatures, when the bones are animated the deformation behaves incorrectly/unexpectedly.

Additionally, during the weight paint process, the vertices don't interpolate between the bones being painted (as one paints using intermediate values for the weights, such as 0.5 for each bone) as it does with bones in a single armature, it either maps 100% to the first or second bone.

(The vertex groups/weights are correctly created by blender when weight painting, and user care was taken to not have bone name collision, meaning there are no bones with the same name between armatures).

Exact steps for others to reproduce the error
multiple_armatures_weight_bug.blend
In attached file, two armatures were added as modifiers of the Cube mesh. Each armature has a single bone. "Armature" has the left bone ("Bone"), "Armature.001" has the right bone ("Bone2").

"Bone" is 100% weighted to the leftmost vertices of the cube, 50% weighted to the vertices on the middle, and 0% to verts on the right.

"Bone2" is 50% weighted to the middle vertices and 100% to the right.

Moving "Bone", I expected the Cube's left vertices to move 100% with it and the middle ones to move 50%, but it moves all the vertices by 100%, ignoring the 50% weight to the second armature.

Moving "Bone2", this behavior is similar, the weight interpolation is ignored.

Also, during weight painting, as mentioned above, the vertices don't correctly update their visual coordinate between bones to indicate the weight interpolation between them (by this, I mean that, if weight painting in pose mode, and posing the bones, a vertex 50% weighted to each bone should "jump" to in between them, and this does not happen. The vertices will "jump" but only when the weight reaches 0 or 100% for a bone).

**System Information** Windows 7 64bit, AMD Radeon 5770 **Blender Version** Broken: 2.74 rc2 1f547c1 Worked: never For a mesh using multiple armatures (at least two) with bones that deform it, and weight painted to bones in both armatures, when the bones are animated the deformation behaves incorrectly/unexpectedly. Additionally, during the weight paint process, the vertices don't interpolate between the bones being painted (as one paints using intermediate values for the weights, such as 0.5 for each bone) as it does with bones in a single armature, it either maps 100% to the first or second bone. (The vertex groups/weights are correctly created by blender when weight painting, and user care was taken to not have bone name collision, meaning there are no bones with the same name between armatures). **Exact steps for others to reproduce the error** [multiple_armatures_weight_bug.blend](https://archive.blender.org/developer/F153863/multiple_armatures_weight_bug.blend) In attached file, two armatures were added as modifiers of the Cube mesh. Each armature has a single bone. "Armature" has the left bone ("Bone"), "Armature.001" has the right bone ("Bone2"). "Bone" is 100% weighted to the leftmost vertices of the cube, 50% weighted to the vertices on the middle, and 0% to verts on the right. "Bone2" is 50% weighted to the middle vertices and 100% to the right. Moving "Bone", I expected the Cube's left vertices to move 100% with it and the middle ones to move 50%, but it moves all the vertices by 100%, ignoring the 50% weight to the second armature. Moving "Bone2", this behavior is similar, the weight interpolation is ignored. Also, during weight painting, as mentioned above, the vertices don't correctly update their visual coordinate between bones to indicate the weight interpolation between them (by this, I mean that, if weight painting in pose mode, and posing the bones, a vertex 50% weighted to each bone should "jump" to in between them, and this does not happen. The vertices will "jump" but only when the weight reaches 0 or 100% for a bone).
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @pjmendes

Added subscriber: @pjmendes

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Campbell Barton self-assigned this 2015-03-23 14:27:55 +01:00

Afraid this is working as intended, for each vertex the weights are normalized and distributed between bones - for that modifier only. Rather then being shared across multiple armatures.

While there are cases where you might want to use multiple armature modifiers, limitations like this make it less useful (YMMV).

closing.

Afraid this is working as intended, for each vertex the weights are normalized and distributed between bones - for that modifier only. Rather then being shared across multiple armatures. While there are cases where you might want to use multiple armature modifiers, limitations like this make it less useful (YMMV). closing.
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
Interest: X11
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#44081
No description provided.