How to Record an Orangutan Animation Where Eyes Become Nostrils and Leaves Become a Moustache

Record this animation as two linked transformations: the orangutan’s eyes become nostrils, and its mouth-held leaves become a moustache. Use annotated drawings to preserve those correspondences without filling in unspecified movement.

The task is to make a visual record that another reader can follow: what is present initially, what each feature becomes, and which details of the change remain unspecified. A compact storyboard with explicit feature labels serves that task better than a polished drawing that quietly supplies extra actions.

The method below combines storyboard annotation, endpoint comparison and optional animation tools. The references explain those recording concepts; the orangutan scene itself comes from the supplied description.

What exactly needs to remain connected?

Begin with a literal action sentence: “An orangutan’s eyes become nostrils, while the leaves held in its mouth become a moustache.” Keep this sentence beside the drawings as the controlling description. Both starting materials and both resulting features matter.

The first correspondence is eyes to nostrils. A record showing eyes alongside newly added nostrils would describe an addition rather than the stated transformation. Make the connection explicit with a label attached to the changing feature group.

The second correspondence begins with leaves held in the mouth. Recording only “leaves become a moustache” loses their starting relationship to the orangutan. Recording only a moustache at the end loses the fact that the mouthful of leaves supplies it. Preserve both parts in the caption.

Use a short correspondence list before drawing:

• Starting feature: eyes. Resulting feature: nostrils.

• Starting material and placement: leaves held in the mouth. Resulting feature: moustache.

• Unspecified details: exact positions, contours, colours, duration, intermediate shapes and relative timing of the two changes.

These unknowns affect how faithfully the sequence can be recorded. The description establishes two transformations, but it does not establish whether they happen simultaneously, overlap or occur one after the other. Place them within the same scene without assigning an unsupported order.

How can a storyboard preserve the change without inventing frames?

Use a pair of endpoint studies accompanied by a transformation note. These drawings represent the stated starting and resulting conditions; they do not claim to reproduce particular frames from an existing animation. Label them “starting condition” and “resulting condition” rather than assigning frame numbers.

