robcat2075

make an action that keyframes that once and repeat the action in the chor.

a bitmap with stars painted on it, used as a background rotoscope won't take much rendertime. Long ago someone modeled a star sphere that modeled the points of light with tiny patches so the camera could turn to any angle. http://www.hash.com/forums/index.php?s=&am...ost&p=67493 but the link is dead. maybe someone has the file.

You mean you dont' see the wavy channel line? There are two buttons at the bottom of the PWS that choose the view mode. the one with red-green-blue lines turns on the channel view. the next one turns the red-dot keyframe view back on.

Sort of. A typical A:M walk-cycle is really animated as if the character were stationary on a treadmill with the feet sliding backwards. The path constraint is what really moves him forward. it sounds like you understand the essentials now.

you can keyframe "Active" on and off . In the properties for the model bone. But it will take keyframing to do it.

Here's an example of using "ease" to vary the speed of a walk. WalkVary.mov look at the ease channel for the path constraint. Notice how it can make the character slow down, speed up and even walk backwards, all without changing the original walk cycle. The properly animated Walk cycle makes this work without foot slipping. In the second half you can see the effect of an additional chor action that has keyframes on the Hip bone only. Same walk cycle but the new Hip keyframes are "added" to the old motion to alter the character's stance. and here's the PRJ: WalkVary03.zip

Restart A:M. Just curious, does it do this after every kind of render? Or only when you render to Quicktime? to TGA? to AVI?

It sounds like your walk-cycle action doesn't have "has stride length" ON. That makes A:M try to match the progress thru the cycle to match the progress along a path. Almost by definition a cycle is something that is repeated exactly over and over. a "second chor action" would allow you to add keyframes independently of the cycle action to vary the position of bones from where the cycle puts them. I dread meantioning it because it's hard to explain in text here on a forum. Hopefully someone will pop in to do that. As an aside, i'd just mention that if you really need a walk to vary, animating the steps individually is the way it would normally be done, with no cycle at all.

can you show us a "with" and "without"? I didn't even know hair could take a displacement map.

It's so dark I can barely see it, but what i can see looks promising. I suspect your monitor is set to to a gamma standard that 99% of the rest of us aren't set to.

Make sure you turn TSM Constraints ON before you start animating. Then move the bones that you see. There shouldn't be any pose you can't make by moving the visible bones.

TSM2 intentionally hides all the bones it made when you ran Builder and Flipper. They are controlled by the the new bones left visible after Rigger is run. Your screen shot looks normal. The arms are in FK by default and the legs are in IK by default. What bones are you needing to see that you do not see?

select a portion of your model and an "untitled" group will appear under it in the ProjectWorkSpace rename that group then drag your material onto that group in the PWS.

welcome to A:M! one solution is to flatten the path vertically -select the path -open the properties window (ALT-3) -set transform>scale>Y to 0% this flattens it -set transform>translate>Y to 0cm this brings it to ground level you may need to close and reopen the chor for the rabbit to recognize the altered path

there is a button at the top called "Show manipulator properties" when it is on and something is selected, a small display will appear next to your cursor that shows the same properties as in your screencap

That's a good looking cat!

Sorry, didnt' catch your previous post. Right now, I'm already tasked 100% trying to fix TWO scenes. However... Does my sample work on your computer? If it seems to not work then maybe you are doing the simulation wrong. If it doeswork , I'd try transferring that one chain to your head as a test. If it stops working between my sample and your head then you know you made some change. A/B comparisons are all I know to find out the problem. No, it isn't quick. If it does work on your head, then I'd look to see what is different between my chain and your chain. Or... try duplicating my simple test case from scratch on your computer. Does it work or not? If my sample worked for you but your duplication doesn't then that means your' skipping something. Let me know what you find out.

A talking Acorn! You'll need to add some new CPs to splice the mouth in yellow dots are new CPs blue lines are new splines connecting CPs green dots are "hooks" (where a spline is dead-ended onto another spline without using a CP. TAoA:M explains them in one of the modeling tuts)

Does this happen on any chor you save or just particular ones? As an experiment you might try going to the PWS and dragging the important things from the bad chor into a new blank chor and save that. (Do I need to say this should be a new file name?). If you do them one at a time you may find that one particular element is causing the problem. If you've been saving versions of your work it's possible to test which one is the first to have the save problem, then use a text editor to compare that and the previous version for signs of obvious weirdness.

-What does he do when the weapon chooser ends up on "cake frosting dispenser"? -"Smart power-moves for longer lasting" has the slight air of Google Translate to it.

alpha channels are easy to do, but really hard to explain. I'll let these guys try: http://www.am-guide.com/TinCan/AM_&_Alpha.htm http://www.ypoart.com/tutorials/alpha/fundamentals.php

The fire tut in TAoA:M shows the essentials of varying particle properties over their lifetime. you'd use sprite paritcles instead of streak particles. creating the cloudlet would be a photoshop job. It will need an alpha channel to hide the square edges.

make a small cartoon drawing of a cloudlet and use that as a spriticle. Make a particle emitter spew them out and have them grow so they just about cover the flailing arms and then fade out.

no, it wont' work on the current OS. Guess you'll have to figure out what went wrong on AM2001

TAoA:M exercise 16 show how to make fire There's also a sample explosion project on the CD>Data>Projects>Particles