It includes the above-mentioned fix as well as another improvement which is that it now no longer requires the original rig to be in rest position. This is done by grabbing the weights from the selected deform SOP's input and then transferring the deformed point positions to the shadow_geo (necessary because it's very common for the deform SOP to be set to ‘Delete Capture Attributes’, the auto-rig is setup this way).
Performing the capture correct after this step sets the whatever the current pose is as the ‘capture pose’. So then all subsequent deformations to the shadow_geo will take place *from* this point. Meaning bones and deformed geometry will always match up.
This could be handy if you're working with an already animated asset, that you don't want to mess about duplicating or resetting channels on to retrieve the rest position (I am really, really lazy )
Nulls also have their display scale set to something hopefully more sensible.
That's wonderfull! How far are we from the exact inverse ? taking an imported fbx (matching RIG) driving a real Houdini rig ? Trying to import Mocap from MotionBuilder then adjust modify in Houdini
So it's time for my Yearly journey back to Houdini Character systems. After talking to some of the SideFX guys at Siggraph in Vancouver I was excited again by the idea of characters in Houdini. I went through the cat rigging tutorial (One of the more complete tutorials I have seen) and then I read through this thread again. I thought I would chime in on my opinions so far. I do think the Bones instead of joints for the system was probably a mistake. And FBX import does become quite Huge and messy with the amount of nodes. And there seems to be NO easy system to attach Mocap and edit it on a character.
But beyond that I have to say the I just don't buy into the with “With Greater Power comes Greater Responsibility” concept that was implied in this thread. For one thing it's not more powerful when you have a mess of hundreds of nodes. It actually slows you down and makes you weaker. And it certainly shows with how Non-Responsive the rigs can be even on a very powerful workstation in Houdini. Personally I think this is one area that would be faster, More efficient, and productive with TOOLS instead of Nodes. It doesn't mean that the tools couldn't communicate with nodes. And overall the process would be a much more pleasant experience with proper tools.
Nodes are great. I use them in about a dozen programs. But too much of anything is a bad thing. I'll give an example: I am just now learning Blender 2.8 which is in Beta currently. I got all the meshes for a character imported rigged and was animating in under 30 minutes. This was my very first time rigging in blender.
Getting the Houdini cat going properly took all night. If I can do this faster and have more fun doing it in a FREE software package, Then there is definitely a problem. Personally I think this slavish devotion to nodes is the key to the problem.
Add to this, that Simple things like importing OBJ's can't even handle material importing. Or that the Materials imported with the FBX import are your older material set-ups, And you have a system that seems slow and more then a little bit annoying.
I find it frustrating because I want characters in Houdini to work. But the truth is that it is not a set up that I can see animating characters in for years at a time.
)
