Hey Rob, I'm trying something similar now and having no luck...
I just want to adjust the size of the inset on an Extrude Polygon
Island node based on Self.PolygonArea. However it seems to return 0.
Any tips? Did you manage to get anything working?
DAN
On Thu, Aug 9, 2012 at 5:35 PM, Rob
Hi Dan,
not possible Im afraid as that inset is global per object whereas
polygon_area is per polygon context. If you treated each
extrude independently with an repeat node then it is possible but a pain
jumping through contexts. I think I ended up getting the needed polygon
selecting
Hi Adam
In the create Strand node, It might fix your problem if you tick on reverse
strand direction.
Thanks
Ben
On 22 October 2012 17:54, Adam Sale adamfs...@gmail.com wrote:
Dang.. forgot that I had built it in a 2014 Beta..
Here is a link with a similar simple setup for 2012
Thanks Rob,
I was hoping to avoid Repeats in this instance because I have a very
dense mesh... Bummer.
Cheers,
DAN
On Tue, Oct 23, 2012 at 4:41 PM, Rob Chapman tekano@gmail.com wrote:
Hi Dan,
not possible Im afraid as that inset is global per object whereas
polygon_area is per polygon
Here's a modified version of Mr Laforge's compound that does the
extrusion length and inset based on polygon area. Yeah, it uses a Repeat.
http://xsisupport.files.wordpress.com/2012/10/extrusion-by-area.png
On 23/10/2012 11:47 AM, Dan Yargici wrote:
Thanks Rob,
I was hoping to avoid
Hi, short question:
how do I set/write the ICEAttribute.DataArray from JScript? Can't find a
code example.
It is a safe array, that much I found out.
attr.DataArray = [23,44,50]; is not working.
// WARNING : 3392 - Invalid offset specified while extracting data from
this attribute...
I have a particularly nasty issue with normals evaluation in Softimage.
There is a method called CGeometryAccessor::GetNodeNormals (C++ SDK)
that evaluates and returns the node normals for the entire geometry.
Automatic normals are computed; user normals (if any are present) take
precedence
this is in the help somewhere, damned if i can find it again.
its python, but will print info about the a selections attributes:
hopefully that helps.
from win32com.client import constants
xsi = Application
#xsi.CreatePrim(Cone, MeshSurface, , )
attrs =
I ran into this problem a few years ago developing a tool. I don't remember
how I resolved it, but try using the GridData object instead of reading/writing
directly to a Jscript array.
GridData.Data = attr.DataArray;
You might have to define one or both dimensions of the GridData object
Hi Kamen,
We hit this bug as well and it has since been confirmed by ADN support
(and logged as SOFT-6862). Note that this bug also occurs in
interactive sessions (not just in xsibatch). We noticed the bug when
we opened scenes with user normals and rendered immediately.
To workaround this
Hi Eugen,
What version are you trying this in? AFAIK, writing ICE attributes is a new
feature in the SDK of SI|2013...
http://download.autodesk.com/global/docs/softimage2013/en_us/sdkguide/files/GUID-177FE97B-99EB-4EF2-A33A-B17811915954.htm
New Methods (Object Model)
-
Thanks, guys!
The Python example I found myself, but that does not help in JScript.
GridData must reside in a CustomProperty, right?
I would have to define one first... not very elegant.
Am 23.10.2012 20:09, schrieb Matt Lind:
I ran into this problem a few years ago developing a tool. I don't
XSI has a big advantage over Maya when creating UVs based on
the Camera.
In Maya2012x64, if you create UVs using the active (persp/cam) view,
you´ll get the UVs *autonormalized* into the 0-1 UV range.
Which is introducing stretch and distortion if all you want is to
create UVs that *align* with
No. Griddata can be made all by itself:
var oGridData = XSIFactory.CreateGridData();
oGridData.Rowcount = n;
oGridData.Data = attr.DataArray;
-Original Message-
From: softimage-boun...@listproc.autodesk.com
Afaik you can create GridData on the fly without attaching it to a PPG:
XSIFactory.CreateGridData();
Search the SDk docs for Using a Temporary GridData Object.
Thanks, guys!
The Python example I found myself, but that does not help in JScript.
GridData must reside in a CustomProperty, right?
From what I observed, if your array is the right size, you will have this
error shown.
The size of the array will depend on the siICENodeContextType associated with
the ICEAttribute and the object containing this ICE Attribute.
--
NewScene(,
I've tried it with both options, still the same behavior for me when I use
it with spawn on collision
On Tue, Oct 23, 2012 at 8:28 AM, Ben Beckett nebbeck...@gmail.com wrote:
Hi Adam
In the create Strand node, It might fix your problem if you tick on
reverse strand direction.
Thanks
Ben
It would seem that my ICE tree is still evaluating after I have cached it and
disconnected all nodes apart from the cache on file node. A workaround I am
using is to make a new empty pointcloud and use that to play back my cache. I
am wondering if anyone has any other workflows for this, and
delete the simulation marker... just ran into some more headaches myself in
regards to caching.
On Tue, Oct 23, 2012 at 6:22 PM, Nick Angus n...@altvfx.com wrote:
It would seem that my ICE tree is still evaluating after I have cached
it and disconnected all nodes apart from the cache on file
Good advice Steve!, works like a charm... Thanks
N
From: softimage-boun...@listproc.autodesk.com
[mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Steven Caron
Sent: Wednesday, 24 October 2012 11:34 AM
To: softimage@listproc.autodesk.com
Subject: Re: ICE cacheing
delete the
20 matches
Mail list logo
