With the re grooming you could just save out your old weight maps and
reapply them
Maybe as long as you have not edited the mesh!
Ben
On 5 November 2013 15:41, Jonny Grew jonny.g...@gmail.com wrote:
Just thought I'd give you an update about this...
Mr MB had a look at our scenes and
Cheers, Ben. Good call - and no the mesh hasn't changed... but we want to
steer completely clear of using anything that was involved in the previous
setup call it superstition if you like but I don't want to risk adding
anything that might have been involved in the initial corruption!
As it
Forgot to say 2013 sp1 - testing in 2014 now but the fear of switching
version mid project makes me reluctant!!
*-- *
*Jonny Grew Ltd *
*www.Jonnygrew.com http://www.Jonnygrew.com*
*http://vimeo.com/jonnygrew/showreel2013*http://vimeo.com/jonnygrew/showreel2013
*07855 212722*
Jonny Grew Limited
I have found it is safest, and I presume you are using ICE Cache?
..to setup the instancing on the point cloud reading the cache in -
i.e. I copy and paste the instance section from the original cloud to
the in cloud. So you can either read in the cache into the mixer, or a
cache node -
I have been working with this feather tool for two years now my formula to
make it work is:
Step1
In scene one
Create the feathers with mbfeather tool on your character save this as a
base scene
Step2
PolyMesh Duplicate the feathers (this example is for one type of feathers)
Step3
With that
Cheers, guys.
So it appears that with either of these methods we can only get it to work
with one feather type?
Am I missing something?
As we can't access the attribute that defines the feather type (1-6 within
the group) the set instance doesn't look like an option and the polymesh
duplicator
I found this plugin brill but its a bit of a fiddle, There is a addon out
there that will export all the feathers together as one mesh.
I've seen at Glassworks, if that person want to give it out I suggest you
set up a new thread to see if this person comes forward. He all over this
list, so he
If you were going that route maybe emTopolizer2 would be another solution?
http://www.mootzoid.com/plugin/emtopolizer2
For the original issue it sounds like the ice custom attributes
'optimisation' problem. Without knowing which attributes are resonsible for
the instance picking you're a bit
Cheers, Ben - Will do. We're packing up a scene with the problem to mr MB
himself too so we'll see if he can shed some light on it! - Hopefully not
stating that we've made a fundamental mistake that will make us look like
knobs!
Yep, Matt... That's the problem... but again if Mr MB can show is
ICEcache mode should work fine - you just need to possible recreate or
copy the Instancing section on the cloud in.
S.
On 2013/11/04 6:53 PM, Jonny Grew wrote:
Cheers, guys.
So it appears that with either of these methods we can only get it to
work with one feather type?
Am I missing
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
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
12 matches
Mail list logo
