robcat2075

A week to go! There is still time to put your entry together!

I did a little experimenting and found that an expression in the form of... AtFrame(GetFrame(),..|..|Translate.X) ... does create a "Missing a Right Parenthesis" error even though they appear to match.

David has a page of tuts on expression that may be instructive...

It is easy to get it wrong because the paths are so complicated. Our resident expert on expressions is David Simmons (it'sjustme). Drop him a message see if you can get him to look in on this.

He's supposed to have three little finger at the wrist. I'm just going to do two. I've hooked in three splines... ... to accommodate stitching in two spline rings. I extrude those out to start making fingers. I wonder what they do with them?

I would set the bone to "Euler" rotation and use the Z rotation channel since that will produce little visible motion of the bone and yet the curve would still be viewable in the same window. There is a function in Expressions that lets you retrieve values for a parameter for any previous or future frame. something like this Z rotation = ((previous frame z translation - current frame z translation) - (current frame z translation - next frame z translation) ) * some scaling factor

I think you could do that now. Since you only need the Z translation channel, a non-relevant channel on the same bone could be given an expression that calculates the acceleration.

Stitch in a loop from which a wing will be extruded... I added a couple CPs near the front edge so i can define the shape of the bone inside the skin better... Now I can extrude that loop out to make the patches for the wing... This theory of the wing flap is thought to be inaccurate today, but I'll do it because it's iconic... extra CPs for knobbier joints...

Steffen seems to have fixed this. I was able to load and render with the two sample plugins you had in the bug report. Keep your eyes peeled for v19k when it becomes available. Thanks for discovering the issue, Roger!

Try this... clip4900BoneMotiontoPoseSlider.mov

What is the origin of the tool you use to extract Pose slider data into a format for your "actuators" to use? Did you write it? Someone in your company? Is it a plugin that works in A:M or something that works on a saved file?

scenes from un-aired pilot for a TV series starring William Schallert and trouble-making cartoon character named "Philbert." This was primarily a project of Friz Freleng. Live action directed by Richard Donner, later of "The Omen," "Superman" and "Lethal Weapon" fame.

Charles, The above technique causes the Pose slider to move with the bone motion but it doesn't create an actual data channel of key frames for the Pose slider. If that is a problem, I have a solution.

Still two weeks to go for Prehistoric! Here is another Prehistoric tip...

try this... clip4894GimbalExpression.mov

Tell me if I'm getting this... clip4891GimbalBakingA.mov

there should be a straightforward solution. i can almost taste it. To summarize: you want the linear motion of Act_Target_Left and Act_Target_Right to be mirrored in the motion of posesliders? Was doing that with expressions not working?

It sure is a tiny body for such a large head. Now that i look at this I realize I've got the neck attached to the head wrong. It's good i didn't spend time trying to perfectly attach it yet.

Do you mean rotation? If you just need to tie a pose slider to the rotation of a bone, that is smartskin. You can link anything that can be keyframed to the rotation of a bone.

We should probably try to reproduce that for a bug report. Steffen has fixed the expressions crash for v19k

It's just plain big. This is like something Orson Welles would do. Background for "Super-Rabbit" (1943)

Charles, try this... clip4869BoneMotionDrivePoseSlider.mov

Have you tried a Reset All settings?

Hi Charles, What other motion does the bone1 have, beside moving from -5 to +10? There are probably several ways to link the pose slider to bone motion.

You might test out the expression-making process in v19e. I only tried it in v19j. Maybe it still works in v19e?