robcat2075

Hey, Tore... Here's a better idea... On Saturday I do "Live Answer Time". People call me on Skype and I look at their problem and try to solve it. Get yourself Skype and you can show me exactly what it is that your other software is doing and what you want A:M to do and I think we can identify the problem very quickly and decide if it's a bug that needs to be reported or if it's just something that needs to be done differently.

I was able to "like" the post without an error message, but I've been able to do that before without errors.

Because it's important to fix the thing that is the actual problem and not spend time on something else that is being referred to by the wrong name. There has to be a yes or no answer to this question at least: Also, in the following software, when you set "Out=60" doesn't that just mean that when you hit Play the program will play the animation onscreen from frame 0 to 60? Or does it mean something different?

Tore, I've read the thread and I'm still not clear on what you are doing that needs the Chor length to be a certain length. Play range affects only the span of the timeline that gets played in real time when you hit the Play button. It has no effect on Render Range. Chor length also has no effect on Render Range. Newton and SimCloth use Chor length to know when to stop a simulation but other than that Chor Length doesn't mean much. Render Range is something you explicitly set in the render panel. Tore... is Render Range what you are really trying to save with your PRJs?

Here I moved the light to show that it's not dependent on the environment lighting

that's the one that's probably a deal-killer for use on cloth where you can't explicitly control the shape. Cloth will get curved and folded. So far, the SSS method is the only way I know of differentiate between front and back of a single thickness surface in any shape...

I dimly recall that my technique was a compositing process. It used the fact that the "wrong" side of patches with SSS on them would render as black to create a matte to composite two renders together.

When you say "Scene length" what do you mean that is different form the Chor "length"? I'll note that in the file, Play Range and Chor length ("Frames") are written as separate values, so they are potentially independent of each other, but there is no "Scene length " parameter.

The reflection thing is weird. Try an image with an image in it, something other than a flat color.

I tried your test PRJ and it does fail to retain the 50 frame setting after a save and reload. What you really want is for the Blue bar (the Chor Length) to stay set at 50 frames after a save and reload, without having to make other workarounds in the chor, right?

That's pretty good.

They're just not in the holiday spirit.

That's quite impressive! Good work and good animation!

Tore... tell me what I'm getting wrong here: clip3869ToresChorLengthQuestion.mov

Tore, in that other software it looks like you are referring to what in A:M is the "Play Range" rather than A:M's Chor "length." I'm not clear on what it is you want to set the "Chor" length for? Tell me what you need that for and i can know what you want better.

Chor Length is typically set to be as long as the last key frame in any object in the chor. Can you present a test case that shows Chor length being lost? Shouldn't shortening the general length of the choreography from say 100 to 50 frames automatically shorten all that choreography's object's actions to maximum 50 frames? No, I don't believe it should. Object Actions have a time span that is independent of the chor length. There would be serious bad side effects if changing the Chor length (which is mostly a nominal value, it doesn't prevent you from rendering any more or less of a chor than the stated length) automatically scaled or chopped Object Action.

Models don't have length setting but their Actions do.

WhatsTheNews... I'll note that a temporary work-around for the sort-order thing is to go to the PWS, go to the chor, and drag "Shortcut to Ground" to the top of the Chor so it is first in the list rather than last.

OK, I don't think it will be long before it goes live. Maybe a few weeks.

There is a tiny drop-down menu at the top right corner of the Reports screen. I guess when you try to switch to v19 on that, there is no "v19" for you? I wasn't gloating, I was just happy to report on this new milestone for A:M. Issue 6631 "Depth Sorting..." is indeed now a v19 issue and is marked as solved and a quick check in the v19 I have indicates it is so.

I'm alpha-testing v19 for the first time today and... i found my first bug!

Sorry to hear about your mother in law, John. Best wishes for you and your family.

Merry Christmas everyone! Here it is... This year's Christmas Greeting: Down on the House top

Nice to see you're still around, Paul!

With all-triangular faces is is impossible to have the ideal intersections of splines where one spline crosses over one other spline and no other splines cross or dead end in that intersection. To shade patches properly from one patch to another, all corners of the patches need to be in that X-intersection form.