Moom walk cycle V27 - V31

Jon gave me some great critique regarding the 'stamping' in my walk cycle, suggesting that I drop the leg on the passing positions in order to give a more subtle step. First are a couple of attempts I made to correct the issue beforehand, then are the ones following his feedback where I tried to integrate his advice - all with varying success, but things that don't work are just as important as those that do. So here we go. Let's blast through this:

Version 27



First, here's the default version, just so you can see what I'm trying to correct. I've made some slight alterations since V25 - couple of things regarding the arms, just to loosen them up a tad. The legs do look pretty off in comparison to the otherwise fairly casual arms. His legs have a definite 'kick' to them.

Version 28



Here, all I'd done is very slightly adjust the foot roll on the up position, trying to bring it a little lower and closer to the contact pose. It's only a very subtle change and it does appear to have smoothed things out by a fraction - but not really enough to be noticeable to anybody that hasn't been staring at it for 4 million hours.

Version 29

First attempt following Jon's feedback where I tried dropping both the legs on the contact pose and also bringing the leg on the contact a little closer to the up position. It didn't exactly work; the issue I'm having is that dropping the leg of the passing position, the foot scrapes or goes straight through the floor. I can adjust the foot roll to try and bring it back up but rotating it back too far (in favour of the previous pose) causes it to twist uncomfortably, and also raises the knee again - which puts me straight back to square one. Rotating it forward lessens the height of the knee but this is problematic in that the foot, rather than delaying and dragging, then looks very robotic as we can see above. It needs to drag a little for flexibility. It also means that the space between the trailing leg on the down and passing positions is very small, causing the leg to delay at the crossover.

I also had to adjust the bend in the trailing leg on the down position to compensate for the lower passing position - otherwise the knee and leg were bent more on the down position, causing a bit of a jump/'pop' as it tried to interpolate the two keys. Unfortunately lessening the bend in the knee now means there's too little movement to stretch equally across the frames - as a result the knees on both legs start to bend at exactly the same time and move almost in perfect synch, which looks a little peculiar and quite robotic to me?

It may also be me but I kind of think that dropping the leg looks a bit like he doesn't bring it up far enough - the walk just seems to lose a lot of the feeling of weight?

I'm actually wondering if the stamping is actually more to do with the large gap between the legs on the up and contact keys - closely observing it, I can see it almost looks as if he's kicking his leg out. I think perhaps I just need to alter those positions so that the legs are just a little closer together in terms of posing so that it's a bit smoother?

Version 31



All of these captures look exactly the same... it must look like I haven't changed anything! I guess it's one of those things; when you've been staring at something frame-by-frame for so long you can pinpoint every tiny little thing in each frame. Things that nobody else in their right mind would ever notice.

Anyway, here I just tried adjusting the contact pose very slightly so that the step was a little less wide, allowing the leg enough time to travel smoothly from one pose to the next. It seems to have gone some way to removing that 'kick,' but it also plops me back to square one where my step wasn't quite wide enough. I think that, really, it's the up position that needs to change more than anything. If I can just tinker with the foot roll and leg position I might be able to figure out a way to smooth it out a little.

Shuttlecock drop test V1

Poking around on myUCA, I found the reference videos that were very kindly posted up. My own set of shuttlecocks have actually arrived now, so I'll be able to shoot my own footage to use, but I thought it might be helpful to practice animating a basic drop of a shuttlecock before I get into throwing them around.

Analysing the video, I was able to break it down somewhat and figure out the main timings:

It's actually quite a tricky one to plot in thumbnails. I got a bit confused somewhere along the way - started out alright with the first graph by just showing a few of the poses and a few scribbled notes, but the second graph started to get a bit confusing where I started trying to get in more of the exact motion. I started by sketching it all in one place then halfway through started spacing it out (mostly cause I didn't have enough room on the left. Didn't occur to just sketch it going in the opposite direction) - it's fine for purposes of checking the poses but it doesn't make much sense in terms of what the shuttlecock is supposed to be doing. I should have refined it further and made a clearer, more final chart that makes sense to look at before trying to animate. Perhaps that's where I went wrong.

