While I appreciate the software's efforts to cache only the ICE attributes
that it deems necessary (unless I list all the ones I want - in this case,
many); can we please, please, get a Just bastard cache everything, I don't
care how big the cache files are button?
I've lost hours today trying
+1 for brute cache !
Am 06.02.2013 um 15:06 schrieb Dan Yargici danyarg...@gmail.com:
While I appreciate the software's efforts to cache only the ICE attributes
that it deems necessary (unless I list all the ones I want - in this case,
many); can we please, please, get a Just bastard cache
long way around but definitely a brute force approach. make a custom
attribute display for each attribute you need storing.
On 6 February 2013 14:14, Sebastian Kowalski l...@sekow.com wrote:
+1 for brute cache !
Am 06.02.2013 um 15:06 schrieb Dan Yargici danyarg...@gmail.com:
While I
Thanks Rob.
Yeah, I know about that one but it's just so hacky and shit, frankly.
There really needs to be a fool-proof fallback implemented once and for
all.
DAN
On Wed, Feb 6, 2013 at 4:21 PM, Rob Chapman tekano@gmail.com wrote:
long way around but definitely a brute force approach.
I know I know, I used to have various hacky ways to 'force' an
attribute to be stored in a cache. daisychaining them or storing
userdata in the color or whatever ;) all of them have failed me at
some point until I happened upon a demo ICE topo scene provided by
Ciaran Moloney and saw that every
one way of doing it is to put a Log Values between the data and the
setData node. Even if the log node is muted, Log is unchecked, this node
forces the attributes to be evaluated.
Cheers
Vladimir
On Wed, Feb 6, 2013 at 3:51 PM, Rob Chapman tekano@gmail.com wrote:
I know I know, I used to
I've got used to it, but still one of this small things that would ease up my
daily routine ;)
.sebastian
Am 06.02.2013 um 15:51 schrieb Rob Chapman tekano@gmail.com:
I know I know, I used to have various hacky ways to 'force' an
attribute to be stored in a cache. daisychaining them or
I would still advise using the forcing to be done through some
arithmetic nodes - like adding a zero vector to point positions etc.
Alok
Lead TD
Modusfx
On 06/02/2013 11:14 AM, Vladimir Jankijevic wrote:
the problem with this is that with the log node present in the tree,
the icetree will
I'd second that.
I normally use all attributes I want to force evaluation for to construct a
zero length 3D vector. Then I do*GetPointPosition -- AddMyZeroVector
-- SetPointPosition* as the last Execute in my tree.
Has been working this way for me for years now.
Cheers, Martin
--
Subject: Re: [Mini rant-let] Caching attributes - again.
I'd second that.
I normally use all attributes I want to force evaluation for to construct a
zero length 3D vector. Then I doGetPointPosition -- AddMyZeroVector --
SetPointPosition as the last Execute in my tree.
Has been working
...@googlemail.com]
*Sent:* 06 February 2013 19:24
*To:* softimage@listproc.autodesk.com
*Subject:* Re: [Mini rant-let] Caching attributes - again.
I'd second that.
I normally use all attributes I want to force evaluation for to
construct a zero length 3D vector. Then I do *GetPointPosition
11 matches
Mail list logo
