robcat2075

You got the IK hands figured out, right? Those last two stills look very dark here. Here's some notes on the shot. Ilidrakeshot3_4.mov

Well, without seeing it, I'd still say robots are the prime candidate for Holmes' suggestion:

Show a picture of it.

The work-around, when going to render, seems to be to load the scene fresh and not scrub the time slider. Just load it and render and then it comes out OK.

Here's an example I just got in rendering These are from an image sequence rendered by two instances of A:M. the first instance was producing not-good splines and the second instance was producing good splines. Exact same pose in each frame but two different results. splinejitter.mov

Imposters!

It's something more than a refresh issue because it will be visible after teh screen is redrawn for each new frame. I should note that this isn't something I'm getting during spline or muscle mode animation, this is in regular moving bones around animation. My suspicion is that it happens on CPs that weighted to more than one bone but that's just a theory.

Occasionally when I'm animating the splines on my model will stop smoothly interpolating thru their CPs. Suppose several patches are twisted then straightened out. The CPs move to their correct places but the splines going thru them don't' quite adjust right it's as if the angles of intersection has frozen. like this. I've marked the corresponding angles with red green and blue arcs. So far, saving and reloading is the only sure remedy. Anyone seen this and know what causes it?

Quicktime has great compression and almost everyone has it.

Rendering_an_image_sequence_to_a_movie.mov

Seeing that picture of the real wood object makes me want to try to get that look with A:M.

15J+ CD version, running on Windows 7 I got exceedingly few crashes with v15 and I did lots with cloth. If you got something you can repeat... make an AM Report on it. And if you're on the v15 subscription version you can be trying the v16 beta.

Funny movie!

Exporter corrector? It worked for me on the first try. Here's an OBJ I made in Wings imported as an OBJ into A:M v11.1i running on Win 7 WingsOBJTest01__2_.zip If what you are trying to import is so complex that you don't want to remodel it in A:M it's probably got a lot of polygons.

No, only the first chor action "needed" to change the color. However, when you "show more than drivers" to see "Groups" and then try to set a color there, it makes a difference whether chor action 1 or 2 is active even though you're not clicking on anything in either one. After you set that group color a channel representing what you have done also gets created in the chor action that was active. I didn't make a Pose to change the color since I didn't want to save a new version of the character to preserve the pose. Changing the color in the chor avoids altering the character file.

What version are you using? Help>About Animation:Master... what version does it say?

After some backtracking through the previous versions of this PRJ (there's only 378 of them) I find that the problem surfaces after I added second chor action to Shaggy. If that chor action has the green "active" check mark next to it when i try to change the color on a group i get the odd result. If I have the original chor action active when i try to make the change I get normal behavior. The second chor action was set to "Add" So this probably isn't a "bug" as much as A:M trying to accommodate two competing influences on the same element.

I'm wanting to change the color of a group on a model, in the chor. When i click on the color chip no color i set gets accepted and the RGB channels for the color do not resemble the values shown in the color picker. The red and green are actually below zero. Is there a good reason these are not corresponding to the color picker? I dimly recall seeing something like this a long time ago but don't recall if it was intended or not.

That turned out well! I'm wondering about the flesh colored flaps on her hips... what are those?

Camera Mapping, actually applying the image as a decal while looking through the camera, is the way to get the image to stick after the camera moves to a new location. Front projection/rotoscope can't do that.

It works in v15 for me

An object is in your camera view.... Select the object in the Objects folder and >New>Decal The decal will appear in the camera view for you to position and apply on the object. The bounding box is very jittery in this view. Drag an image onto a light and the light will project the image like a slide projector. Good also for making non-circular light patterns.

Really, really, really close now. Mark, how are those shadows doing?

High powered!

I'm trying the Stanford Bunny OBJ right now and, yeah, Windows says "Not responding" but I've done it before and I know if I wait long enough a bunny will show up. Try something over night. Once you resave it as MDL it doesn't take so long to load. Just to make sure it's an A:M readable file try importing it as a polygon "prop" first Be warned that anything over about 10,000 patches in A:M is asking for very tedious waits when editing splines.