You might be right Jonny, been a while since I used it. I am sure you
can look see what attributes are being written and find the instance one
- it is most likely an integer that can then be fed into an instance node.
S.
On 2013/11/04 9:01 PM, Jonny Grew wrote:
The problem is, Sandy, that I cannot recreate the instancing section
of the ice tree. The compound for MB feather tools is not explorable.
You simply point it at an instance group but the allocation of each
individual feather instance is defined by an envelope weight on a
duplicate of the render mesh (called the envelope mesh) Under the hood
this will give the particles a custom attribute (I'm guessing) that is
used to inform which instance each particle should use-the same goes
for size and rate but driven by a weight map that is local to the
render mesh. Determining which attribute is being used and how is
what I would need to know in order to use on a secondary ice tree by
using the set instance geometry node in my 'cache read' particle cloud.
MB looking at it but cache issue could be down to how the feather
tools were set up originally or some kind of internal confusion due to
the fact we have 3 separate feather tool setups all referencing the
same instance feather group.
Will report back when I know more.
Jonny
