Re: ICE modelling - polygon area
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 Chapman tekano@gmail.com wrote: Steve, great! thanks for that, will have a go at implementing the way you have done this, looking at your ICE tree it doesnt look like an obvious solution :) my issue is proving more difficult because each Polygon needs its own radius size depending on a distance to a null and am using a repeat node with the selected poly index array to cycle through each one setting unique values. similar to this http://xsisupport.com/2012/06/07/ice-modeling-extruding-polygons-with-random-lengths/ but further jumping through contexts by trying to set individual polygons pointpositions as well. Have made some progress with a grid (see pic), just stuck when applied to long thin extruded objects in the shot where the polygons are not regular square to begin with and need scaling beforehand. On 9 August 2012 16:15, Stephen Blair stephen.bl...@autodesk.com wrote: I don’t know if this helps, but here’s something similar I was messing around with http://xsisupport.com/2012/08/07/resizing-polygons-with-ice/ From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Rob Chapman Sent: August-09-12 11:12 AM To: softimage@listproc.autodesk.com Subject: Re: ICE modelling - polygon area must be getting close - keep getting this now ' ERROR : 2429 - Access to a custom ICE node index set failed. This can occur when accessing an index set from the BeginEvaluate or EndEvaluate callback. all im trying to do is repeat in an array each selected polygons changes at the point level. ie I want to uniformly scale the polygon around its centre by a radius. whilst it is simple on a single Polygon, http://xsisupport.com/2012/02/09/making-circles-on-the-surface-of-a-mesh/ this is not so easy to get correct context when dealing with an array of polygons where each one is to have an individual radius value. and If I see another Context Mismatch: Input context supported: Per Object or Polygon output context supported: per Point well I guess I will just sigh yet again - this is sooo frustrating!
Re: ICE modelling - polygon area
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 surrounding vertices making these into a circle with the radius as a factor of the original polygon area before extruding. Also Stephen has the most information available i believe on tips tricks with ICE modelling http://xsisupport.com/?s=ice+modelsubmit=Search good luck!, if you get stuck I can try dig out the compound used for the job but pretty much used the example tips and tricks provided by Mr. Blair cheers Rob On 23 October 2012 15:24, Dan Yargici danyarg...@gmail.com wrote: 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 Chapman tekano@gmail.com wrote: Steve, great! thanks for that, will have a go at implementing the way you have done this, looking at your ICE tree it doesnt look like an obvious solution :) my issue is proving more difficult because each Polygon needs its own radius size depending on a distance to a null and am using a repeat node with the selected poly index array to cycle through each one setting unique values. similar to this http://xsisupport.com/2012/06/07/ice-modeling-extruding-polygons-with-random-lengths/ but further jumping through contexts by trying to set individual polygons pointpositions as well. Have made some progress with a grid (see pic), just stuck when applied to long thin extruded objects in the shot where the polygons are not regular square to begin with and need scaling beforehand. On 9 August 2012 16:15, Stephen Blair stephen.bl...@autodesk.com wrote: I don’t know if this helps, but here’s something similar I was messing around with http://xsisupport.com/2012/08/07/resizing-polygons-with-ice/ From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Rob Chapman Sent: August-09-12 11:12 AM To: softimage@listproc.autodesk.com Subject: Re: ICE modelling - polygon area must be getting close - keep getting this now ' ERROR : 2429 - Access to a custom ICE node index set failed. This can occur when accessing an index set from the BeginEvaluate or EndEvaluate callback. all im trying to do is repeat in an array each selected polygons changes at the point level. ie I want to uniformly scale the polygon around its centre by a radius. whilst it is simple on a single Polygon, http://xsisupport.com/2012/02/09/making-circles-on-the-surface-of-a-mesh/ this is not so easy to get correct context when dealing with an array of polygons where each one is to have an individual radius value. and If I see another Context Mismatch: Input context supported: Per Object or Polygon output context supported: per Point well I guess I will just sigh yet again - this is sooo frustrating!
Re: Strands Question
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 https://www.dropbox.com/sh/z8p4v5kkh24fqhg/PlWaklwcbU/Raintest2012.scn Frame 27 is the first instance of this extra tail on the newly spawned blue particles.. Just not remembering how to fix this one.. Thanks for any help.. Adam On Mon, Oct 22, 2012 at 12:47 AM, Thomas Volkmann li...@thomasvolkmann.com wrote: ** Unfortunately the scene crashes at startup... at least on my machine :/ /Thomas Adam Sale adamfs...@gmail.com hat am 22. Oktober 2012 um 05:35 geschrieben: Hey folks, Its been a while since I've used strands, and I recently came across an issue that I can't remember how to fix. Searching archives yields no useful results, as I'm not sure how to frame my query. If I emit Strands from particles ( like rain streaks), and then spawning particles based on collisions with say a grid, the spawned particles inherit the strands, but they have this behavior where the strands are actually ahead of the actual particle from which they are supposed to trail. In the create Strands Dialogue, there is a Reverse Strand direction option, but this doesn't do it. Its easiest to see this on frames 15 and 16 of the dropbox attach. Heres a link to a scene so you can see what I mean.. I feel like this is one of those duh moments... https://www.dropbox.com/sh/z8p4v5kkh24fqhg/hOZ9aew6n9 Thanks for any thoughts.. Adam
Re: ICE modelling - polygon area
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 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 surrounding vertices making these into a circle with the radius as a factor of the original polygon area before extruding. Also Stephen has the most information available i believe on tips tricks with ICE modelling http://xsisupport.com/?s=ice+modelsubmit=Search good luck!, if you get stuck I can try dig out the compound used for the job but pretty much used the example tips and tricks provided by Mr. Blair cheers Rob On 23 October 2012 15:24, Dan Yargici danyarg...@gmail.com wrote: 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 Chapman tekano@gmail.com wrote: Steve, great! thanks for that, will have a go at implementing the way you have done this, looking at your ICE tree it doesnt look like an obvious solution :) my issue is proving more difficult because each Polygon needs its own radius size depending on a distance to a null and am using a repeat node with the selected poly index array to cycle through each one setting unique values. similar to this http://xsisupport.com/2012/06/07/ice-modeling-extruding-polygons-with-random-lengths/ but further jumping through contexts by trying to set individual polygons pointpositions as well. Have made some progress with a grid (see pic), just stuck when applied to long thin extruded objects in the shot where the polygons are not regular square to begin with and need scaling beforehand. On 9 August 2012 16:15, Stephen Blair stephen.bl...@autodesk.com wrote: I don’t know if this helps, but here’s something similar I was messing around with http://xsisupport.com/2012/08/07/resizing-polygons-with-ice/ From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Rob Chapman Sent: August-09-12 11:12 AM To: softimage@listproc.autodesk.com Subject: Re: ICE modelling - polygon area must be getting close - keep getting this now ' ERROR : 2429 - Access to a custom ICE node index set failed. This can occur when accessing an index set from the BeginEvaluate or EndEvaluate callback. all im trying to do is repeat in an array each selected polygons changes at the point level. ie I want to uniformly scale the polygon around its centre by a radius. whilst it is simple on a single Polygon, http://xsisupport.com/2012/02/09/making-circles-on-the-surface-of-a-mesh/ this is not so easy to get correct context when dealing with an array of polygons where each one is to have an individual radius value. and If I see another Context Mismatch: Input context supported: Per Object or Polygon output context supported: per Point well I guess I will just sigh yet again - this is sooo frustrating!
Re: ICE modelling - polygon area
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 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 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 surrounding vertices making these into a circle with the radius as a factor of the original polygon area before extruding. Also Stephen has the most information available i believe on tips tricks with ICE modelling http://xsisupport.com/?s=ice+modelsubmit=Search good luck!, if you get stuck I can try dig out the compound used for the job but pretty much used the example tips and tricks provided by Mr. Blair cheers Rob On 23 October 2012 15:24, Dan Yargici danyarg...@gmail.com wrote: 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 Chapman tekano@gmail.com wrote: Steve, great! thanks for that, will have a go at implementing the way you have done this, looking at your ICE tree it doesnt look like an obvious solution :) my issue is proving more difficult because each Polygon needs its own radius size depending on a distance to a null and am using a repeat node with the selected poly index array to cycle through each one setting unique values. similar to this http://xsisupport.com/2012/06/07/ice-modeling-extruding-polygons-with-random-lengths/ but further jumping through contexts by trying to set individual polygons pointpositions as well. Have made some progress with a grid (see pic), just stuck when applied to long thin extruded objects in the shot where the polygons are not regular square to begin with and need scaling beforehand. On 9 August 2012 16:15, Stephen Blair stephen.bl...@autodesk.com wrote: I don’t know if this helps, but here’s something similar I was messing around with http://xsisupport.com/2012/08/07/resizing-polygons-with-ice/ From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Rob Chapman Sent: August-09-12 11:12 AM To: softimage@listproc.autodesk.com Subject: Re: ICE modelling - polygon area must be getting close - keep getting this now ' ERROR : 2429 - Access to a custom ICE node index set failed. This can occur when accessing an index set from the BeginEvaluate or EndEvaluate callback. all im trying to do is repeat in an array each selected polygons changes at the point level. ie I want to uniformly scale the polygon around its centre by a radius. whilst it is simple on a single Polygon, http://xsisupport.com/2012/02/09/making-circles-on-the-surface-of-a-mesh/ this is not so easy to get correct context when dealing with an array of polygons where each one is to have an individual radius value. and If I see another Context Mismatch: Input context supported: Per Object or Polygon output context supported: per Point well I guess I will just sigh yet again - this is sooo frustrating!
setting ICEAttribute.DataArray in JScript
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... Thanks, Eugen
User normals evaluation bug?
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 over the auto ones. This is documented and works just fine when the scene is opened interactively. However, the same method, when invoked from the xsibatch environment, returns garbage data if user normals are involved (if there are no user normals at all, everything is OK) I have reason to believe that this is may be somehow connected to a delayed operator evaluation issue under xsibatch. Is anyone aware of a good way to force operator evaluation on a given geometry (or the entire scene)? I know Softimage is supposed to do this by itself, but this seems to be a bug and I am looking for a workaround. K.
Re: setting ICEAttribute.DataArray in JScript
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 = xsi.Selection(0).ActivePrimitive.Geometry.ICEAttributes; for attr in attrs: if attr.IsDefined == True : xsi.LogMessage( *** ) xsi.LogMessage( Name: + attr.Name ) xsi.LogMessage( DataType: + str(attr.DataType) ) xsi.LogMessage( StructType: + str(attr.StructureType) ) xsi.LogMessage( ContextType: + str(attr.ContextType) ) xsi.LogMessage( IsDefined: + str(attr.IsDefined) ) xsi.LogMessage( IsConstant: + str(attr.IsConstant) ) xsi.LogMessage( Readonly: + str(attr.IsReadonly) ) xsi.LogMessage( AttributeCategory: + str(attr.AttributeCategory) ) xsi.LogMessage( Element count: + str(attr.ElementCount) ) dataType = attr.DataType; data = attr.DataArray; #print data.NestedObjects() for i,elem in enumerate(data): if dataType == constants.siICENodeDataFloat: xsi.LogMessage( float: + str(elem) ) elif dataType == constants.siICENodeDataLong: xsi.LogMessage( long: + str(elem) ) elif dataType == constants.siICENodeDataBool: xsi.LogMessage( bool: + str(elem) ) elif dataType == constants.siICENodeDataVector3: xsi.LogMessage( Vector3: + str(elem.X) + : + str(elem.Y) + : + str(elem.Z) + : index + str(i) ) elif dataType == constants.siICENodeDataQuaternion: xsi.LogMessage( Quaternion: + str(elem.W) + : + str(elem.X) + : + str(elem.Y) + : + str(elem.Z) ) elif dataType == constants.siICENodeDataRotation: xsi.LogMessage( Rotation: + str(elem.RotX) + : + str(elem.RotY) + : + str(elem.RotZ) ) elif dataType == constants.siICENodeDataMatrix33: xsi.LogMessage( Matrix33: ); xsi.LogMessage( str(elem.Value(0,0)) + : + str(elem.Value(0,1)) + : + str(elem.Value(0,2)) ) xsi.LogMessage( str(elem.Value(1,0)) + : + str(elem.Value(1,1)) + : + str(elem.Value(1,2)) ) xsi.LogMessage( str(elem.Value(2,0)) + : + str(elem.Value(2,1)) + : + str(elem.Value(2,2)) ) elif dataType == constants.siICENodeDataMatrix44: xsi.LogMessage( Matrix44: ); xsi.LogMessage( str(elem.Value(0,0)) + : + str(elem.Value(0,1)) + : + str(elem.Value(0,2)) + : + str(elem.Value(0,3))) xsi.LogMessage( str(elem.Value(1,0)) + : + str(elem.Value(1,1)) + : + str(elem.Value(1,2)) + : + str(elem.Value(1,3))) xsi.LogMessage( str(elem.Value(2,0)) + : + str(elem.Value(2,1)) + : + str(elem.Value(2,2)) + : + str(elem.Value(2,3))) xsi.LogMessage( str(elem.Value(3,0)) + : + str(elem.Value(3,1)) + : + str(elem.Value(3,2)) + : + str(elem.Value(3,3))) elif dataType == constants.siICENodeDataColor4: xsi.LogMessage( Color: ); xsi.LogMessage( str(elem.Red) + : + str(elem.Green) + : + str(elem.Blue) + : + str(elem.Alpha) ) elif dataType == constants.siICENodeDataString: xsi.LogMessage( String: + elem );
RE: setting ICEAttribute.DataArray in JScript
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 before it will work. Matt -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eugen Sares Sent: Tuesday, October 23, 2012 10:40 AM To: softimage@listproc.autodesk.com Subject: setting ICEAttribute.DataArray in JScript 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... Thanks, Eugen
Re: User normals evaluation bug?
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 bug, you have to force XSI to recompute the normals. This can be done in a number of ways - for example by calling NormalizeUserNormals from script, but be aware that most user normal commands will create user normals if they don't already exist, so you first have to determine which obejects need this treatment. Another way, which ended up being a lot simpler for us, is to call CGeometryAccessor::GetUserNormals before calling CGeometryAccessor::GetNodeNormals and just do nothing with the returned CRefArray (i.e. get your normals using the GetNodeNormals as before). Note that GetUserNormals is not particularly fast so this will make mesh extraction from XSI even slower than it is now (which is already WAY too slow) so it's best to only call GetUserNormals when you need to (i.e. first render after scene open). Hope this helps, -Nicolas On Tue, Oct 23, 2012 at 10:58 AM, Kamen Lilov kamen.li...@chaosgroup.com wrote: 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 over the auto ones. This is documented and works just fine when the scene is opened interactively. However, the same method, when invoked from the xsibatch environment, returns garbage data if user normals are involved (if there are no user normals at all, everything is OK) I have reason to believe that this is may be somehow connected to a delayed operator evaluation issue under xsibatch. Is anyone aware of a good way to force operator evaluation on a given geometry (or the entire scene)? I know Softimage is supposed to do this by itself, but this seems to be a bug and I am looking for a workaround. K.
Re: setting ICEAttribute.DataArray in JScript
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) - ICEAttribute.DataArray - Sets a 1D Array object containing the data defined by an attribute. - ICEAttribute.DataArray2D - Sets a 2D Array object containing the 2D data defined by an attribute. - Geometry.AddICEAttribute - Adds and returns a new attribute data on a geometry. - Geometry.RemoveICEAttribute - Removes a non-built-in attribute from a geometry if not required by an ICETree. On Tue, Oct 23, 2012 at 2:09 PM, Matt Lind ml...@carbinestudios.com wrote: 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 before it will work. Matt -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto: softimage-boun...@listproc.autodesk.com] On Behalf Of Eugen Sares Sent: Tuesday, October 23, 2012 10:40 AM To: softimage@listproc.autodesk.com Subject: setting ICEAttribute.DataArray in JScript 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... Thanks, Eugen
Re: setting ICEAttribute.DataArray in JScript
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 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 before it will work. Matt -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eugen Sares Sent: Tuesday, October 23, 2012 10:40 AM To: softimage@listproc.autodesk.com Subject: setting ICEAttribute.DataArray in JScript 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... Thanks, Eugen
Re: xsi's Attached to Camera feature in maya?
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 the view in relation to the resolution/film gate. Example, a setextension geo where you want to reproject the BG plate, a concept or whatnot and can´t/mustn´t keep an extra CAM for projections via the shader network hanging around. Max sucks in that department as well, try projecting a 4K square map through a camera while having a 16:9 aspect ratio in your Render settings dialed in. It´ll work if you change the aspectratio of the output to 4K square, project, then back to the previous settings but you have to keep track of it mentally. Such stuff is so 1992... Cheers, tim P.S: Oh, and make sure you mel button use the old PolySplitTool; the new one is crappy imo, the old one let´s you add your edges wherever you want... On 23.10.2012 05:12, Manuel Huertas Marchena wrote: yeah exactly, I'll try to use built in features when ever I can, although being using maya for about 3 weeks now I find plugins like NEX and uvratiopro can speed things up a lot... ...which makes me think, I wish xsi's uv tools were as good as its particle system, having something like uv ratio pro or renderhjs's textools for max equivalent would an be awesome add to an already awesome app :) From: chrisg.dot@gmail.com Date: Tue, 23 Oct 2012 14:02:44 +1100 Subject: Re: xsi's Attached to Camera feature in maya? To: softimage@listproc.autodesk.com Glad you got it going. It's fairly well done, once you get the hang of it. i suppose the big advantage is that it's built in, and it's a navigation mode not unlike the alt key, so you don't have to muck about in another window like zoomerator and other scripts. now, back to softimage!! :) cheers, chrisg On 23 October 2012 13:57, Manuel Huertas Marchena lito...@hotmail.com wrote: Awesome, got it working now, thanks for sending the link of the documentation.. it s method 2 I was looking for, it actually works really smooth now, and I am glad its just a hotkey toggle, I changed it to a closer hotkey though..(to the left side of the keyboard..) I find the backslash a bit unfortable (kinda far, and I am using a wacom with the right hand) because you actually need to keep it press for that feature to work.
RE: setting ICEAttribute.DataArray in JScript
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 [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eugen Sares Sent: Tuesday, October 23, 2012 11:30 AM To: softimage@listproc.autodesk.com Subject: Re: setting ICEAttribute.DataArray in JScript 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 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 before it will work. Matt -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eugen Sares Sent: Tuesday, October 23, 2012 10:40 AM To: softimage@listproc.autodesk.com Subject: setting ICEAttribute.DataArray in JScript 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... Thanks, Eugen
Re: setting ICEAttribute.DataArray in JScript
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? 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 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 before it will work. Matt -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eugen Sares Sent: Tuesday, October 23, 2012 10:40 AM To: softimage@listproc.autodesk.com Subject: setting ICEAttribute.DataArray in JScript 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... Thanks, Eugen -- --- Stefan Kubicek Co-founder --- keyvis digital imagery Wehrgasse 9 - Grüner Hof 1050 Vienna Austria Phone:+43/699/12614231 --- www.keyvis.at ste...@keyvis.at --- -- This email and its attachments are --confidential and for the recipient only--
RE: setting ICEAttribute.DataArray in JScript
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(, false) CreatePrim(grid, MeshSurface, , ) SetValue(grid.polymsh.geom.subdivu, 2, null); SetValue(grid.polymsh.geom.subdivv, 2, null); // Type = Vector3, Context = One element per polygon. attr = Selection(0).ActivePrimitive.AddICEAttribute(MyVec3, siICENodeDataVector3, siICENodeStructureSingle, siICENodeContextComponent2D ) attr.DataArray = [ XSIMath.CreateVector3( 1.0, 0.0, 0.0 ), XSIMath.CreateVector3( 0.0, 1.0, 0.0 ), XSIMath.CreateVector3( 0.0, 0.0, 1.0 ), XSIMath.CreateVector3( 0.0, 0.0, 0.0 ) ] -- Francis -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Stefan Kubicek Sent: October 23, 2012 14:58 To: softimage@listproc.autodesk.com Subject: Re: setting ICEAttribute.DataArray in JScript 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? 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 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 before it will work. Matt -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eugen Sares Sent: Tuesday, October 23, 2012 10:40 AM To: softimage@listproc.autodesk.com Subject: setting ICEAttribute.DataArray in JScript 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... Thanks, Eugen -- --- Stefan Kubicek Co-founder --- keyvis digital imagery Wehrgasse 9 - Grüner Hof 1050 Vienna Austria Phone:+43/699/12614231 --- www.keyvis.at ste...@keyvis.at --- -- This email and its attachments are --confidential and for the recipient only-- attachment: winmail.dat
Re: Strands Question
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 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 https://www.dropbox.com/sh/z8p4v5kkh24fqhg/PlWaklwcbU/Raintest2012.scn Frame 27 is the first instance of this extra tail on the newly spawned blue particles.. Just not remembering how to fix this one.. Thanks for any help.. Adam On Mon, Oct 22, 2012 at 12:47 AM, Thomas Volkmann li...@thomasvolkmann.com wrote: ** Unfortunately the scene crashes at startup... at least on my machine :/ /Thomas Adam Sale adamfs...@gmail.com hat am 22. Oktober 2012 um 05:35 geschrieben: Hey folks, Its been a while since I've used strands, and I recently came across an issue that I can't remember how to fix. Searching archives yields no useful results, as I'm not sure how to frame my query. If I emit Strands from particles ( like rain streaks), and then spawning particles based on collisions with say a grid, the spawned particles inherit the strands, but they have this behavior where the strands are actually ahead of the actual particle from which they are supposed to trail. In the create Strands Dialogue, there is a Reverse Strand direction option, but this doesn't do it. Its easiest to see this on frames 15 and 16 of the dropbox attach. Heres a link to a scene so you can see what I mean.. I feel like this is one of those duh moments... https://www.dropbox.com/sh/z8p4v5kkh24fqhg/hOZ9aew6n9 Thanks for any thoughts.. Adam
ICE cacheing
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 am I correct in assuming things generally get evaluated in the tree even if they are not directly executed. Cheers, Nick [Description: ALT_signature_NANGUS] inline: image001.gif
Re: ICE cacheing
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 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 am I correct in assuming things generally get evaluated in the tree even if they are not directly executed. ** ** Cheers, Nick ** ** [image: Description: ALT_signature_NANGUS] ** ** image001.gif
RE: ICE cacheing
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 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.commailto: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 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 am I correct in assuming things generally get evaluated in the tree even if they are not directly executed. Cheers, Nick [Description: ALT_signature_NANGUS] inline: image001.gif
