Constraint with custom space not limiting transformation #111663

Open
opened 2023-08-29 17:46:53 +02:00 by Seifolio · 8 comments

System Information
Operating system: Windows 11
Graphics card: RTX 3060

Broken: Blender 3.6.2
Worked: Never

Affect transform conflict with custom space

According to documentation, Affect Transform option will limit manual rotation, but it doesn't with custom space. It works with local space.

Steps To Reproduce

Open file and rotate contrained bone. Check bone transformaton - it is not limited.

**System Information** Operating system: Windows 11 Graphics card: RTX 3060 Broken: Blender 3.6.2 Worked: Never Affect transform conflict with custom space According to documentation, Affect Transform option will limit manual rotation, but it doesn't with custom space. It works with local space. **Steps To Reproduce** Open [file](https://projects.blender.org/attachments/12bb976b-abb1-407e-a17e-ac54cf58e141) and rotate contrained bone. Check bone transformaton - it is not limited.
Seifolio added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-08-29 17:46:54 +02:00
Seifolio changed title from Affect transform Issue to Affect Transform Issue 2023-08-29 17:47:28 +02:00
Dependency cycle detected:
  OBArmature/Robo.Arm.MCH.001/POSE_IK_SOLVER() depends on
  OBArmature/Robo.Arm.IK.CTRL.001/BONE_DONE() via 'IK'
  OBArmature/Robo.Arm.IK.CTRL.001/BONE_READY() via 'Ready -> Done'
  OBArmature/Robo.Arm.IK.CTRL.001/BONE_CONSTRAINTS() via 'Constraints -> Ready'
  OBArmature/Robo.Arm.CTRL.001/BONE_DONE() via 'Copy Transforms'
  OBArmature/Robo.Arm.CTRL.001/BONE_READY() via 'Ready -> Done'
  OBArmature/Robo.Arm.CTRL.001/BONE_CONSTRAINTS() via 'Constraints -> Ready'
  OBArmature/Robo.Arm.MCH.003/BONE_DONE() via 'Limit Rotation'
  OBArmature/Robo.Arm.MCH.001/POSE_IK_SOLVER() via 'IK Solver Result'

Thanks for report. You file contains dependency cycle. So this can cause undefined behavior.
Can you fix this can confirm that bug is fixed too?

``` Dependency cycle detected: OBArmature/Robo.Arm.MCH.001/POSE_IK_SOLVER() depends on OBArmature/Robo.Arm.IK.CTRL.001/BONE_DONE() via 'IK' OBArmature/Robo.Arm.IK.CTRL.001/BONE_READY() via 'Ready -> Done' OBArmature/Robo.Arm.IK.CTRL.001/BONE_CONSTRAINTS() via 'Constraints -> Ready' OBArmature/Robo.Arm.CTRL.001/BONE_DONE() via 'Copy Transforms' OBArmature/Robo.Arm.CTRL.001/BONE_READY() via 'Ready -> Done' OBArmature/Robo.Arm.CTRL.001/BONE_CONSTRAINTS() via 'Constraints -> Ready' OBArmature/Robo.Arm.MCH.003/BONE_DONE() via 'Limit Rotation' OBArmature/Robo.Arm.MCH.001/POSE_IK_SOLVER() via 'IK Solver Result' ``` Thanks for report. You file contains dependency cycle. So this can cause undefined behavior. Can you fix this can confirm that bug is fixed too?
Author

Hello,
Thank you for the fast response. Here I made a simpler armature with two bones (Bone A) and (Bone B) no relationship between them.
you can rotate (Bone B) which has the Limit Rotation Constraint based on custom space of (Bone A) and (Affect Transform) is on. All is working good except (Affect Transform) you can find that the bone rotation exceeds the limit (not visually but in the transformation data)

Hello, Thank you for the fast response. Here I made a simpler armature with two bones (Bone A) and (Bone B) no relationship between them. you can rotate (Bone B) which has the Limit Rotation Constraint based on custom space of (Bone A) and (Affect Transform) is on. All is working good except (Affect Transform) you can find that the bone rotation exceeds the limit (not visually but in the transformation data)

This is original transform data. All you see are evaluated versions of objects in its transforms. It's like modifiers that make very detailed meshes. You can see them, but their original data will be different. So it's not a bug, just the way blender works.

This is original transform data. All you see are evaluated versions of objects in its transforms. It's like modifiers that make very detailed meshes. You can see them, but their original data will be different. So it's not a bug, just the way blender works.
Member

Thx reporting! Agree this is not a bug though, the original values are still there (just limited by the constraint), if you disable the constraint, those original values take affect.

So unless this is a misunderstanding (in which case feel free to comment again), will close this report.

Thx reporting! Agree this is not a bug though, the original values are still there (just limited by the constraint), if you disable the constraint, those original values take affect. So unless this is a misunderstanding (in which case feel free to comment again), will close this report.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-08-30 14:13:27 +02:00
Author

What I understand now is that (Affect Transform) doesn't work for custom space please tell me if I am wrong
Here another try with the local space:

(Image 1) with (Affect Transform) is on --> The original values didn't go beyond the limits
(Image 2) with (Affect Transform) is off --> The original values go beyond the limits

What I understand now is that (Affect Transform) doesn't work for custom space *please tell me if I am wrong* Here another try with the local space: (Image 1) with (Affect Transform) is on --> The original values didn't go beyond the limits (Image 2) with (Affect Transform) is off --> The original values go beyond the limits
563 KiB
570 KiB
Member

Will recheck later

Will recheck later
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2023-08-30 17:14:25 +02:00

Just from documentation, this seems like a bug, but looking at code it seems to be not implemented:

        /* Skip incompatible space-types. */
        if (!ELEM(con->ownspace, CONSTRAINT_SPACE_WORLD, CONSTRAINT_SPACE_LOCAL)) {
          continue;
        }

This is quite old piece of code, so not sure who could tell more information. In any case will confirm and let module decide whether this is undocumented known issue or bug.

Just from documentation, this seems like a bug, but looking at code it seems to be not implemented: ``` /* Skip incompatible space-types. */ if (!ELEM(con->ownspace, CONSTRAINT_SPACE_WORLD, CONSTRAINT_SPACE_LOCAL)) { continue; } ``` This is quite old piece of code, so not sure who could tell more information. In any case will confirm and let module decide whether this is undocumented known issue or bug.
Richard Antalik added
Status
Confirmed
Module
Animation & Rigging
and removed
Status
Needs Triage
labels 2023-09-01 03:37:14 +02:00
Richard Antalik changed title from Affect Transform Issue to Constraint with custom space not limiting transformation 2023-09-01 03:38:03 +02:00
Christoph Lendenfeld added
Type
Known Issue
and removed
Type
Report
labels 2023-10-10 11:09:31 +02:00

putting this as a known issue since I went through the code and custom space seems to be not implemented for affect transform

putting this as a known issue since I went through the code and custom space seems to be not implemented for affect transform
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
5 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#111663
No description provided.