It ought to recreate UVs and material assignments also, I'd think. :)

On Fri, Aug 24, 2012 at 10:42 PM, Chris Chia <[email protected]>wrote:

> Hi Rob,
> >From what I know, you can force a custom attribute to be cached if you
> deliberately force it by "display its attribute" while you are caching from
> the 'real object'.
>
> Anyway, I have written a small ice node plugin (during the wkends) and
> this node reads some attributes from ice cache in order to recreate the
> topo. Currently i only cache 2 attributes: pointpositions and
> pointToVertives. It's working well.
>
> Just wondering what attributes do you guys need to recreate topo... Keen
> to know how others are using... ;) so that I can share this plugins (with
> other nodes too) with you guys...
>
>
>
> On 16 Aug, 2012, at 10:18 PM, "Rob Chapman" <[email protected]<mailto:
> [email protected]>> wrote:
>
> Ciaran, thank you very much indeed that worked a treat!   I had a slight
> issue recreating getting the txt_proj attribute over but mostly just a typo
> in the name I think.
>
> for those that are stuck in Production on 2012 still and want a slice of
> Topo caching action from Ciaran, I converted it to work in 2012 and can be
> reached here
>
> https://docs.google.com/open?id=0B0WD7fSUkxAMODRlZl9GQ0FsTWc
>
> now if only there was a centralized resource for uploading and sharing all
> these cool new compounds, tricks and techniques ;)
>
> Best
>
> Rob
>
>
>
> On 15 August 2012 15:29, Rob Chapman <[email protected]<mailto:
> [email protected]>> wrote:
> mine or Softimages? :) no-worries - been there done that already, trick is
> to replace the compiled 2013 node with a renamed 2012 version then export
> the icetree.
>
> et voilĂ  - forward compatability
>
>
>
> On 15 August 2012 15:19, Ciaran Moloney <[email protected]<mailto:
> [email protected]>> wrote:
> er...careful. 2013 uses a new super powerful build array from set node
> that may cause your flux capacitor to explode.
>
>
>
>

Reply via email to