Component Standard Connections

Dave_Moulder · August 31, 2021, 5:46pm

I’ve created a new spine component based on Spine_FK_01. This component basically lets me place the joints in the spine with the guide, instead of it being a division function of the component. Great when I have to match existing skeletons.

Everything is working but components added as children aren’t being connected up with the standard connector. Can someone explain how that works?

Thanks for your time in advance.

-Dave

Dave_Moulder · August 31, 2021, 6:45pm

I think I’ve solved half of as the child components are following the FK. But I need it to follow the IK top control. It’s not 100% clear to me the relationships between the dictionaries and how they relate to the connectors. So some help would be useful.

So far I’ve set the relationships as such…

Here’s the gist.

gist.github.com

https://gist.github.com/thirstydevil/afa20bfe13e7e9bc7ab127366b26cc5c

spine_FK_02_init.py

import pprint

import pymel.core as pm
from pymel.core import datatypes

from mgear.shifter import component

from mgear.core import node, fcurve, applyop, vector, curve
reload(curve)
from mgear.core import attribute, transform, primitive

This file has been truncated. show original

Miquel · August 31, 2021, 11:24pm

Sorry I didn’t check all your code

But the method to check should be setRelation:

can you confirm that your self.cnx0 and self.cnx1 are following as expected the IK. If you didn’t change that part they will follow the FK (if I recall correctly)

Dave_Moulder · September 1, 2021, 9:35am

Hi @Miquel, thanks for the reply.

I didn’t expect to have to change the setRelation function when I made the new component as much of the code stayed the same. The “hooks” self.cnx0 and self.cnx1 are still there and working as expected, I got a half working solution by adding the loop and between the “%_loc” and the FK controls as in the above demo.

If you could, I’d love to see some explanation of the setRelation method and how these dicts describe the connection process. It doesn’t jump out at you in the code.

More than happy to share the component for you to test. I’ve added new methods for it in the applyop and curve modules. So I’d like to post a push request to git for review too once this new component is working and tested.