Quote - *"You seem reluctant to accept that minor...."

*No, I don't mean to seem that way.  Sorry.  Last night I had some thoughts and I wanted to voice them.  You've responded to them well, but where an idea was overlooked I sought clarification.  I'm trying to learn what's a realistic concern and what isn't.  You've helped me a lot with that, but, as you know, I'm not quite there yet.  :-P  So I keep asking.

Ok, understood :).

Quote - *"There's nothing wrong with this - it's expected behaivior."

*That's kind of where I miss out, I think.  A lot of expected behavior seems to really surprise me.  Still learning.  :-P  Is there any other expected behavior that might set me off on tangents?  So far we have the lumpy morphs and the body part edge thing.  What other hypothetical cases could there be?

Hmmm.. probably too hard to say, until we run across them.  I'm normally pretty good about anticipating areas of potential confusion, but I do take some things for granted that might not always be clearly stated.  I'm also generally pretty good with 'instinct' about whether or how something might work, but generally don't know the details until I sit down and think it through, so I'm not always prompt in explaining my reasoning behind something.  In addition to both of those, is the fact that some of this stuff comes as a surprise to me too .

Quote - *"Cool beans! I look forward to seeing that."

*The simple Laplacian (I almost called it 'Lamarckian' - heh) smoothing being applied has at least one known issue.  It can have trouble with concave polys, in which it ends up worsening the concavity or behaving in ways that might seem surprising.  I saw evidence of this in the inner eye region with my test, after a couple of smoothing passes.  So it will need some type of screening or restricted selection to be applied effectively.

There are better smoothing algorithms.  I'm not sure whether I can figure them out, though.  Once I have this set up, I'll look at the other examples I have.  In the meantime, I have averaging and this....

If needed, we can come up with some screening for concave polygons (I assume you mean concave polygons and not non-planar polygons... right?  Either way, we can screen for them, but I'd need to know which you mean).

Quote - *"The fix/solution is to start looking at the next actor in line, where an intersection can take place."

*What are the implications for the datafile format?  Just so's I know what may be coming down the pike.  I don't want to commit too fully to developing various ideas if basics may still change....

The only implications for the datafile format would be if we intended to merge multi-actor data into one file.  In that case, I'd recommend what I proposed the other day.. new actors: records, separating sets of weight records.  If we keep the files separate, then ther is no change that I know of. 

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.