Copy Transforms constraint jumps when changing influence #34532

Closed
opened 2013-03-04 23:07:48 +01:00 by Nathan Vegdahl · 10 comments
Member

%%%OS: Xubuntu 12.10
Blender version: SVN r55030

When a bone is sheared, the Copy Transforms constraint causes it to suddenly jump when blending it's influence to/from 0.0. Expected is a smooth transition between 0.0 and 1.0 influence.

Attached is a file demonstrating the issue. Simply drag the influence slider, and notice it's behavior especially near 0.0.%%%

%%%OS: Xubuntu 12.10 Blender version: SVN r55030 When a bone is sheared, the Copy Transforms constraint causes it to suddenly jump when blending it's influence to/from 0.0. Expected is a smooth transition between 0.0 and 1.0 influence. Attached is a file demonstrating the issue. Simply drag the influence slider, and notice it's behavior especially near 0.0.%%%
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

%%%Update:
The same "jumping" behavior occurs with Copy Location, Copy Rotation, and Copy Scale as well. So it seems the problem is likely in some code that's shared among those constraints.%%%

%%%Update: The same "jumping" behavior occurs with Copy Location, Copy Rotation, and Copy Scale as well. So it seems the problem is likely in some code that's shared among those constraints.%%%
Member

%%%The copy transform constraint has no blending option (in the code). In theory you could simply mix two 4x4 matrices, but that doesn't always give the desired result, especially not when rotations are involved. Decomposing the matrix would also not work (shear gets lost).

I will ask Joshua what he'd suggest to do. A linear interpolated matrix (with its limitations) is probably what Nathan would accept :)%%%

%%%The copy transform constraint has no blending option (in the code). In theory you could simply mix two 4x4 matrices, but that doesn't always give the desired result, especially not when rotations are involved. Decomposing the matrix would also not work (shear gets lost). I will ask Joshua what he'd suggest to do. A linear interpolated matrix (with its limitations) is probably what Nathan would accept :)%%%
Author
Member

%%%Yeah, it's not necessarily a trivial problem, I'm aware.

Note, however, that as per my first comment here, this problem is showing up for the Copy Location, Copy Rotation, and Copy Scale constraints as well. In the example file, just substitute any of those constraints for the Copy Transforms constraint, and the same problem appears. It basically seems to be a problem with constraints operating on bones (and objects? haven't checked) that have been sheared by parent transforms.

Ideally the shear could somehow be "extracted" and separately interpolated, and then re-inserted afterwards, such that the other interpolations happened as if they were "inside" the space of the shear. That's probably not trivial to do, and may be one of those "multiple possible solutions" things, but it would sure be useful behavior.%%%

%%%Yeah, it's not necessarily a trivial problem, I'm aware. Note, however, that as per my first comment here, this problem is showing up for the Copy Location, Copy Rotation, and Copy Scale constraints as well. In the example file, just substitute any of those constraints for the Copy Transforms constraint, and the same problem appears. It basically seems to be a problem with constraints operating on bones (and objects? haven't checked) that have been sheared by parent transforms. Ideally the shear could somehow be "extracted" and separately interpolated, and then re-inserted afterwards, such that the other interpolations happened as if they were "inside" the space of the shear. That's probably not trivial to do, and may be one of those "multiple possible solutions" things, but it would sure be useful behavior.%%%
Author
Member

%%%Hmm, here's a thought:
If you decompose and then recompose the matrix, you lose the shear, yes? So couldn't you then use the inverse of the decomposed/recomposed matrix to extract the shear from the original? Not sure if that would give the desired result, but I imagine it would at least be smooth. Something to try, perhaps.%%%

%%%Hmm, here's a thought: If you decompose and then recompose the matrix, you lose the shear, yes? So couldn't you then use the inverse of the decomposed/recomposed matrix to extract the shear from the original? Not sure if that would give the desired result, but I imagine it would at least be smooth. Something to try, perhaps.%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Added subscriber: @Sergey

Added subscriber: @Sergey

it was quite a while already, moving to TODO now http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Animation#Constraints

Pretty known limitation of constraints which are heavily used to decompose matricies..

it was quite a while already, moving to TODO now http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Animation#Constraints Pretty known limitation of constraints which are heavily used to decompose matricies..

Added subscriber: @Josephbburg

Added subscriber: @Josephbburg

The file doesn't seem to have the bug in Blender 2.91.

The file doesn't seem to have the bug in Blender 2.91.
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
4 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#34532
No description provided.