Hoo boy.  A 1000 link chain took about ten minutes to generate and grabbed 35% of my RAM, failing to release it at the end of the run.  The resulting .obz file is 4.5 MB, as is the uncompressed .cr2 for the chain.  Poser is slightly slow in responding to camera changes once the long chain has been loaded, and the entire chain can't be displayed onscreen at one time without pulling back too far to be able to see what it actually is.

So.  Obviously I need to try to optimize the process and do some junk-cleaning.  I'm being cavalier about the data which is being processed by the script, and I'm not cleaning all of it up as I go and releasing the RAM.  It might help to write the files as they're built up, too, rather than compiling them fully then writing the whole thing at once.

I think it's fairly evident, as well, that a 1000-link chain isn't really a practical figure in Poser.  :lol:

Edit: When I removed the 1000-link figure from my scene, 10% of my RAM was released.  Poser was using all of that just to keep the figure passively loaded in memory.  Yikes!  :scary:

===========================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.