But anyway, looking at the video reference, the shuttlecock drops very quickly to start (weighed down by the tip), taking about 9 - 10 frames to fall. It hits the ground, tip-first and bounces back up again, slowly sagging to the side as it does. It doesn't bounce very high, and it pauses for a couple of frames but continues rotating slightly before it starts to fall. It lands on its side and the tip strikes the table/ground which causes it to bounce back up. The feathers of the shuttlecock hit the table as well which knocks the tip back forward - so you get a sort of wave effect as it rises and falls.

Bearing all this in mind, here's a first attempt:

This is mostly just a first draft, nowhere near complete yet - as always, little more than keyframes with no fcurve or timing alteration. That will all come once I've got the basis of the motion sorted out.

Just to review what I've got so far, the drop itself as the shuttlecock enters the screen is far too slow. It's only 10 frames, as per the diagram, but I don't think I really dropped it from high enough. If I increase its starting height then it should speed it up quite nicely.

It doesn't really bounce high enough after striking the ground, making it seem quite heavy. All I'll need to do is just increase the height of its peak and it should be a bit better.

The last problem is the bounce at the very end as it comes to a stop. I don't know if it's the timing, or some mistake in the keyframes, or even if it just looks weird because it's bouncing on the spot - but it seems to be a bit of a kink as it bounces off the table. I really can't put my finger on it - it's weird, when I step through it frame by frame, it actually looks fine, so I wonder if it's just in the spacing or timing?

After tweaking that, I plan to spread things out so that the shuttlecock bounces across the floor rather than up and down in a straight line - see if that helps things any - and then start looking at altering the curves and timing to give the shuttlecock a sense of weight. In accordance with the video I'd like to delay the shuttlecock at the peaks of each bounce for just a couple of frames and keep it rotating as it hangs in the air.

The process of animating the shuttlecock so far was pretty simple. Using the reference video posted on myUCA, I simply went through frame-by-frame, identifying key poses for the shuttlecock and simply replicating them within Softimage using the rig controls.

The shuttlecock rig is quite nice because it only has two controls - rotation and position - but I do find it very difficult only being able to view keyframes for one set of parameters at a time. This makes offsetting and re-timing things quite tricky as I need to keep flipping back and forth between each rig control to check the location of other keyframes.

I think the biggest mistakes I made in terms of workflow were not planning properly and also animating the shuttlecock bouncing in place rather than mimicking the motion in the video and having it go across the table. You'd think I'd have learned from the bouncing ball exercise that that's a bad idea!...

Nonetheless, I'll give it another shot!

Bowling ball drop rotoscope V2

Started cleaning up the rotoscope; first I lengthened and slowed down the shot, which massively improved things. I think it's looking a bit better now; the main things I had to alter were, as said previously, the speed of the ball's drops and the hangtime at the peak of the bounce. I messed around with the rotation slightly as it's falling, and also reduced the distance that the ball rolls away.

I'm not terribly happy with the rolling at the end - it looks off to me, but I can't seem to put my finger on exactly what's wrong. I feel as if maybe it starts rolling too soon after landing - I can't explain it, but it looks as if the ball is sliding more than anything. Perhaps the rotation doesn't quite match up to the speed of the movement? Maybe it's the timing on the movement?

The initial drop seems a bit too slow as well - the ball lacks any real weight and I think some of the successive bounces need a bit of tweaking as well. They're a little choppy? Overall, I'm not too sure about any of it - the ball, to me, doesn't seem to carry any particular weight of character. Maybe it hangs in the air too long as well?

Bowling ball drop rotoscope

Taking a brief break from fcurves, thought I'd have a bit of fun playing around with Softimage's rotoscope options. You can basically attach an image to the back of any viewport to use as modelling reference. That in itself isn't especially useful for my purposes, but in addition to static images, Softimage allows you to attach image sequences as well.

I found a video on Youtube of a guy dropping a bowling ball in front of the camera and decided to try playing around with it.

Mucking around with trying to convert the file to an image sequence appears to have messed up the frame rate (it was probably originally shot at 29fps, come to think of it) so the final version appears to be on fast forward, but hey ho.

To attach the sequence, click on the display option dropdown in the top right of any viewport and click on 'Rotoscope' which will bring up the 'Rotoscopy' property page.

Clicking on New > New from file then opens up a dialogue box - by default, Softimage looks in the 'pictures' folder for all rotoscopy images. I used the terribly-converted bowling ball image sequence, which Softimage then pins to the back of the scene.

