Creating Torerego

2009-12-28T00:02:00.000-08:00

First comments

2009-09-28T03:18:00.000-07:00

Mortens first general comments where:

-sort of works nicely.
-needs to be pumped up!
-More epic and more Ego

Although very general, these comments are great because it says with other words:
-the story its on its good way
-need some changes.....but always for the better. And the changes happens within the current framework.

So there is no need to rethink the story, just to pump up the content more. And the best part, Morten will do a lot of it, since he comes in with a fresh eye. :) Im looking forward to this!

To be continued soon!

2009-09-26T01:25:00.000-07:00

First pass of animatic finished! HOH!
I originally planned to do it in one week, i guess work, moving from spain (through sweden and then to norway) sort of got in the way.

So the animatic is now in the hand of my dear friend Morten who is going to rough it up again fix faults, make it more interesting critique my choices etc etc etc.
It weights in on 1:12 minutes and is accompanied by the infamous malagueña song played on guitar. Just what i like.
Here are some rough shots without revealing too much information.

Now i need to start thinking about actually MODEL the sets and shade them. As these layout-sets will not work very well rendered.
Also, after playing around with Softimage i have considered converting my torero over to that software as its quicker, more stable, has a channelbox and very very good rigging-tools

Lets see.

Updates

2009-09-17T03:50:00.000-07:00

Ooups! sorry about the updates. things have been rather hectic as of late. I have been working at a marvellous company in stockholm called swiss...and recently signed on for a project in animal logic.
But there is stuff to come!

Animatic

2009-07-14T07:51:00.001-07:00

It has been silent for nearly two weeks now. I am working on the animatic, and i see very little point in updating a lot before that part is finished.
Animatic is a great way to test out the the rig i have made so far and there are a number of fixes that needs to be done. Also to the current scene-set.

Versions of the Rig

2009-07-04T12:46:00.001-07:00

I have, after heavy pressure from morten made some scripts and versions of the rig for:
proxy
Lowres
Highres
(I will post the scripts here later on, when they hasve proven to work 100%)

Still a long way to go on the skinning-part. But its looking up.
You know you are NOT done if the model still looks best in t-pose.

Animatic

2009-07-03T11:34:00.000-07:00

Finally starting doing animatics while also testing the rigs and I can already see now that its going to require a lot more tuning. (look at the armpit for this position, not too nice deformations)
Morten is intensly working on the music, but finally things seems to be moving a tad faster.

Editing!

2009-07-03T04:58:00.001-07:00

Meanwhile i am doing my rigging. My good friend Morten Overlie has come to visit me here in Spain to do a little editing of my shortmovie in-between the sangrias he has promised to consume. In vast quantities.

Hopefully I can release parts of the first animatic-sessions here on the blog.
The animatic will be done entirely in 3d as i see little point in starting drawing/scanning/editing pictures when the entire process is so quick in 3d.

Corrective morph-system

2009-06-26T08:42:00.000-07:00

Sometimes. Most of the time. Two morphtargets will not play friends. Meaning that together they move same points in [X,Y,Z] When both are triggered the points get a double-translation that ends in PURE UGLINESS.
To ensure that the result is better, we apply a third morph that fixes the result
This morph is dedicated to only fix this coincidene and is called a corrective-morph

Morph1 + Morph2 = ugly
Morph1 + Morph2 +correction = nice

UGLY----->NICER

Thats all nice.
The problem i had was how to make this system automatic.
When the two morphs are triggered together i wanted a percentage of the third morph to be triggered. Doesnt sound hard? We are actually talking here about two values controlling one value. And there is no multiply/divide-node in max.
The resulting math would look something like this:

Morph1*morph2 = value of correctivemorph/2
But where to write this in max?

So i decided on fixing it on the face-gui level.

The yellow dot is the controller. When moved along Y. it triggers morph1. Along X, Morph2.
Since the extenct of values are [1,1] the diagonal would have to be 45-degrees.
So if i made a another "invisible shape"(the grey rectangle inside the yellow dot) 45 degrees on the controller...its local-axis X would always be defined by the controllers XY. Perfect. One value derived from TWO values.
Pointconstrain the "invisible shape" to the controller and voila!
This localX was easy enough to use to trigger the corrective morph through a ExposeTransform-node.

More Morphs

2009-06-25T10:23:00.000-07:00

Shifting volume around can be tedious. but after a while it becomes rather meditative. And you keep moving point/vertices around untill its looking good. :)
This is the mesh that is going to be the morph-target for the inner part of the eyebrow...moving down.

the eyebrow is divided into three. Inner, middle, outer. They have to move: up, down, left, right.
And since the system needs to be on both sides we get
3*4*2=24 morphs just for the eyebrows. Luckily its easy to flip the geomitry over to the right side with the new polygon tools in max.
That little toolbox there with looptools (curve and straight) really makes my day.

Scripts scripts scripts

2009-06-24T23:42:00.000-07:00

I am a beginner scripter. I am really new to it all.
But they are a great way to save you loads of work.

Here is an example:
15 bones are running down each arm the torero. I want them to be maya-style/tendons so i can easily pull them off the rig and make nice arcs etc etc.
That would take me half an hour of quite repetitious clicking/selection/applying/aligning.

Here is a script that does it in one second. It could probably be written nicer and use FN()-functions for some of the things. But it works great!

AxisPointArray=#()
BoneArray =#()
join BoneArray $Selection

for i=1 to BoneArray.count do
(
PositionPoint = point()
PositionPoint.box = true
PositionPoint.size = 8
PositionPoint.wirecolor = color 0 255 0
PositionPoint.transform = BoneArray[i].transform
PositionPoint.name = "Position_" + BoneArray[i].name
join PositionPointArray PositionPoint
)

