Copy Rotation with Offset fails with hierarchies #28844

Closed
opened 2011-10-08 04:23:55 +02:00 by bassam kurdali · 7 comments
Member

%%%I have two bone chains:

base_parent/base_child (which is untransformed)

parent/child (which is)

parent has a copy rotation in local space with offset to base_parent
child has a copy roation in local space with offset to base_child

I rotate parent.

Now when I rotate child, I get weird rotations/crazy space (try rotating around local Y axis). Given that the local space transformation of the base chain is zero, I'd expect normal behaviour in this case, which leads me to suspect an error/bug.

uname: 2.6.35-30-generic #59-Ubuntu SMP Tue Aug 30 19:00:03 UTC 2011 x86_64 GNU/Linux
affects: revision 40847
hardware: intel cpu/ nvidia gpu%%%

%%%I have two bone chains: base_parent/base_child (which is untransformed) parent/child (which is) parent has a copy rotation in local space with offset to base_parent child has a copy roation in local space with offset to base_child I rotate parent. Now when I rotate child, I get weird rotations/crazy space (try rotating around local Y axis). Given that the local space transformation of the base chain is zero, I'd expect normal behaviour in this case, which leads me to suspect an error/bug. uname: 2.6.35-30-generic #59-Ubuntu SMP Tue Aug 30 19:00:03 UTC 2011 x86_64 GNU/Linux affects: revision 40847 hardware: intel cpu/ nvidia gpu%%%
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

%%%I turns out that I over complicated: the parent -> base_parent constraint (and the bone base_parent) is not needed to demonstrate the bug. All that is needed that child have a transformed parent, and that child have a local->local copy rotation with offset for the chaos to ensue.
%%%

%%%I turns out that I over complicated: the parent -> base_parent constraint (and the bone base_parent) is not needed to demonstrate the bug. All that is needed that child have a transformed parent, and that child have a local->local copy rotation with offset for the chaos to ensue. %%%
Author
Member

%%%Final simplification, and new update:
The problem is unrelated to hierarchies. once you have transformed the bone, it's in crazy space.
check the file crazyspace.blend, now with just two bones.
%%%

%%%Final simplification, and new update: The problem is unrelated to hierarchies. once you have transformed the bone, it's in crazy space. check the file crazyspace.blend, now with just two bones. %%%

%%%Any updates here? %%%

%%%Any updates here? %%%
Member

%%%This needs a fix in transform code, to calculate the correct inverse method to rotate the bone.

Now if that was easy... but the standard inverse doesnt work because the constraint in turn screws the inverse up. That is caused by the "offset" option.
A math genius might be able to solve it, but this so specific for how this constraint works, we wouldn't get benefit for it really. All constraints have too many options...

Choice: remove "offset" or stick to crazyspace :)%%%

%%%This needs a fix in transform code, to calculate the correct inverse method to rotate the bone. Now if that was easy... but the standard inverse doesnt work because the constraint in turn screws the inverse up. That is caused by the "offset" option. A math genius might be able to solve it, but this so specific for how this constraint works, we wouldn't get benefit for it really. All constraints have too many options... Choice: remove "offset" or stick to crazyspace :)%%%
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Author
Member

%%%an idea for the future:
replace complex options in constraints with either a transform/constraint stack or nodes:

  • simplify transform options
  • simplify constraints
  • allow adding transform nodes 'on top' of constraints in order, thus no crazy space and real offsetting.

this should be fixable long term (animation master and max didn't have these issues afair)%%%

%%%an idea for the future: replace complex options in constraints with either a transform/constraint stack or nodes: - simplify transform options - simplify constraints - allow adding transform nodes 'on top' of constraints in order, thus no crazy space and real offsetting. this should be fixable long term (animation master and max didn't have these issues afair)%%%
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
3 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#28844
No description provided.