Page MenuHome

Right Mouse Confirms instead of Cancels after IK target added
Closed, InvalidPublic

Description

System Information
Operating system and graphics card

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)

Short description of error
Adding a target to targetless IK which is another targetless IK changes RIGHT-Mouse to CONFIRM instead of CANCEL

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

  1. Extrude start cube face twice in one axis.
  2. Add a Bone to one segment of extruded cube.
  3. Extrude bone twice, one for each segment.
  4. Parent cube to armature
  1. Add targetless IK to Bone.002, Length 2
  2. Add targetless IK to Bone.001, Length 1

    At this point, right clicking a bone in Pose Mode (default setup) and pressing G moves the bone. A further right click cancels the selection. Normal.
  1. Select Bone.001 and in Bone Constraints add a Target to the IK to be Bone.002
  1. Select Bone.002, Press G to move bone.

9) Right Click

This Should Cancel the move but now seems to Confirm it instead.

Details

Type
Bug

Event Timeline

John (meat5000) added a project: BF Blender.
John (meat5000) set Type to Bug.
John (meat5000) added a subscriber: John (meat5000).
John (meat5000) created this task.
John (meat5000) raised the priority of this task from to Needs Triage by Developer.

Blender 2.7
Win 7 64 Ultimate

AMD 8350
Gigabyte 990FXA-UD3
16GB Corsair 1866
Radeon 5770

Added example with the problem based on the steps:


Continue from step 8.

Using your example I noticed that Bone.002 returns to its previous rotation but Bone.001 gets confirmed and holds its new position.

This also happens as stated in Build 2.69 as well as 2.7

Bastien Montagne (mont29) triaged this task as Confirmed, Medium priority.

@koil (koilz), thanks for the file! :)

Bastien Montagne (mont29) claimed this task.

Analyzing further this case, it just can’t work… IK are not meant to work this way (actually, using the next bone in a connected chain as target has absolutely no sense), you are creating some kind of nightmare with cyclic dependencies…