Revision as of 14:34, 19 April 2018 by Frankiezafe (Talk | contribs)

Notes about computation of inverse kinematics^{[1]}

At this moment, the research is focusing on solving a 2 bones system, the leg in this case, but it would be applicable on the arms or any other part of a skeleton having at least 2 parents.

The main issue seems to be the computation of the knee position. All distances are easily computed:

- upper leg (red) keeps its length
- leg (yellow) keeps its length also
- distance between the target and the origin of the upper leg can be easily computed in world space.

Rendering the position of the knee is crucial to compute the rotation to apply on the upper leg. Once correct, the rotation of the leg will be simple to render, as it is the rotation from the current direction to the [knee - target] direction.

A little warning: the graphic here above is in 2d. In a 3d world, the position of the knee is a circle on a sphere: any point being at the right distance of the target point **and** the upperleg origin will be a valid candidate! The circle of possibilities is the intersection of 2 spheres having a radius equal to bones length.

The radius of the cyan circle can be solved by using this equation^{[2]}:

a = 1/(2d)sqrt(4d^2R^2-(d^2-r^2+R^2)^2)

A little screenshot for better readability:

Once computed, we will need to pick a point on this circle by using an arbitrary direction:

- front axis of the leg or
- knee - target difference.

- Animation Bootcamp: An Indie Approach to Procedural Animation - a GDC talk about character animation in a computation effective way.

- ↑ Inverse kinematics sur wikipedia
- ↑ Sphere-Sphere Intersection

**online identity** ∋ [ **social** ∋ [mastodon♥, twitter®, ~~facebook®~~, diaspora, ~~linkedin®~~]
∥ **repos** ∋ [github®, gitlab♥, bitbucket®, sourceforge] ∥ **media** ∋ [itch.io®, vimeo®, peertube♥, twitch.tv®, tumblr®] ∥ **communities** ∋ [godotengine♥, openprocessing, stackoverflow, threejs]]