dag.findComponentChildren2 fails after a rig was built.
jhoolmans opened this issue · 0 comments
jhoolmans commented
Having both the guide and rig in your scene from Shifter will cause this function to fail due to name clashing.
Related issue: mgear-dev/shifter#70
Error log:
# Traceback (most recent call last):
# File "/home/jhoolmans/Development/mgear_dev/mgear_dist/release/scripts/mgear/shifter/guide.py", line 1028, in updateComponentName
# guide.updateProperties(self.root, newName, newSide, newIndex)
# File "/home/jhoolmans/Development/mgear_dev/mgear_dist/release/scripts/mgear/shifter/guide.py", line 921, in updateProperties
# comp_guide.rename(root, newName, newSide, newIndex)
# File "/home/jhoolmans/Development/mgear_dev/mgear_dist/release/scripts/mgear/shifter/component/guide.py", line 497, in rename
# self.parent, oldName, oldSideIndex)
# File "/home/jhoolmans/Development/mgear_dev/mgear_dist/release/scripts/mgear/core/dag.py", line 223, in findComponentChildren2
# return [pm.PyNode(x) for x in children]
# File "/usr/autodesk/maya/lib/python2.7/site-packages/pymel/core/general.py", line 2282, in __new__
# raise _objectError(name)
# pymel.core.general.MayaNodeError: Maya Node does not exist (or is not unique):: u'chain_C0_2_loc'