for i=1 to BoneArray.count do
(
AxisPoint = point()
AxisPoint.box = true
AxisPoint.size = 8
AxisPoint.wirecolor = color 0 255 0
AxisPoint.transform = BoneArray[i].transform
AxisPoint.name = "Axis_" + BoneArray[i].name
in coordsys local move Axispoint [0,0,8]
join AxisPointArray AxisPoint
AxisPoint.Parent = PositionPointArray[i]
)

for i =1 to BoneArray.count do
(
--BoneArray[i].position.controller = position_XYZ ()
BoneArray[i].position.controller = position_list ()
MyposConst = Position_Constraint ()
MyposConst.appendtarget PositionPointArray[i] 50
BoneArray[i].pos.controller.Available.controller = MyposConst

)
for i=1 to BoneArray.count-1 do
(
Aimer= lookat_constraint()
BoneArray[i].rotation.controller = Aimer
BoneArray[i].rotation.controller.constraints.appendtarget PositionPointArray[i+1] 50
Aimer.lookat_vector_length = 0
Aimer.PickUpNode = AxisPointArray[i]
Aimer.upnode_world = false
)
-------------------------
------------------------
And here is what the script does :
Adds the green points to the correct-places and binds the bones to the green points.

NamingConventions

2009-06-24T15:01:00.000-07:00

Some quick thoughts on naming-conventions for objects in the scene.
Right now, my torero-scene consists of 1199(!) induvidual objects. Each of those has a purpose and a lot of time it can be hard digging after then in the viewport. Or maybe i need to access them through scripts.
So I used a naming-convention that goes like this: (in this case the controller for the left shoulder) All in studleyCaps

-ToreroCtrlShoulderLeft
1. The charactername
2. What type of object
3. What part of the torero
4. What side of the torero, unless its an object on the mid-axis. e.g.Spine.

-ToreroBonePinky04Left
Here is another example to show numbering. I have many bones running along each digit of the hand of ther torero...and I number them BEFORE i write "Left". No real reason. I just think its less messy.

A great tool for mass-renaming is wahooney´s rename tool (he has lots of great script)
head over to www.wahooney.org for more :)
True, max comes with a mass-rename tool already, but wahooneys just have tons more flexibility

MorphTargets

2009-06-24T14:14:00.000-07:00

This is the peak of tediousness ;)
To be able to animate the face of the torero i chose finally to rely on morphtargets.
Morphs are "tweaked" versions of the object. A target-mesh so to speak. When i drag a slider, i want the toreros face to go towards that target-mesh

Originally i planned doing this more parametrically by rather skinning the lips etc to point that where floating over a nurbssurface to always retain volume and art-direction... but i costed more than it tasted in the end. Specially since max is operating with a somewhat outdated (hah! its a decade old, for sure!) morph-system. I ended up having nightmare about points not moving linearly in XYZ-space. And i wasted two good days.
-lesson learned: The way that is best is the way that works.

(a third of the shapes needed)
One shape just tweaks a little exclusive part
of the face. e.g.
-upperlip-upwards
-eyelid-down
-Eyebrow-inwards
etc etc etc.

this picture shows the facial-control-panel(!)
in action. Those small yellow dots represents a
specific area of the face. When they move, the
corresponding area shapes with that movement.

2009-06-24T03:51:00.000-07:00

Here is a quick view back in time from when I was modelling the head of The torero.
So much fun! :)

The Rig

2009-06-24T03:13:00.000-07:00

This system took me a while. I must make my own rigscript for the next time around so i dont have to repeat this prosess anymore. Its the fifth time i make rigs, and the process isnt becoming more fun. just more tedious as my ambitions grows.

For those you who are not "techy". A rig is a skeleton that drives the virtual puppet. Those colorful-curves that seems to be floating around is the "controllers" that the animator grabs to animate. They in turn drive the skeleton.

For those of you who ARE techy:
-i wanted to try out a couple of new things on this rig. The elbow consisting of multiple joints was one of them. So i could have more or less the same volume in his elbow while bending the arm.
The same technique is applied to the shoulders and i am very very happy with how the deformations turned out. There was no need for additional skinmorphs in the shoulder-area (armpits not included...they were another story..)

(Click on image for a larger view)

to do list on the rig:
-finish facial-rig
-fix some bloody twist-bone-errors on the upper-legs
-fix the jacket with morphs or something while rotating chest to the sides and forward

2009-06-24T02:51:00.000-07:00

Here are some images of the model:

(click on images for a larger view)

And i found some OLD drawings as well :P

Here are some images of the set i am modelling(no colors yet!):
The dressing-room is located in a quite luxurious "hall" in the back-end of the Arena.
On the podium is where the mirror is located and most of those 40 seconds will be viewed THROUGH the mirror.

(some "details" :P)

Torerego Just got its own BLOG

2009-06-24T02:43:00.000-07:00

Hi, My name is Stein Lotveit. I am a Norwegian animator currently living in Madrid.
Between projects and work I try make my a shortfilm that is called "Torerego".
This blog is to serve as a production-diary and also function as a mean to push myself to work harder and publish my progress :)

About Torerego:
Torerego is going to approx. 40 seconds (wow, that IS short). The film is about a Torero in a dressing-room. The medium for the film is Animation done on computer.
I want to make the quality as high as possible, So its still going to take quite a while to finish.
At the time of writing the project i have completed:

-modelling character
-75% finished character-rig
-modelling 1 set

yet to complete:
-story-editing
-rig
-texturing
-shading
-animation
-lighting
-Image-postProduction
-sound