robcat2075

A reminder to those of you who think you're already done... record that commentary track! It will be fun!

I see one possibly bad CP (more than 4 corners) near the upper corner of the door opening.

I forgot the screen capture

Welcome to the forum! Presuming that you've made your decals so that they are all the same dimensions and would normally align if applied exactly...it's easy to apply them exactly! Apply one decal in the normal manner, then drag any additional images that need to line up with it from the Images folder at the top of the PWS to the Images folder under the decals folder for your model. make sure to set the "Type" for each image in the properties for that image. Occasionally it is necessary to close and reopen a model after a operation like this to get them all recognized. Normally only Color and sometimes Transparency are visible in real-time mode.

You can use a high JPG setting like 85%. that looks pretty much uncompressed for most purposes and won't be too large. I haven't gotten around to downloading anyone's yet, I've been otherwise occupied.

drop box will probably work fine since i don't have to sign up for anything to download. I think the top of the thread mentioned to render it to a JPG series, right?

One alternative to hiding things with transparency is to hide them by scaling. Scale a part to 0% in a pose.

See if you have stereo and multi-pass on. What does a regular render do?

Run two instances and open the task manager. Go to the Processes tab and on one instance of master.exe and "Set Affinity" to CPU 0 then do that for the other instance of master.exe and "Set Affinity" to CPU 1. Try it. try the tutorial that Fucher wrote

Does your current OS show more than one core available for the system?

If you're using IK arms, check if there are any keys on FK arm bones. Those can probably be deleted.

You can read a bit about Bob (one of our TWO directors) Taylor's involvement with "Goof Troop" in this animator blog post: Part 1 Part 2

You mean on this scene, right? or overclock the one you have. almost always, calculating particles will use more (not obvious excepton long prerolls), "finding Patches" does too i think. Multiple instance seems to be gone. Use the Netrender now.

Hard to diagnose just from a verbal description. My first wild guess... Is IK turned on in the Actions? Try deleting that key from all the actions and turning it on in the chor action at the start of the chor. Or, have only the actions turn it on and dont' have a key for that inthe chor action.

You're welcome. I'm happy you're happy to be happy using TSM2.

New life for an old tut! I don't even remember what's in it. I hope it was good.

I've only scanned this thread so maybe this has been mentioned already but... a fast way to set default interpolation on many bones at once is to CTRL or SHIFT select them in the PWS, do a bounding box around the curves then do >Curve>InterpolationMethod>choose slope This will affect all keys in the curves that you have not manually set a specific interpolation on (IOW, they are still set to ""default") You can quickly select select a whole range of bones with SHIFT and selecting just the top and bottom ones in the range you want.

I've put a zip with the permission and key in it in the original post. tip: Always save every installer for everything you might ever want to ever use.

For specular highlights to show the rest of the white of the eye will need to not appear full white. If the white of the eye has much ambiance turned on that will compete with the shiny specular highlight. That makes sense - go with more of an off-white then? Possibly. There are some eye tutorials around you might look at for color advice.

For specular highlights to show the rest of the white of the eye will need to not appear full white. If the white of the eye has much ambiance turned on that will compete with the shiny specular highlight.

that's looking cool. It's interesting to compare yours and the drawing and try to ascertain what makes them look different. A thicker lip on the eyelid would match the drawing more.

That definitely helps since one picture is just a flattened representation of a not-flat object. A front view of a face tells you how far up or down an ear is but doesn't tell you how far back the ear is. That's what the side view tells you. Good rotoscopes need to match very closely. A front and side view should show the same vertical distances for features. A front and top view should show the same horizontal distances for features. Fortunately A:M allows you to move and scale rotoscope images to help them match up. It's also important to get images with as little perspective distortion as possible. The farther away the camera is from an object the less perspective distortion there will be.

I'll just note that the Technical reference (free on pdf) covers almost every detail of A:M. It's not a gripping read, but the facts are in there. Also HomeSlice has made a wiki that I can't find a link to at the moment to that explains every parameter in A:M. Look for that too. Edit: http://www.hash.com/forums/index.php?showt...2&hl=tiddly

16 - I counted frames and he was doing two steps in 12 frames. so something is more compressed than you thought it was. I was just trying to ascertain what part of what you had was the part you didn't like. Since the 12 frames per two steps is the speed you want and the foot sliding is insignificant, I'm back to square one on not being sure what you are unhappy with since this is very close to your original chor's result. ? In all three chors i used your original 20 frame action cycle. It's really 20 frames not 22 frames when the overall action loops. I slightly modified the keyframes on the foot targets so when they are on the ground they are moving at a constant speed with no variation. In "Treadmill" walk or run cycles the ground is moving at a constant speed so the feet must be keyed to move likewise. I didn't fix the problem with the two feet moving different distances. Normally you would have them travel same in a treadmill cycle. Normally you would use an action like that with a path constraint to make A:M handle the problem of matching the prgress thru the animated cycle versus the character's progress over the ground. But it is possible to do as you have done and manually move the charcter forward while he cycles thru his action. I had to experiment to find how far 7(?) cycles of foot steps should carry him. If you look at the properties for "Shortcut to Runcycle" on the Thoms in each chor you will see that "Crop Range" is the same in each case: 0:00 to 0:20. Crop Range allows you to set what part of a cycle gets used by a character. I changed that from A:M's auto guess of 0:00 to 0:22 I set "Cycle length" different in each chor. Cycle length allows you to set how fast A:M interpolates thru the action contained in the crop range. This is where the "scaling" is happening. You can guess what "repeat" controls. "Chor Range" alters automatically based on what "repeat" and "Cycle Length" multiply out to. In the chor Thom has only a keyframe on his model bone at the start and end of his travel t move him over the distance of seven cycles. I changed the time of the last keyframe to match the end of the "Chor Range" time. Modify your 20 frame action cycle to make the motion you want and see what the result comes out to be in the chor where it is applied. I ideally if You knew in advance you wanted 12 frame speed you'd make the original action 12 frames. But... there's more than one way to get to your destination.

He's a cutie! He should have a little toothbrush to hang on his belt.