combi, thanks for the help - I tried setting the constructionHistory flag to false but that didn't seem to make any significant difference. Currently it takes about 1:20 to do 1000 meshes which is a lot slower than I'd like. It is the combine at the end that is taking so long - without that it's only about 15 seconds.
Marcus, your're close, but what I need to do is bake a dynamics simulation on a bunch of meshes to joints. So for each mesh in the sim, I need one joint, and I need to essentially copy whatever keyframes are on the mesh to it's corresponding joint. I have it working, but without the combine, I'm left with individual skinCluster nodes for each mesh, meaning I might have 1000+ skinCluster nodes in my file which I'd like to avoid. On Wednesday, November 4, 2015 at 11:45:14 AM UTC-6, Marcus Ottosson wrote: > > You can of course use the skinCluster -e -g “anotherGeom”, and it will > “deform” this geometry, but it is not supported by the node. > > Ah, yes you’re right. I was confusing this with skinning a combined mesh. > Sorry to have made you dig up all of those links. :) > > I’ve experimented in the past with a “fan-in-fan-out” sort of approach to > that, where meshes were combined and then separated before and after a > skinCluster node, but can’t remember whether it actually worked. There was > issues with point numbers changing I think, though that seems fixable. But > I suppose that’s quite off topic! > > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/cadc2491-7ef2-49ca-a529-828b551f4344%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
