The rigattribwrangle and rigstash method is good, but I was having trouble in that whenever I converted units, the rigattribwrangle was producing a very odd-looking skeleton. It was working correctly, but the problem was in how the localtransform is computed.
The localtransform of a child joint is affected by the parent, and how it is affected is determined by the “scaleinheritance” attribute. This was 1 by default, which, according to the docs, means the child isn’t affected by the parents’ scale. I guess the convert units was causing a scale issue that wasn’t propagating down the rig. I set this to zero instead (i@scaleinheritance = 0) and it worked fine. Zero was just the first value I used and it worked.
Thank you! This solved the issue for me, although I thought it was due to a different root cause… On my end I just couldn’t find the “localtransform” 4×4 matrix attribute on any of the outputs of the fbxcharacterimport node (with any of the Mixamo downloaded fbx files).
My question is, if there isn’t a localtransform point attribute on the incoming geometry, how does the VEX code in the first rig attribute wrangle work? Where is this VEX expression finding and pulling the “localtransform” 4×4 matrix data from? Is it just computing it from the available “transform” 3×3 matrix point attribute on either the Capture Pose or Animated Pose geometry?
Also, I can’t seem to be able to find the Episode 31 of this course where you discuss the FBX issues with KineFX. Any chance the numbering has changed since your post below? I’ll keep working my way to the course until the end, so I’ll come back to this once I find it!
Hey! Chris chiming in here: This episode uses FBX Files, which sometimes can cause issues with KineFX. We’ve adressed these issues and all our known solutions in Episode 31 of this course. If something in your setup isn’t behaving as shown in the video and the error persists if you load the scenefile, give Ep31 a watch!
Unlock with Patreon
For anyone having trouble with recreating this:
The rigattribwrangle and rigstash method is good, but I was having trouble in that whenever I converted units, the rigattribwrangle was producing a very odd-looking skeleton. It was working correctly, but the problem was in how the localtransform is computed.
The localtransform of a child joint is affected by the parent, and how it is affected is determined by the “scaleinheritance” attribute. This was 1 by default, which, according to the docs, means the child isn’t affected by the parents’ scale. I guess the convert units was causing a scale issue that wasn’t propagating down the rig. I set this to zero instead (i@scaleinheritance = 0) and it worked fine. Zero was just the first value I used and it worked.
Thank you! This solved the issue for me, although I thought it was due to a different root cause… On my end I just couldn’t find the “localtransform” 4×4 matrix attribute on any of the outputs of the fbxcharacterimport node (with any of the Mixamo downloaded fbx files).
My question is, if there isn’t a localtransform point attribute on the incoming geometry, how does the VEX code in the first rig attribute wrangle work? Where is this VEX expression finding and pulling the “localtransform” 4×4 matrix data from? Is it just computing it from the available “transform” 3×3 matrix point attribute on either the Capture Pose or Animated Pose geometry?
Also, I can’t seem to be able to find the Episode 31 of this course where you discuss the FBX issues with KineFX. Any chance the numbering has changed since your post below? I’ll keep working my way to the course until the end, so I’ll come back to this once I find it!
Hey! Chris chiming in here: This episode uses FBX Files, which sometimes can cause issues with KineFX. We’ve adressed these issues and all our known solutions in Episode 31 of this course. If something in your setup isn’t behaving as shown in the video and the error persists if you load the scenefile, give Ep31 a watch!