Scrubbing the timeline will play back the image sequence! Magical. The only problem is scale - as you can see, simply dropping in a primitive sphere reveals how tiny the image is, which isn't always ideal. In most cases you could simply scale down your object but in instances where you have a complex character rig, you don't really want to scale it down too much.

The other option is to enable the 'attached to camera' checkbox in the rotoscopy property page. This basically fixes the rotoscope to the lens of the camera so you're able to pan around with the camera and line up your object over the rotoscope without altering its position. You can zoom in and out of your object without effecting the scale of either the object or the rotoscope.

When you're happy with the positioning, you can turn on 'enable pixel zoom' (the square magnifying glass at the top of the viewport' which locks the position of the rotoscope and object together. 

Sorry if that made no sense. I'm still very tired!

Anyway, I didn't get too fancy with it. I just wanted to see how it worked, mostly, so literally all I did was trace the position of the ball with keyframes - no fancy fcurve editing (yet)!

Wireframe:

No distracting background:

Of course direct rotoscoping never usually works - for things like ball bounces the results can be decent enough, but in the case of more organic or lively motion (particularly walk cycles) the resulting animation can lose a lot of the original personality and weight. Rotoscope and motion capture can be a great starting point for overall timing and to get a very basic animation down, but they usually require so much cleanup afterwards you may as well be animating from scratch!

Anyway, I actually think that the rotoscope looks mostly OK - there's certainly a feeling of some kind of weight, but there's a lot of tweaking and refining that could be done. I think the overall speed is probably a bit too fast, mostly due to the problems in converting the frame rate - so I'll probably sort that out with the region select tool in the dope sheet. Once the speed is sorted out it should be a little easier to pinpoint the exact problems with it, but I think generally the series of successive bounces could use some work. Looking at the original footage there is a noticeable pause at the peak of each bounce before it comes back down, which mine definitely lacks. This should be easy enough to fix.

As an aside, I also think that the ball rolls away a little too long at the end, but that could simply be due to the fact that the rest of the animation is too fast in comparison.

Post-tutorial wall bounce amendments

Following Jon's (very helpful) critique on Friday I amended my first wall jump exercise!

We both agreed that my ball hit the peak of its stretch on the drop a little too early, and he also pointed out that my ball remained in the squashed position once it began the jump, which looked a bit weird — it needed to stretch as soon as it left the ground. There was a similar issue with the landing — the ball squashed before it even hit the ground.

My first amendment was better, but the ball was still stretched on the drop a little too early, and Jon commented that he felt the drop itself was perhaps a bit slow. I do think that the speed of the jump and fall is a little too uniform, so on my next amendment I made an attempt to speed it up slightly by reducing the number of frames between the highest and lowest points and slightly altering the fcurve.

The faster speed seems better to me, but I think the stretch is still too early! It also seems to me like the ball comes down a little too quickly — I may try increasing the ball's delay at the peak of its jump, or just slow down the beginning of the drop a little.

I also went back and tried to correct the same squashing/stretching issues in my other bounce, the one with multiple jumps:

Something still seems at odds to me about this one, but I'm not quite sure what it is exactly. I think that maybe the ball hangs in the air a little too long on the first (and smallest) bounce, or maybe that it doesn't hold its initial downwards/preparatory squash long enough. The ball's squashes on each impact with the ground are also quite quick/sudden, so maybe I need to look at holding the squashes on-screen for just a little bit longer?

Softimage - interpolation experimentation V4

Yet another update. Still having difficulty ironing out that bug with the looping! It's bothering me. A lot.

Aside from that I've altered the ball's hangtime in the air. It's looking better, but I think it's still a little too much? I also think that now the ball drops around that first corner a little too fast. Arrrghh!! Am I never satisfied?! (The world: "no!")

Luckily it's a simple fix, just altering the slope of that first curve so it's a little shallower. I do feel that this is actually really, really helping - I'm far from confident, but I do feel I understand the fcurves a lot more than I did a week ago.

Just to talk a little about what I changed this time:

First thing, to get the nice overshoot at the top of the right side, I just brought the height of the curve a little above the position of the next keyframe. This gradual slope caused the ball to slow into a position slightly above the point reached by the next keyframe, then slowly dropped back down into it before continuing the movement. I also lessened the width of this curve on both sides, so that the ball wasn't hanging in the air quite so long before dropping back down.

