Is this a bug?? Any fix?

   381   4   2
User Avatar
Member
7 posts
Joined: Sept. 2020
Offline
So I'm learning kineFX in Houdini, not new to the software at all, but I have only two days of "experience" in all this rigging stuff.

I already created the skeleton and oriented the bones properly. The issue is that I keep encountering a very annoying bug. When I try to unparent a bone, fix its orientation, and reparent it again, the rig pose suddenly starts to glitch, and all the handles shift to weird pivot offsets, becoming deformed.
By simply selecting the joint, the pose shifts. It moves with all transform parms to 0.
I fixed that by simply not using the parent thing and working on the orientation by eye, but then I tried to create twist joints on the arm, and the bug happened again. I have no idea why, and I have no idea how to fix it, because I need a way to create those joints.

This was recorded on H 20.5.487 btw, but I updated the H v21.0.440 (the latest version) and the bug remains the same.

Thanks so much if somebody has already had this issue and knows how to fix it )
Edited by Nok - Sept. 26, 2025 19:23:06

Attachments:
rig bugs.mp4 (10.2 MB)

User Avatar
Member
691 posts
Joined: Aug. 2019
Offline


I'm not sure what the exact cause is, but here Rig Pose SOP is telling you something is wrong. What does the warning say in the node info panel?

Attachments:
Enter_a_filename.png (22.4 KB)

User Avatar
Member
7 posts
Joined: Sept. 2020
Offline
raincole
Image Not Found


I'm not sure what the exact cause is, but here Rig Pose SOP is telling you something is wrong. What does the warning say in the node info panel?

Thank you, man! I didn’t see the warning — what an amazing eye you have! The warning says: “Discarding shears on group0.”

As far as I’ve discovered, when you unparent/parent, split, resample, or modify the joint geometry, the transform matrix gets corrupted. It’s no longer orthogonal (only translation, rotation, and scale) after those modifications and ends up with more values than it should. Because of that, the Rig Pose node interprets it as if there’s shear in the matrix and discards it right away.

Once part of the matrix is deleted, the rest of the components break since there’s missing data. Apparently, you can’t really do anything other than deleting the attribute and rebuilding it again. I tried using Orient Joints, reconstructing the matrix with Rig VOP and Attribute VOP… nothing worked.

The only solution I found was: Attribute Delete → Orient Joints.

I even made a tutorial in case anyone else encounters this bug, because it was a real pain to solve.
Thanks again

Edited by Nok - Oct. 1, 2025 06:23:47
User Avatar
Member
8067 posts
Joined: July 2005
Offline
The problem here is that the Resample SOP is a generic geometry operator so it doesn't know about the data constraints that KineFX requires. So what happens is that the Resample SOP is mostly likely just linearly interpolating the components of the transform matrices (feel free to log an RFE to improve this). My fix here is to just apply a Rig Doctor and then an Orient Joints (make sure you turn on Up Vector). I've attached the file I tried.

Attachments:
kinefxResampleFix.hip (118.9 KB)

User Avatar
Member
7 posts
Joined: Sept. 2020
Offline
edward
The problem here is that the Resample SOP is a generic geometry operator so it doesn't know about the data constraints that KineFX requires. So what happens is that the Resample SOP is mostly likely just linearly interpolating the components of the transform matrices (feel free to log an RFE to improve this). My fix here is to just apply a Rig Doctor and then an Orient Joints (make sure you turn on Up Vector). I've attached the file I tried.

Hi, thanks for the comment!

I took a look at your scene, and the Rig Doctor doesn't work for me (I also tried reconstructing the transforms with rigVOP), and it still bugs.

It makes sense what you said about the resample, but it's not only creating new points, but overwriting, copying, deleting, and unparenting-modifying-parenting. At this point, I don't know if it's the Houdini version or what, but I'll definitely write an RFE or maybe talk to support for some help.

For now, the issue is solved. The only way I found to fix this is by deleting the attributes completely, and then copying the previous atts or creating those again. But it's really weird for me needing to do this bc there's no other way.

Thanks again for your help

Attachments:
still bugs.mp4 (8.4 MB)

  • Quick Links