> Quote - OK, I'll do a cr2. It may be too big to post in the thread, so can you IM me with an email address to send it to? When you say "containing only the basic information for a chain?" could you elaborate a bit on what you mean by that? Do you mean a skeleton with only the bits that would change with each link?

I think just a basic template with two or three links, showing the ideal origin, endpoint, and orientation.  It doesn't need to be a working .cr2 which could function in Poser.  Just something I can try to study to (hopefully) figure out how to approach this idea.  I don't think the "figure" section or the geometry listings would be needed, unless there are any chain-related peculiarities which would fall there.  Maybe a couple of sample links, as well, so I can judge how the joint positions relate to the geometry scale, and how the pices fit together.  If all of this can't be attached as a ".zip as .txt" in a forum post, I'll PM you with an e-mail.  :thumbupboth:

Here's a bugfix for the update I just posted.  This one seems to be stacking as intended, along whatever axis represents the local Y for the plane.  I expected localspace translation, prob'ly because I was thinking about the scaling along local axes which was set up yesterday.  :lol: 

Quote - I'll keep this version, one man's bug is another man's feature!

I generally think that way myself, actually!  :lol:  Not everyone appreciates that reasoning, however, I've found.  :sad:

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.