This approach draws on the storyboard’s combination of drawings and written directions. Krita’s official manual describes storyboards as drawings accompanied by contextual text, including action descriptions and production details. That combination lets the image show a condition while the caption explains the relationship between conditions. Krita Manual: Storyboard Docker (https://docs.krita.org/en/reference_manual/dockers/storyboard_docker.html)

For the starting study, identify the subject as an orangutan and mark the eyes and mouth-held leaves clearly enough to attach labels. Avoid elaborating the surrounding scene. No background, viewpoint, expression or lighting arrangement has been supplied.

For the resulting study, label the features produced by the two changes. The important information is their origin: “nostrils, transformed from the eyes” and “moustache, transformed from the mouth-held leaves.” Keep these labels outside the drawing so they cannot be mistaken for objects within the scene.

An illustrative drawing choice would be to repeat a simple head outline in both studies so the feature groups are easy to compare. This is a layout choice for the record, not evidence that the animation uses a fixed viewpoint or unchanged outline. State that distinction in the drawing notes.

Between the studies, write: “Eyes become nostrils; mouth-held leaves become a moustache. Intermediate appearance and relative timing are unspecified.” This records the complete supplied change sequence without inserting a halfway state.

A practical order of work is:

1. Write the literal action sentence.

2. Draw and label the starting condition.

3. Draw and label the resulting condition.

4. Connect each starting feature group to its named result with an annotation outside the scene.

5. Add one note identifying the details the description does not establish.

How should you track position, shape and material?

Treat position, contour and material as separate recording questions. “Becomes” establishes correspondence, but it does not by itself say that a shape moves, shrinks, rotates or changes colour. Those would require additional visual information.

For the eyes-to-nostrils change, record the group-level correspondence first. The description does not specify which individual eye maps to which individual nostril. If the drawing needs reference marks, use them to identify the group rather than creating an unsupported left-to-right mapping.

Likewise, avoid drawing a downward path simply because a conventional arrangement suggests one. A path would assert motion through space. If no path is supplied, a written connection between the endpoint labels preserves the transformation more accurately.

For the leaves-to-moustache change, keep the starting material visible in the starting study and preserve its mouth-held placement. In the result, the caption should identify the moustache as the outcome of those leaves. The description does not establish whether leaf edges, stems or texture remain visible after the change.

For example, a rough study could use several overlapping pointed outlines to stand for the mouthful of leaves. That is an illustrative shorthand, not a reported leaf count or arrangement. A note such as “leaf shapes schematic” prevents the drawing’s convenience from becoming an apparent fact.

The same restraint applies to the moustache. Its width, curl, texture and colour are unspecified. Use a minimally detailed labeled shape if drawing it, and mark the contour as schematic. The record’s precision comes from preserving the transformation, even when the supplied appearance is sparse.

Which animation concepts help check the record?

Keyframes provide a useful way to think about the stated conditions. Krita’s animation guide explains a traditional workflow in which keyframes contain important poses and drawings between them supply the intervening action. Applied here, the endpoint studies identify what is known before any intermediate action is considered. Krita Manual: Animation with Krita (https://docs.krita.org/en/user_manual/animation.html)

For this record, keep the intermediate action undescribed. Adding a halfway drawing would make a new claim about how the transformation unfolds. The two endpoint studies and their correspondence notes already preserve the information supplied.

If you use animation software to compare drawings, onion skinning can help inspect their relationship. Krita describes onion skins as tinted or coloured views of preceding and following frames overlaid with the current frame. Its controls allow their visibility and opacity to be adjusted. Krita Manual: Onion Skin Docker (https://docs.krita.org/en/reference_manual/dockers/onion_skin.html)

Use that overlay as a comparison aid. Check whether a feature was accidentally omitted, whether a label points to the intended group, or whether an illustrative outline shifted unintentionally. An overlay cannot establish an unknown motion path or recover unspecified intermediate shapes.

Automated shape tweening requires particular care. Adobe’s documentation explains that Animate generates intermediate shapes between specified vector shapes. Shape hints identify corresponding points in the starting and ending shapes. These are tools for constructing a transition, so their generated results should not be treated as a record of this scene’s unspecified transition. Adobe Animate: Shape tweening (https://helpx.adobe.com/animate/desktop/animation/shape-tweening.html)

The useful principle is explicit correspondence: identify what becomes what. You can apply that principle through labels without asking software to generate additional frames. That keeps the eyes-to-nostrils and leaves-to-moustache changes legible while retaining the limits of the description.

What should the finished visual record contain?

Finish with a small, self-contained package: the literal scene sentence, the two labeled endpoint studies, the feature correspondence list and the note about unspecified timing and intermediate appearance. Keep any illustrative drawing choices identified beside the relevant study.

A digital storyboard can hold the drawings and notes together. Krita’s Storyboard Docker supports configurable comment fields and export to PDF or SVG. For this scene, example comment fields could be “feature correspondence” and “illustrative choices”; those names are suggested organisation choices. Krita Manual: Storyboard Docker (https://docs.krita.org/en/reference_manual/dockers/storyboard_docker.html)

Before considering the record complete, read each transformation from its starting label to its result. Can a reader tell that the eyes themselves become nostrils? Can they tell that the moustache comes from the leaves initially held in the mouth? Remove any detail that accidentally changes either answer.

Also inspect the annotations for implied movement. Arrows inside the drawing can look like travel paths; frame numbers can imply measured timing; a detailed intermediate shape can imply an observed stage. Use external correspondence marks and plain captions wherever those implications would exceed the supplied information.

The finished record should preserve one unmistakable scene: an orangutan’s eyes become nostrils, and its mouthful of leaves becomes a moustache. Clear endpoint studies, exact labels and visible uncertainty make that transformation useful to revisit without adding an animation the description never supplied.

Sources

• Storyboard Docker — Krita Manual (https://docs.krita.org/en/reference_manual/dockers/storyboard_docker.html)

• Animation with Krita — Krita Manual (https://docs.krita.org/en/user_manual/animation.html)

• Onion Skin Docker — Krita Manual (https://docs.krita.org/en/reference_manual/dockers/onion_skin.html)

• Shape tweening — Adobe Animate (https://helpx.adobe.com/animate/desktop/animation/shape-tweening.html)