Weird behavior with spline setup in APEX Autorig Component

   296   3   3
User Avatar
Member
2 posts
Joined: Dec. 2015
Offline
Hi, I'm not sure if this is a bug or if I'm doing something wrong.

So I wanted to rig a spline with APEX using the Autorig SOP, but I wanted to enable "custom" on the driver tab on the Spline Autorig SOP, because I want to have a choice in the number of CVs in my curve rig, instead of the default 4 controls.

The way I did it is by deciding the number of control points first, then have a "mult" attribute, which just determines how many segments there are between two control points. From that I resample the spline, and the number of segments is defined by the formula (ctrl_pts -1) * mult.



After that I did tags, rig doctor, pack folder, fk autorig SOP, and then the spline autorig SOP. Set curve order to equal the number of control points, enabled "custom", then on the resample slider I set it to equal mult. The setup works just the way I wanted.



Now here's the problem, if I update either the ctrl_pts or the mult, the rig breaks. I did refresh the autorig sops (fk first, then spline) but it doesn't fix the problem.



The weird thing is if I change either the prefix or suffix, then the setup updates perfectly. What's even weirder is I can only change it with a completely new prefix. I think it's pretty cumbersome to always update the prefix every time I have to update the ctrl_pts and mult parameters.



I think this is a bug, but if anyone has a solution I'd really appreciate it. Thanks.

Image Not Found

Attachments:
img02.png (57.1 KB)
img03.png (467.3 KB)
img04.png (469.4 KB)
img05.png (508.2 KB)
img06.png (628.1 KB)
hipfile.hiplc (343.3 KB)

User Avatar
Member
76 posts
Joined: Oct. 2018
Offline
This does sound buggy, because you're fixing it by changing the naming scheme. If Will doesn't jump in here with an answer, I'd log a BUG report.
User Avatar
Staff
66 posts
Joined: Oct. 2023
Offline
Can you please log a RFE/BUG.
User Avatar
Member
2 posts
Joined: Dec. 2015
Offline
Hello, thanks guys for the response.

I just finished logging the bug/RFE. In the meantime I'll try to explore APEX more and see if I could come up with a workaround.
  • Quick Links