I mean, sometimes you cache it in the right context but ice refuses to read it...that's my case above.
2012/11/23 Fabricio Chamon <xsiml...@gmail.com> > ...happens everytime to me. > What I always do is to init the custom variable on the right context > *before* loading the cache (cahe on file node). > It prevents the rest of the icetree from screwing up with your attribute. > > > 2012/11/23 Sebastian Kowalski <l...@sekow.com> > >> jep, had that idea after thinking more about it (and drinking my first >> coffee). >> but I've shivered a bit by guessing how long this would take on a 10 mill >> + cloud ;) >> thanks >> >> Am 23.11.2012 um 10:37 schrieb Rob Chapman <tekano....@gmail.com>: >> >> Hi Sebastian, >> >> if it is just a color gradient by particle density that you are after >> then it is really simple to get this with a Get Neghbours > count > rescale >> range > gradient >> >> ie this https://vimeo.com/1618403 >> >> it is a fast realtime calculation (as long as you set the search distance >> to a reasonable level!) than can be applied in the modelling stack of an >> ice tree to an already cached simulation affecting the color >> >> if its something else required from the actual part of the Lagoa >> Simulation then I have no idea of how to get it without simmming again. >> >> >> >> On 23 November 2012 09:22, Sebastian Kowalski <l...@sekow.com> wrote: >> >>> >>> Hey list, >>> >>> i can't read the Lagoa_Density attribute from my cache files, giving me >>> this error msg: "The cache has a different definition for attribute >>> 'Lagoa_Density'. Loading canceled" >>> This is a massive showstopper right now, i have should check that. >>> I thought this attribute is a value per point. >>> >>> I could try to write this attribute into a custom attribute, but this is >>> a heavy simulation, i don't want (and don't have the time) to re-sim. >>> >>> any hints how i could fix that would be much appreciated. >>> >>> sebastian >>> >> >> >> >
