robcat2075

There is a tech talk... http://www.hash.com/forums/index.php?showtopic=26015

A good book on the strategy of facial animation is Jason Osipa's "Stop Staring" although I don't think the current version covers A:M and the original version wasn't aware of several relevant features in A:M. He has varying levels of need-to-have Some minimums for the mouth would be open "ah" pose, then the sideways stretched "ee" pose, then the "oo" pose and maybe the slightly curled in "mm/b" pose. Then you might add raising and lowering the corners of the mouth for smile/frown. Note that smiles pull back more than up. You want to be able to raise and lower eyebrows and at various angles. You want to be raise an lower the upper and lower eyelids independently to follow eyes looking up or down. Real eyelids are not rigid shells that rotate up and down, they drape over the pupil and the part where the pupil is is pushed a bit wider. Nostril flares? Cheek puffs? maybe. My own preference is to rig most of the face features with bones. Things like jaws, lips and eyelids tend to move around a center point and bones lend themselves to doing that smoothly whereas poses tend to move in straight line fashion from key to key. I find cheeks maddening to do well, to keep the fleshy look as the lips move around. I resort to smart skin to augment the result of my boned lips and jaw.

I see now that the Camera has an "ignore Fog" switch. I presume that will work on the default background color.

Other possibilities are to render at a higher res and scrunch it in post (basically higher anti-aliasing)

If your "sky" is a background object rather than the default camera background color you can set it to "ignore fog" in its properties.

I'm still trying to track this down. Can you point me to the page? The nearest I can find is "Click on the material in the folder to select it." but that one seems specific.

I recall a past problem with multipass motion blur where if, say, it was set to 16 passes it was taking the 16th pass from the previous frame and adding that to the first 15 passes from the current frame, so there would be a slight ghost image one frame out of place. If you can reproduce that problem that would be a good AM report.

I should never use "RMB" because I always have to come back and explain that it is short for "Right Mouse Button"

Does a listing for the second rotoscope at least show up under the model in the PWS? It has some properties and you can choose a "front", "left"... view You can also >New>Rotoscope in a window to add a rotoscope instead of dragging one in.

What didn't work in that?

A generic test of constraining a bone in one model to a bone in another model survived being saved and reopened, so we'll need to know more about your case.

As always... If you can post a sample PRJ that does it, that will make it immensely easier than someone trying to reconstruct it from the description.

I didn't reply because I couldn't even think of a crazy unlikely reason for that problem.

I don't recall that one, where is it?

I have animated smoke that varies the emmission rate so I know it can be done. There's a thread with an example PRJ there... http://www.hash.com/forums/index.php?showt...43&hl=smoke

I have now! I can't tell you how often I've wished you (or anyone else) would have the money to pay to do their rigging.

I wonder if something has changed in Windows to break that? I seem to recall this working in v16 and it doesn't work there either now.

For the moment, use the pdf TechRef. The information is the same in there.

Do you get three topics in the left pane that don't lead to anything else? It looks like it doesn't work in 17g

What are you trying to key?

Is this what you are trying to do? ClothTestSimpleSimmed.prj

I'm glad to hear you are chipping away at it.

That looks cool, Marcos! Good Rigging, Mark!

I look at their new-features video and think, "what? they couldn't handle alpha channels before this?" I'm glad they are on board with that, none-the-less.

As far as optimizing render time... I would be VERY surprised if A:M is not already optimized to spend no unnecessary time on things that will not show in the rendered frame.