The same principle applied for the overshoot on the left side; I dropped the curve a little lower than that keyframe. There's quite a sharp curve here, which shows the ball's acceleration to the bottom of the drop.

I lessened it slightly, but it's still a little too extreme. In retrospect I think that the problem with the glitchy loop is because I've put the overshoot in the wrong place. A better place to put it would be just before the last keyframe, as opposed to after the first. That way the ball can overshoot before the last keyframe, which will be identical to the first, allowing it to loop straight back to the exact same position and continue its drop. It just makes more sense that way (to me at least...)

Softimage - interpolation experimentation V3

Slight update! I've added a little overshoot to either end of the ball's climb, which softens things out and adds a little more realism to the whole thing. There's a weird kink at the very end caused by looping the video - I think the start and end positions don't quite match up or something. Need to figure out how to get the overshoot without it jerking like that!

I actually shunted the position of a couple of the keyframes around a little bit, mostly the second one. I moved it a little further to the left so that it hit the lowest point of the drop a little more quickly, solving the problem of it falling too slowly at the beginning.

I need to look at fixing the kink at the end now, as well as reducing the ball's hang in the air at the right side.

Softimage - interpolation experimentation V2

A slightly more complex experimentation this time. I wanted to try and have the ball move in a semi-realistic fashion down a steep slope, rolling along the bottom of the curve and up the other side. Almost like a skate ramp - the ball would of course lose momentum as it begins the steep climb, so it probably wouldn't quite make it to the top before it rolls back down again.

Maybe viewing the video will make more sense...!

Looking a little shoddy thus far, but I think I can tweak it to fix it up a little. I cheated a little on animating the ball itself, but seeing as this is mostly an fcurve exercise I think I can get away with it! I drew the path using the bezier knot tool as described in one of my earlier posts. I tried to keep the angle of the slopes relatively consistent so that it would have an equal distance to travel on both sides. I then just set the curve I'd drawn as the ball's motion path by selecting the ball and using Create > Path > Set Path. The ball then locked itself to the first bezier knot point and the animation is automatically set to follow the path using a splined interpolation - a relatively lifeless speed and not at all realistic. 

Opening the animation editor reveals that the ball's speed and motion is controlled by fcurves! (I didn't screenshot it, sorry!) So I set to work tweaking and messing around with it.

The curves for this one are a little convulted, but I'll do my best to try and explain them...

The first thing I did was activate the animation ghosting for the ball so I could get a clearer picture of how my timing was without needing to play it back every time. This allowed me to much more accurately tweak my curves as I was able to see immediately after adjusting them how it would effect the animation.

Originally, the ball was a little too 'sharp' on the curve at the bottom. It followed the shape almost exactly so I needed to round it out a little bit so it didn't jump too sharply on the corner. I simply added a couple of keyframes either side of the lowest position at the bottom of the path and dropped the Y position a little, so that it remained on the bottom of the curve a little longer.

Starting from the first keyframe, I wanted it to slowly accelerate out of the highest point and pick up speed as it dropped down the slope, hence the sudden spike in the curve. I wanted it to keep a continuous speed as it turned the corner and uses the energy gathered from the sharp drop to propel itself up the other side. Gravity would be pulling down on the ball all the while, causing it to gradually drop in speed as it nears the top of the slope, eventually pulling it back down and causing it to roll back up the other side.

There's a very wide curve on the top keyframe that keeps the ball at its current level before gradually beginning its descent which rapidly escalates into a steep drop, increasing the speed of the ball. 

I think that I've sort of got the effect I was going for - it's getting there, at least. I think that the ball probably hangs in the air too long at either side of the curve, so I need to reduce the width of that curve so that it drops a little sooner. This might also allow me more time to adjust the acceleration so that the increase in speed is a little more gradual. I think that it gets too fast too soon as it falls from the right side. Conversely, I think it's too slow in picking up speed on the initial drop from the left side - simply shifting the width of the curve so that it's a little more equal on both sides should rectify that.

I also think that it stops too suddenly as it returns to the starting position, almost as if it's hitting an invisible ceiling. I'd like to add a little overshoot to that, so that it flies up a little further before dropping back down. Tweaking the curve so that it extends slightly below the final keyframe should give me that result.

Hopefully that all makes sense...!

