robcat2075

I detect a tiny bit of sliding there. Make sure the keyframes at the beginning and end of a foot-on-the-ground portion are zero-sloped so the foot isn't wandering in between. And of course make sure the beginning and end are really in the same spot or the foot will still be moving as it tries to transition from one to the other.

I can't because, even though i made my own, the school only wants AnimationMentor students to use their characters. It was an extremely basic character and really just a stick figure, however. You can make one better in A:M!

Nic3e models! I thought that was maybe your photo reference image until i clicked on it. I'm not sure where the mirror is there. Is it in front of the book shelf looking thing? Normally you'd just leave the "surface" of a mirror as white. Are you wanting a dark mirror?

Glad to have you around, Paul! Happy Birthday!

Thanks, Nancy! I wonder what goes on internally that makes the reversed map come out differently. I don't think that gets you anything since Displacement relies on bump-style shading for its shading (shhh, dont' tell anyone it's a trick!). It uses the displacement map twice, once to elevate the surface and once to give it a shaded appearance.

These two coins have displacement maps on them with similar settings. Both maps attempt to create details raised above the main surface. The top one with the simple bumps on it shades as expected for the light coming from above the camera's left shoulder. The more complex one, with the monkey image, has a varied result with different details seeming to be lit from different directions. Does anyone know why? DisplacementTest.zip

About seven years ago they took down their six-foot fence and put up a nine-foot fence. Umm...There wouldn't be any razor wire on top as well? perhaps? And is it surrounding a large concrete "mansion"? Interesting true fact... in 15 years I have never seen them put out any garbage.

Normally the ambiance shoudl be 0 for such a use. An object with ambiance 100% on might appear bright white. If you can post the PRJ and image, that will, of course, speed diagnosis up.

I've voted several times! I'm sure others have too.

is a surface set to 100% ambiance?

About seven years ago they took down their six-foot fence and put up a nine-foot fence.

As Matt says, you'll need the leg or foot to be able to turn a bit independent of the body direction. You really can't do good turns while using a repeating walk cycle. This will work when you are animating each step separately as I showed you before: RobotTurn.mov (The audio may not play if this movie is played in a browser. In general, t's best to download all QuickTimes and play them in the QT Player.)

Yay!

I get it too. Has someone AMreported this?

You can thank Rafael Anzovin for that one. So... mysteries solved? Why is that clip a minute long? You didn't really render a whole minute did you?

Can other values be moved past 16,000 reliably? Like an X translate?

I looked at the behavior in V13 a bit more closely and noticed that the rotation values increment as expected to about 15900 degrees and then at 15:28 flip down to about -15900 and continue to increment from there. There is a noticeable jump inthe bone rotation at the switch. I presume some sort of value limit is being exceeded in a variable. V13's behavior is probably more "wrong" but gave the appearance of working past 16 seconds. It occurs to me that this may not be truly solvable since there's no variable type that's truly infinite in range yet would have the precision needed to represent the rotation accurately. Or is there?

None have ever been found. Not in this century, nor in the last. Not in this universe nor any other.

And remember to turn off the auto balance stuff in Knight.

I've been getting this pretty commonly since v15 (maybe even before that). I have seen that since ver 14, but also don't worry about it, since it renders fine. Noticed it while working on TWO, specifically the hypogyraf. If someone could construct a case that looks better in V13 than in V16 that would probably tell a lot.

I looked at the behavior in V13 a bit more closely and noticed that the rotation values increment as expected to about 15900 degrees and then at 15:28 flip down to about -15900 and continue to increment from there. There is a noticeable jump inthe bone rotation at the switch. I presume some sort of value limit is being exceeded in a variable. V13's behavior is probably more "wrong" but gave the appearance of working past 16 seconds.

I get the same behavior as you so i put in an AM report.

I don't get that. My 32-bit A:M boots and a quick run through of TSM2 appears to operate normally.

Can you post a test case? One that shows it worked better in a previous version would be ideal.

Try this and see if it works unzip this to your computer SinfoTest.zip It contains a TGA sequence, a WAV and a .sinfo file Start a new PRJ in A:M import the TGA sequence into the Images folder as an image sequence create a new CHOR drag the image sequence into the camera view, choose "Rotoscope" when asked. It should then ask if you want to "import and link sounds...", choose yes. the CHOR should now have a WAV to match the TGA sequence which appears in the camera view