Can't get component root in post custom step

[corvineMaster]

Whenever I try to get the root of a shifter component (ex: self.component(“control_C0”).root), I end up getting the full path name because it’s the same name as the root node of the module’s guide template. Python doesn’t seem to like it when I try to reference full name spaces, so how can I fix this?

[chrislesage]

Instead, reference a unique node. Try this instead:

Rename roots and npo groups

What I always do is reference the control, and then climb the hierarchy to get the parent that I need. For example: import pymel.core as pm theControl = pm.PyNode('wheel_L1_ctl') theRoot = theControl.getParent() Then you can run rigbits.addNPO on theRoot. No need to rename anything, as long as you can find a unique path to it. Or theControl.getParent(2) if the root is higher up in the hierarchy. The number is how many nodes to climb, so getParent(0) would be the node itself. getParent(1) is …

What does “Python doesn’t seem to like it” mean? Show exactly what code you’re using, or errors you’re getting. You can definitely use long names to get nodes too.

[corvineMaster]

Oh, I didn’t know “.getParent” was a thing you could do! I always used pm.listRelatives(theControl, p=1), but this feels much more intuitive. The rigbits.addNPO solution also worked for me. Thank you for the help!