Just to update everyone. The Softimage RemoveFlexEnv() command is super
slow. The better approach is to get the weights array, iterate over
that cleaning out deformers that you don't need while keeping the
removal of deformer arrays and the removal of the unused deformers from
their respective
Thanks Matt,
You've summed it up quite well. I can't strip any more deformers than I
already have.
Alan, I'm not using GATOR and thus in the MergeMesh PPG it doesn't show
the method it is using. I'm hoping it is using closest vertex.
Eric T.
On Tuesday, October 28, 2014 1:41:01 PM, Alan Fr
This may be an obvious thing, Eric, but did you try the "closest vertex"
method? Since you're transferring from the same exact shape, it should be a
lot faster than the default "closest surface".
On Mon Oct 27 2014 at 9:51:57 PM Matt Lind wrote:
> You'll get the best results if you merge the
You’ll get the best results if you merge the meshes first, cull redundant
deformers from the envelope, then do the weight transfer. The part that’s
taking so long is you’re creating an M x N x O array of deformers and vertices
(436 objects * 161,000 vertices * NbDeformers). That’s a huge envel
Sorry, didn't want to give an
oversimplified answer,
but I also found this.. (from Mathaeus) using Multithreaded ICE :)
http://www.si-community.com/community/viewtopic.php?f=41&t=1199
a small tut about transferring
attributes, even
Thanks Cesar,
The merge itself is relatively fast. Transferring the attributes is
what is slow. UVs are super quick but skinning is the culprit. I don't
have a low res cage as I need to maintain the weighting that is there
pretty much 1 to 1. What is appearing to be the problem is that there
Hi Eric,
A couple of things to keep in mind (I'm sure you already went over these,
but just in case):
- Merge is expensive, make sure to merge your groups at once instead of add
part by part through multiple merge operations.
- Transfer weights from a single cage mesh works way better than from
sm
Yeah these general responses of 'just use numpy' aren't really in the
vacinity of providing me any path forward.
I know what numpy is but this suggestion somewhat implies that I should
write my own GATOR tool, which I have no interest or time to do.
I wish simply doing an:
import numpy
would be
Don't know what is involved for
implementation, but here's the best 'NumPy' description I found
from here http://ipython-books.github.io/featured-01/
which also includes further optimisation tricks/recipies
Featured Recipe #1: Getting the Best
How does this help when having to transfer weights of many meshes and
their points to a coinciding point on a merged mesh?
On Monday, October 27, 2014 10:57:14 AM, Alok Gandhi wrote:
One word - numpy!
Sent from my iPhone
On 27-Oct-2014, at 8:20 pm, Eric Thivierge wrote:
Hey all,
Running i
One word - numpy!
Sent from my iPhone
> On 27-Oct-2014, at 8:20 pm, Eric Thivierge wrote:
>
> Hey all,
>
> Running into a problem lately and it's becoming really problematic in
> production. I have a rigged model with a ton of meshes (985) which are all
> skinned. I have to combine a bunch o
Hey all,
Running into a problem lately and it's becoming really problematic in
production. I have a rigged model with a ton of meshes (985) which are
all skinned. I have to combine a bunch of these based on predefined
groups I've made.
However it's taking forever to combine and transfer weig
12 matches
Mail list logo