Softimage - fcurve interpolation experimentation

More experimentation with interpolation and fcurves. Another set of three balls, each with the exact same keyframes, but with different timing as defined by their fcurves.

(Magical looping Vimeo version coming as soon as it gets processed!)

The first ball is a fairly standard example of slow in/out - the ball starts at a high speed and rushes out of the starting pose, gradually losing speed and slows in to the ending pose. It slowly retreats back out of this pose and slowly picks up a bit of speed as it makes its way back across the scren.

Looking at the animation ghosts for this ball reveals the movement in more detail. The spacing between each frame reveals the ball's gradual deceleration into the end pose. I've found that looking at the ghosts as I'm working has helped me to get a better grip on how the slope of the curve is altering the timing without needing to play it back.

The second ball appears almost cautious as it very slowly creeps out of the starting position then suddenly rushes forward to the ending position, leaping back and inching slowly back to the start. The movement is indicated by the curve's very gradual incline for the first few frames, suddenly spiking upwards as it draws towards the right side of the screen. It comes back almost as fast as it entered, slowing down again as it reaches the starting position.

The third ball is, again, a fairly standard slow in/out. I just wanted to play around with the unified slope orientation option mostly - it looks almost identical to the first ball, but the difference speed at either end is slightly less extreme and there is a little more of cushioning between the start and end points.

Softimage - fcurve interpolation types

In an attempt to better understand the fcurve editor, I'm going to be doing some far more basic examples of how the curves effect the timing/speed. To start with, looking at Softimage's preset interpolation types:

The three balls all have keyframes set at the same points. Although they reach the start and end points at exactly the same time, the way in which they reach those points is very different. In other words, the speed is the same, but the timing is different.

The first ball uses the default "spline" interpolation. Each keyframe will be connected by a smooth curve or "spline" (tried looking up what a spline actually is, but it made my brain hurt), eases into or out of each keyframe, creating very smooth and organic animation.

The curve shows how the ball gradually accelerates out of the starting position, then gradually slows into the second keyframe (the highest point on the graph represents the furthest distance travelled). It then slows out of that pose and comes back in the opposite direction, easing back into the starting position.

The second ball uses the "linear" interpolation type, which as the name suggests is a constant rate of motion with no "cushioning." Objects with a linear interpolation will have their keyframes connected by straight lines, terminating in sharp points at each keyframe, representing a constant speed and sudden changes at each into and out of each keyframe. The result is very mechanical and robotic, potentially useful in animating cameras or lights where such organic motion as offered by spline interpolation isn't always needed.

This ball's rate of motion is steady and unchanging. It starts and ends at exactly the same speed with no acceleration at all. The change of direction is very sudden and sharp with no cushioning from one keyframe to the next.

The last ball uses a "constant" or "stepped" interpolation which keeps the keyframe's current values (position, rotation etc) stationary until the point of change, at which point it will "pop" or "snap" straight to the next one with no in-between movement. This is primarily useful for blocking out the keyframes of an animation without any pesky inbetweens, making it easier to check that the flow from pose to pose is correct. It could also be useful for camera or lighting cuts!

You can see from the graph that the ball's x position remains at the same level until frame 25, where it suddenly snaps upwards to the far right of the screen (highest point on the graph). Again, it remains in this position until frame 25, where it suddenly pops back to the lowest point on the graph - the starting position.

It's mostly the spline interpolation I'm interested in at this point. I certainly understand the principle of how it works, I think it's just going to take a lot more practice to get my brain used to interpreting the curves as speed and movement. I'm going to use the same setup as above - three balls moving at the same rate - but altering the fcurve for each one so that I can better compare the results and, hopefully, start to understand how certain timings "look" as a curve.

Fcurve experimentation - ramp roll V1

Setting myself a couple of little exercises to try and get to grips with Softimage's keyframes and fcurve editor. I decided to try what I thought would be a fairly simple task - get a ball rolling down a ramp before slowing to a halt. It was trickier than I thought.

I didn't know of any better way to get the ball to roll down the ramp other than to manually keyframe it every few frames to ensure it stuck to the surface of the ramp - if left to its down devices, Softimage would have simply allowed the ball to take the most direct route to the next keyframe - levitating the ball away from the ramp, or cutting straight through it, etc. This caused a few problems with the fcurve editor as each new keyframe places a new point on the curve, so adjusting the angle became a case of having to ensure that the curve ran continuously through each point. That meant a lot of handle adjusting and balancing.

