robcat2075

A transparency map and a color map will work also. I suppose the advantage of a material is you can pack both the transparency and color into that one material if you wish but it's a minor point if you are more familiar with painting materials.

That looks like Kate Bradley used to have on Petticoat Junction, although i never saw her put any wood into it.

That looks cool.

Motion blur is image-wide. Faster moving things will exhibit more of it. The non-multi-pass version of motion blur has some sort of a threshold of motion, below which it doesn't bother to add any.

I had never thought of trying to weight with mirror mode on. I'm surprised that got any result at all. btw, you can edit weights in an action and the weights will be changed in the model; maybe that's what you were doing but it sounded like you were switching between the model and the action to check the results.

If it always looked great the first time you tried it, everyone would be doing it. Remember to never have one spline end where two other splines are already crossing. And what vertex said... that arm is too low on the torso.

Yay! thanks!

It should still work in 32-bit v16, which you can install and run with your current license.

Those are good looking tree-scapes! I just stumbled upon this thread again after three years.

What did you see?

That looks super! Are you modeling these in A:M or are doing them in an architectural program and importing them?

All the CPs on your spline need to be on one side of the axis before you lathe. No CP can be on the axis nor can it cross over the axis.

That's odd. Try the benchmark project and see what you get.

Before you lathe, select the two CPs at the poles and back them off the axis a pixel or two. They definitely should not cross the axis.

I like what you are doing at the very end where he's giving us a sideways glance What if his head couldn't turn that much and you had to get most of that done with the shoulders? And now that you have the shoulders moving more, I'll note that the torso can't pivot on motionless hips. it's all connected down to the feet. in general if the torso has to lean in one direction , the hips need to move opposite to keep the weight balanced over the feet.

Isolated motion. that's the term I was looking for. I've heard animators call it that, when one part of the body moves and the parts attached to it remain motionless. This is an accepted practice in 2D limited animation. Fred Flinstone's head will nod and turn and talk without his body (on a different cel) moving at all, but the greater realism of our 3D models seems to make that not work for us. I remember watching a critique where a student had a character with its hands gesturing in front of it. When the character leaned forward the hands (IK hands) remained motionless in space as if they were on an invisible hand rail. That's another example of Isolated Motion. Once you notice it, it looks very odd when it happens.

OK, I didn't see the text editor part.

The first time you drop a model in the chor nothing should be appended to the model name. If it is dropped in a second time it will get a (2) after the model name. Are you saying that extra 1 was automatic?

I'm confused now as to whether your project is working now or not working.

On TWO there was a large folder of models and materials and bitmaps made for the movie. Everyone downloaded this folder and it was synched with the original at hash so if one of the assets was updated eventually yours would be too. For that idea to work, the models each had to be saved as their own MDL file and not inside a PRJ. Likewise with actions and materials Animators would import the models they needed into A:M, drop them into their chors, animate, then save the chor only. The chor saved all their keyframing information and links to the models it used, so that the next time the animator loaded the chor it would also load all the models the chor needed. Because everyone had downloaded the same file structure for the assets anyone who had a properly synched folder of assets could also open up someone elses chor and it would properly search out the matching assets in their copy of the folder. The total assets in a TWO chor could be enormous so saving a PRJ with everything embedded would have created unnecessary duplication of the models. I save incremental versions of my work every few minutes over many weeks of work. It would be impractical to resave a copy of EVERYTHING just because I made a few keyframe changes. Also if a Tinwoodman model got updated with different decals later in the production, that new model would be substituted for my old one when i re-synched my folder and I would continue working on with it. With PRJs with everything embedded that substitution wouldn't happen because I wouldn't really be working with a tinwoodman MDL that was synched to the one on the central repository anymore, I'd just be working with a copy of a tinwoodman in a PRJ. Today I save whole PRJs with everything embedded when I want to save the entire working environment of whatever is cooking and not have to worry that a change I make to a model today will break something I did fifty versions ago but might want to return to. Today i save chors if I am certain my asset development is done and all i want to do is drop my models in the chor and animate them. Note that images and audio can never be embedded, they are always external. If you edit one of those used in today's version that change will appear in previous versions that used them. You can tell if any asset is NOT embedded in the current PRJ if it has the tiny floppy disk symbol on its icon.

If I had to budget myself to one suggestion it would be that the head can not pivot around on the top of the neck like a gymbal. the head is the last link in a flexible chain that makes up the spine and it all has to come into play to look right. All those head nods and turns you are doing have potential, but the torso and neck need to be part of what is making that head move. It's even physically impossible to move the head without them doing at least a little bit. A mime might be able to isolate the head but in normal everyday action ti's all working together to create expression. There's lots of opportunity between the head and torso for overlapping action to loosen things up and create a more lifelike impression.

Bottom line, embedded or not embedded should not make a difference to a constraint. The only way i can imagine not-embedded models being a problem was if you created a constraint with some external models, saved the chor, then when you reopened it, some other models that happened to have the same names but not necessarily the exact same bones were being loaded instead. However i can't imagine how that situation would be created in the first place.

I know that for TWO we used chors exclusively with all models external and were still able to constrain things to other things.

All I know is that somehow my project worked. i don't actually remember how. rendering it to a black background with no alpha channel and compositing with some other transfer method such as luminosity might be useful. Applying a level adjustment could bring out the visibility of the smoke as needed.

extra credit fr the landing gear.