IK constraints that are disabled or have influence set to zero, result in jerky movement of the bones until the IK constraint or target are deleted. #100594
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#100594
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?
System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96
Blender Version
Broken: version: 3.2.2 to 3.4 alpha, branch: master, commit date: 2022-08-02 18:15, hash:
bcfdb14560
Worked: not sure.
Please note there are no dependancy issues as all constraints are turned off. I've also updated the blend file so that there are no dependency issues even when the constraints are turned on.
boney bug.blend
blender_debug_output.txt
2022-08-23 20-55-41.mp4
Added subscriber: @3di
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Archived'
The attached file has dependency cycles:
Except for cases of fake/avoidable dependency cycle, undefined behavior of rig when it has dependency cycle are not considered bug.
You'd need to find a way to rig your model without introducing such cycles.
Hi @mano-wii , that's the point, there are no dependancy cycles, all constraints are disabled.
Added subscriber: @Germano
@mano-wii could you re-open please?
Changed status from 'Archived' to: 'Needs Triage'
Added subscriber: @ArtisticBee
Removed subscriber: @ArtisticBee
Changed status from 'Needs Triage' to: 'Confirmed'
I'm not sure why dependency cycles are maintained even with constraints disabled.
Maybe the dependency graph should be recreated when changing the enabled/disabled state of a constraint?
But in fact, that trembling does not seem to be expected in this case.
Added subscriber: @BClark
While the cycle comes from having the mesh that is a child of the bone be the target for the copy rotations constraint that is on the bone that is the parent of the mesh, you would expect that to happen if the constraints were visible/on/influence active etc. It seems like a bug to me that they are still getting called/calculating in the graph even if they are being told to do nothing, there shouldn't be a cycle because they wouldn't be called because they have zero visual impact on the final frame transform.
@BClark Hi Brad, did you download the new version of the file? There aren't any dependencies any more. The target is now a mesh not controlled by the same bone, this removed all of the dependencies from the log for me (flickering remained), although it did create a new one on the first bone for some reason which was strange.
I know it doesn't make any difference to it being a bug that disabled constraints are still calculated, but perhaps indicates that an additional bug is occurring related to the the order of constraints in the stack not being adhered to? For example if the bone is being aligned based on a non-child object prior to the IK being calculated (as is the case here based on the stack order), then that shouldn't generate a dependency. I could understand a bit of flicker on the next frame when the first element of the stack is executed, but only if the IK locking and copy rotation constraints weren't producing the same result.
Added subscriber: @ArtisticBee
Added subscriber: @michael-123
Hi @michael-123 campbell (3di) .
I send you two tutorials with basic movement in one hand is as you have done.
It may be that in the model you designed the parent and separately together it is a bone that is missing its choice and not necessarily it is a mistake of the program, that is, must be a small tip of the finger so small that it does not appear or you can see at fist only if you zoom in.
As a 3d modeler it has happened to me before with same projects.
Try step by step the video instructions and I hope it helps.
If it does not work then it will be reported as a bug.
I will download the file and do a test on the problem that exists and if there is a result I will let you know.
It shows that there is no smooth movement in the hand.
Keep trying and do not be discouraged, a little every day you will find the solution, it's a very nice work.
https://www.youtube.com/watch?v=ZmiZ6VkSJBE
https://www.youtube.com/watch?v=MvmXvah1bss
@ArtisticBee thanks, I've been doing it for 30 years, so I have a pretty good grasp of it hopefully :) It's already confirmed as a bug looking at the report.
I didn't get the latest file but yes I hope it helps track down some bugs, thank you!
Removed subscriber: @ArtisticBee
this seems to have been fixed with #88752: Setting an overlapping IK constraint to zero influence/disabled gives weird behavior
cannot reproduce in 4.0 anymore