It's looking really dodgy so far. I had trouble figuring out how to get the ball to accelerate on the ramp and slow to a stop at the end - it sort of does that, but it stops far too suddenly and the ball speeds up upon exiting the ramp. It should be easy enough to fix, once I've played with the curves a little more.

Wall bounce homework V2, take 2

Slight alterations made to the first bounce. In addition to increasing the height of its peak, I increased the time it took to reach that point by a couple of frames. This gives it enough time to reach the peak and start its descent with less of the sudden snap that it had before.

I think it's looking a little better, but hopefully some timing tweaks made by the fcurve will improve it even more.

Wall bounce homework V2

Similar to the last exercise but this time I wanted the ball to execute four consecutive jumps in its attempt to get over the wall.

Timing's a bit shoddy so far - these are literally just keyframes on the postion/scale parameters. I think the last two jumps are okay but the first two look off to me. I think it needs to bounce just a little higher on the first jump, or at least reach its current point a little sooner. I think there's too big a change in maximum height reached between the first and second jumps so that there's not really the feeling of successive power being built up. I need to alter the points at which it reaches its maximum stretch on rising and falling as well.

I'm also thinking of adding a set of successively smaller bounces after the final jump as it comes to a rest and loses energy. Should have done that first really!

Wall jump homework V1, take 2

I've dived once more into the terrifying waters of the fcurve editor and emerged very wet, very cold, and not necessarily any braver for it!

I attempted to alter the function curves to add a little more personality to the ball's jump, as well as re-timing a few of the keyframes using the dope sheet, in accordance with the changes made by the fcurve editor.

It took me a fair bit of tinkering to figure out how to alter the curves to best effect, but I think I finally have something fairly decent:

The overall result gives the impression of a ball leaping into the air to catch a glimpse over a very high wall.

The first thing I did was speed the whole thing up by using the dope sheet's "region select" tool to squash all the keyframes together a little more.

With the tool selected, simply drag a selection over the keyframes you want to re-time.

Then, holding shift, drag the handles on either side of the region and drag left or right to reposition/re-time all the selected keyframes. I think you can actually reverse keyframes using this tool as well, if you drag the region far enough in the opposite direction!

I reduced the overall duration of the animation from 41 frames to about 35; the result is just slightly faster but it adds a little more energy to the ball's bounce.

Once I was happy with the timing I switched over to the fcurves editor to alter the speed/timing of the ball's jump by adjusting the slope of the y axis' curve. By selecting "isolate curve" under the view menu you can temporarily hide out all the other curves and view only the curves of the selected parameters. Probably not necessary in this case but is tremendously useful if you have a more complex animation with a lot of curves all over the place.

I didn't get screencaps of all my curve alterations (there must have been at least 50 billion) but this was the one I ended up with. 

The large, sweeping arc at the top represents the ball's delay at the peak of the movement. it moves gradually more slowly as it reaches the height of the jump and remains relatively airborne for a few frames before gradually beginning its descent, picking up speed as it nears the ground.

Huh. Typing that out made much more sense than it did as I was trying to understand it in my head.

It's kind of embarrassing how long it took me to figure it out; it's a relatively simple idea and I mostly understand the principle of it, I think it's just a bit deceptively mathematical and my brain is having trouble getting to grips with it. I find that I'm having massive trouble reading these curves and graphs as speed and timing - my brain just won't process it. I think I've managed to whittle it down to a basic understanding of "the steeper the slope, the faster the movement," but when I start thinking about inverted curves I start to get confused again. 

I'm hoping that it will start to get easier and more natural with practice. I've never been mathematically gifted and anything vaguely resembling numbers tends to frazzle my brain more than I care to admit.

Anyway! I then went back to the dope sheet and altered some keyframes in accordance with the new timing of the ball's ascent and descent. I shifted the stretch poses as it rose and dropped a little further along, so that they would reach the peak of their stretch at a slightly later point (giving them enough time to squash into the next pose without appearing too sudden), as well as off-setting the squash at the top of the movement so that it occurred one frame later. The result was a tiny bit of overlap as the ball reaches the height of its jump and the bottom continues upwards to catch up, 'squashing' it at the top of the movement.

