Just updated the gist and marked the attribute as 'AlwaysEvaluated'. This
is important to ensure it sticks around. Also worth checking out the
AddStaticICEAttribute() command too.
Sometimes it's tricky to just freeze a mesh that has an ICE Attribute on it
that is driven to "store" it. Next time yo
https://vimeo.com/49833260
This isn't storing per point data but the method is the same
Sent from my iPad
> On 28 Feb 2016, at 19:45, Jeremie Passerin wrote:
>
> Thanks Eric, I'll give it a try on Monday.
>
>> On Feb 28, 2016 11:28 AM, "Eric Thivierge" wrote:
>> Here you go Jeremy & all:
>>
I haven't looked at Eric's file, but if you want to, this is very easy in ice.
You can store per point data adding each frame to an array. On a clone. At
the end, freeze the clone and it will be a Permanent attribute you can read
from another object.
Sent from my iPad
> On 28 Feb 2016, at 19
Thanks Eric, I'll give it a try on Monday.
On Feb 28, 2016 11:28 AM, "Eric Thivierge" wrote:
> Here you go Jeremy & all:
>
> https://gist.github.com/EricTRocks/acdb297705dd58a6226c
>
> Can probably be optimized a bit but works for my needs.
>
> Eric T.
>
>
Here you go Jeremy & all:
https://gist.github.com/EricTRocks/acdb297705dd58a6226c
Can probably be optimized a bit but works for my needs.
Eric T.
Eric Thivierge
http://www.ethivierge.com
On Sat, Feb 27, 2016 at 10:35 PM, Eric Thivierge
wrote:
> Ye
Yes I've done it for an internal tool. I can dig up a snippet in the next
few days. You're basically going to write to a Vec3 array attribute that
you'll have to pre-fill with place holder data then build up your data
array through your timeline pass and at the end set it all at once.
It's essenti
pretty sure you could:
Get PointPosition => Build Array From Set => Set Data (self.myDataArray {or
whatever name you choose})
Then use a Get Data node referencing "self.myDataArray" if in the same
ICEtree, or referencing the geo or pointcloud you set the data on if
applying to other geo.
I think
Any reason you don't want to save to an external file? I used to create
point clouds just to store specific data sets to then use to drive another
simulation. For example, creating a volumetric cloud of vectors you could
visualize to drive another simulation.
On Fri, Feb 26, 2016 at 8:12 PM, Jerem
Hey guys,
I'm not sure if there is many people left on that list to answer, but I
thought I'll give it a shot.
I was wondering if there is a way with ICE to cache point position per
frame internaly without saving to file.
I'm thinking maybe I could build an array of point position, and then read
9 matches
Mail list logo
