Page MenuHome

Very Glitchy Armature
Open, Waiting for Developer to ReproducePublic


System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13492 Core Profile Context 22.19.677.257

Blender Version
Broken: version: 2.80 (sub 72), branch: blender2.7, commit date: 2019-05-28 21:07, hash: rB9bae9b634ec6
Worked: (optional)

Short description of error
[IK bones on custom character rig acting really buggy. Been happening for the past few versions.]

Exact steps for others to reproduce the error
[In edit mode make a straight bone for the leg or arm of a character as if in a T pose. Subdivide once the leg and arm. On the ends of the leg and the arm, make controller bones and disconnect them from the parent bone but keep them parented. Create a poll bone from one of the bones from the arm and legs. Make sure it has no parents and is disconnected from the armature but still apart of it. Bring it along the X axis to sit a little in front of the armature. After that go to the joint were original arm bones were subdivided. Click on that joint and move it back along the X-Axis a very small amount so when the IK kicks in it will bend in the manner in which arms bend. Next, In pose mode go and click on the arm controller bone and then shift-click on the parented bone next to it. Hit ctrl. + shift + C to bring up the constraints menu for the bones. Click on IK. Click on the yellow colored bone and go to the constraints tab. Some of the information should already be filled out in the constraint. Put in the target as the armature itself and the appropriate poll for the arms. Set chair length to 2. Do the same steps to make the leg IK bound. Now move the arm controller along the X-Axis and the leg controllers along the Z axis. They should be severely glitching out whenever moved. I have also gotten results of a helicopter motion with arms, not the legs. The problem seems to be limited to how the controllers work with the armature or IK settings.]
[Based on the default startup or an attached .blend file (as simple as possible)]



Event Timeline

Sebastian Parborg (zeddb) triaged this task as Waiting for Developer to Reproduce priority.