I'm still not at all comfortable with my use and understanding of the fcurves. I'm going to start a few more tests and try to get some different results - applying the curves to a variety of personalities/types of bounce etc. should hopefully give me more of an idea as to how the angle and slope of the curves effects the animation.

Wall jump homework V1

Got stuck in to some pretty complex stuff today, dipping our toes into the fcurve editor in some more detail. I never quite got around to understanding it fully during my own experiments so I was looking forward to a more guided and structured approach!

Homework for this week is to animate a ball trying to jump above a wall - the idea is to experiment with some more advanced keyframe tweaks using the fcurve editor to really nail the timing and get some personality into the ball. I'm going to start by completely ripping off emulating Jon's example, just to get a feel for the more structured way of working and try to get the hang of the fcurve editor.

Again, started by just roughly making a quick plan of how I wanted the ball to move. I scrawled out some beautiful and accurate drawings of the ball in the various poses that I would need, before moving on to figuring out their relative positions against the wall. Then I spread them out so I could see them more clearly and get a feel for how many keyframes I would need to lay down to get started.

The fact that it's such a simple animation certainly helps, but it's amazing how much a bit of forward planning streamlines the process. Within about 15 minutes I came up with something that's actually quite workable:

It's all done using the basic transformation tools - the wall is simply a squashed cube, the floor is a grid and the ball is a sphere. The sphere was animated using keyframes on the translation and scale parameters - following Jon's advice I animated one parameter at a time to save confusion, starting with the translation. When I was happy with that movement I added in the squash and stretch using the scale tool. It really helps to keep things simple and organised!

The next task is to mess around with the timing. I think the overall speed of the bounce is too slow so I'll probably shift everything a little closer together to speed it up a bit, before cracking into the fcurve editor to muck around with the timings on the jump/fall.

I'm aiming to have the ball spring into the air with relative speed, slowing down as it reaches the peak of its jump. I'll have it hang briefly in the air for a moment before hurtling back towards the ground. That should hopefully get me more accustomed to using the fcurves so that I can more confidently start mucking around and experimenting with other timings!

Slide homework V3, take 5

And here it is with tweaked timing on the roll across the table. I have nothing else to say about it, other than the fact that this is the angle it looks best at. Viewing it from the front reveals how terrible the rebound off the ring is! So I'm cheating and covering it up.

Slide homework V3, take 4

Still messing around with this one, trying to get that recoil off the ring just right. It's trickier than I thought!

   

It's kind of random, but I ended up looking at the above video for an idea as to how the ball might react on collision with a solid object. It looks like it actually keeps spinning in pretty much the same direction, so I tried to emulate that in the animation:

I'm still finding it quite difficult to get the timing on the rebound just right - the ball always seems to delay right before changing direction and no matter what I do, I can't seem to fix it. This was my best attempt. I guess I'm not quite getting the hang of manipulating keyframes! I did manage to reduce the delay slightly but that caused the ball to shoot off way too fast which I wasn't able to easily fix, given the relatively small amount of frames between the ball's position at the ring and the edge of the table.

I sped up the exit from the slide/entry to the table a bit but now, looking at it, it seems way too fast - a very sudden change in speed from the ball's descent down the slide. I'm going to tweak that once more to try and get a more consistent speed and then call it a day. 

I'm actually a bit more pleased with the rotation of the ball now, though - I had it change direction on the drop to the floor as it bounces away and it seems to have worked fairly nicely. One small success!

Slide homework V3, take 3

Made a brave attempt at altering some of the timings. Most notably the ball drops with significantly more weight than before - it certainly looks more like it's dropping rather than floating! I also attempted some timing adjustments on the exit from the slide, making it a little faster as it flies out the end and hits the table. I'm still not at all happy with the change in direction after hitting the ring - the physics feel totally off to me. I don't even have anything remotely ball-shaped to reference, and clips on Youtube are only so much help!

I've made some minor adjustments to the ball's bounces as it hits the floor as well, manually tweaking a few frames to give a slightly smoother arc. I've sped up each successive drop as well and brought the smaller bounces a little closer together to help give the idea that it's losing energy.

I can't quite seem to put my finger on why the recoil off the ring looks so off. It would certainly help if I had something to reference. I've got a slight feeling it might just be that the change in direction isn't quite sudden enough. It looks as if the ball hits the ring with a fair bit of speed, so it should probably fly off in the other direction a little more suddenly. Think I'm going to have to keep playing around with it.

