In the second week, I learned about the importance of weight and motion in animation, and how they are conveyed through timing and spacing.
Time Charts
The first thing I learned was the time chart. This was a new term to me, as I was not very familiar with the animation workflow. A time chart is a visualisation that illustrates the timing and spacing of an animation.
Timing and Spacing
In particular, timing refers to the number of frames a movement takes, while spacing means the variation of speed. Even with the same timing, different spacing patterns can lead to different speed.
Weight
When talking about weight, I learned how it can be illustrated through speed and an object’s interaction with a character.
For example, under the same force, a heavier object generally takes longer to accelerate than a lighter one. Similarly, when a character holds a ball, the closer the ball is to the character’s hips, the heavier the ball looks.
Bouncing Balls Animation
To better understand weight and motion, we practised animating different types of bouncing balls, including a tennis ball, a beach ball, a bowling ball, and a basketball.
This was my first time using Autodesk Maya to animate something. I was introduced to the Graph Editor and learned how to add keyframes in Maya. I also discovered a very useful feature called Motion Trails, which allows me to visualise an object’s movement directly in the viewport.
While working on this assignment, I also discovered how convenient Maya’s Auto Key feature is. It automatically creates keyframes for modified channels, rather than keying every channel at once. I found this useful for keeping my timeline clean.
As part of the assignment, I researched references for each type of ball to understand how their weight and motion. I analysed the references frame by frame and drew time charts before animating in Maya.
Generally speaking, after receiving feedback from Ting, I realised that my biggest problem was that the spacing in my animation was too even. This made my balls look floating, making it difficult to distinguish their different weights. Also, my timing was also too slow.
Tennis Ball
Reference:
0:19 - 0:25Feedback:
- The overall timing was too slow => cut it in half.
- The ball should slow down as it approaches the highest point of its bounce. As it begins to fall, it should accelerate, moving slowly at first and then faster as it approaches the ground.
- My time chart was too evenly spaced => overly even spacing in the animation.

Revision:
Beach Ball
Reference:
Feedbacks:
- Too much the squash and stretch => over-animation.
- The ball moved too slowly compared to its rotation, especially when rolling across the platform.
- Both the rotation and the travelled distance when the ball fell from the platform were inaccurate.


Revision:
Bowling Ball
Reference:
Feedback:
- Both the timing and spacing were too even, making the ball’s weight less realistic.
Revision:
Basketball
Reference:
Feedback:
- The overall timing was too slow.
- The spacing was too even, making the ball appear to float.
Revision:
Golden Poses
This week, we continued practising posing. But this time, we used a different rig with a character of different proportions. The assignment included four tasks:
- Pose one Hero Pose
- Pose one Sitting Pose
- Pose one Angry Pose
- Make my poses in 360 degree camera
Hero Pose
Feedback:
- The chest and hips were too parallel to each other.
- Exaggerate the curve of the character’s side profile.
- Push the exaggeration further in certain parts of the upper body, such as the chest and shoulders. Some stretching is acceptable when it is intentional.


Revision:
Sitting Pose
Feedback:
- Exaggerate the curve in the side view by bending the back further.
- The silhouette from the side view looked messy.
- I needed to emphasise the curve around the hips.


Revision:
Angry Pose
Feedback:
- The direction of the chest did not match the reference.
- Push the hips further backwards to exaggerate the pose.
- Due to the character’s proportions, my pose lacked balance and looked as though the character was about to fall.




Revision: