Hi,
I just wanted to say, don't be tempted to use the Curves.Set method. It's really handy for editing individual subcurves, but will cause a memory leak and imminent crash of XSI if you use it as part of a SCOP (that's as of version 6.02).
Good luck.
---------- Forwarded message ----------
From: "David Barosin" <
dbaro...(at)gmail.com>
Date: Apr 2, 6:08 pm
Subject: Curve creation using geometry.set
To: XSI Mailing List Archive
Brad!!! Thanks man. I've been able to make the get/set thing to work but
it's a little murky when I try to produce the curve argument data myself.
I'm ultimately trying to create a scripted op that will read external curve
data from a file and build it on the fly in XSI. I was thinking that the
geometry.set method would be ideal since it's a one stop drop of data and
the number of curves in the curveList will vary from frame to frame.