I have actually added some rotation to the ball as well, but you can't see it owing to a lack of pattern or texture. I captured a version with the wireframe visible so you can actually see the rotation:

I actually prefer it without the rotation if I'm being honest - I think it's a bit distracting, but that might be because the rotation doesn't make any sense. I have absolutely no idea how colliding with the ring would effect (or is it affect?) the rotation of the ball, and as I said I've got nothing to reference. I went with my best guess and tried to just have it change direction to roll in the direction it's moving but that looks pretty clearly wrong to me.

I'd like to try adding a nicer rotation to the drop and bounce, as well as have it slightly teeter over the edge of the table just before it drops. I think in order for that to work I'd need to have a gradual deceleration after it hits the ring, so it approaches the edge a little more slowly.

But hey, it seems to be shaping up at least! 

Slide homework V3 update

Little update on the previous animation, I've plotted out the ball's drop from the table. It bounces a little as it rolls away - there's a minute amount of squash as it hits the ground, but I think it still needs a little tweaking. I think the arc of the bounce is getting there but the inbetweens need a little manual tweaking to get it smoothed out.

I rendered out a  couple of angles so you can see it a little better:

Bit of an issue as the ball goes down the slide - as you can see in the side view, it's a little too low and the ball clips through the bottom of the slide. Luckily that's simple enough to fix, just need to adjust the position on some of the frames.

There are a lot of timing problems with the last section - notably as the ball bounces off the ring. It's too slow and moves very uniformly - ideally, I think I need to speed up the ball's entry onto the table and have it knock against the ring with just a little more force. The ball could then lose energy as it rolls towards the edge of the table, pausing as it teeters on the edge, before dropping down. The drop itself also lacks any speed or weight - I've not yet adjusted the timing at all, so that will be my next task. After adjusting the timing on the drop I may need to tweak the squash as it hits the ground first time, depending on the speed of the impact. I don't imagine it's a very heavy ball, nor is it too much of a drop, so I don't think it should fall too heavily.

Regardless, it seems to be coming together! The rough motion is there, it's really just going to be about tweaking the timings and adding a bit of polish now. I plan to add rotation to the ball once I'm satisfied with the movement.

Slide homework V3

Here's a little progress on my third attempt at the slide task. It's not yet complete but I figured I'd take a breather and just talk a bit about what I've come up with so far and how the approach I've taken has been working out. These sort of half-finished progression posts are quite helpful I find!

So, this time I sat down and thought about it much more carefully, spending some time plotting out the path and action that my ball would take. I ran through the sequence at different speeds in my head and on paper, timing myself using a stopwatch and taking a very loose average of the timing that worked best. I plotted the rough keyframes on this sophisticated and totally accurate diagram: 

Using the chart as reference I was able to copy the keyframes over to the 3D counterpart, which really helped me to get to grips with the timing. I also took a brave stab at timing/spacing charts which you can see dotted all over the page - though certainly far from an industry standard I feel that taking the time to have a go at them myself really improved my understanding of how they worked. I've read lots about thinking in rhythms and spacing and beats but I just didn't really understand how to apply any of it. I think it's one of those things that, no matter how many books you read on the subject, you actually have to give it a go before the penny finally drops. 

I hope that made sense.

Anyway, though the resulting animation probably doesn't look too much different, the process and workflow of actually creating it was more logical and far more straightforward. A little forward planning really does make such a monumental difference - and a far less stressful experience.

It's not quite complete yet, as you can see. I still need to tweak a little of the timing as the ball exits the slide - I kind of feel that its entry to the table is a little too slow. I think it could stand to be a bit faster so that the impact with the ring causing it to roll off the table makes more sense.

Aside from that, I had a crack at giving the balls a little more weight and personality by squashing the red one as it pulls back and stretching it as it lunges forward, to give it a bit of strength. I think the impact of the peg with the blue ball has a little more kick as a result! I'm relatively satisfied with the path of the ball down the slide itself, aside from the aforementioned speed issue.

The next major thing is to get the ball to roll off the table and look at giving it a bit of bounce as it rolls away. Then I can go back and start manually tweaking the inbetweens to create breakdowns and ensure that the path of the ball is as natural as possible.