Ah thanks, that's good to know. I was misinterpreting dag. I put it there
because the node I was struggling with had no cycles of its own, but its
ancestors had some (dozens, if you believe cycleCheck). Without dag=True, I
got nothing, and with it, I got a page of text. Still, if this node doesn't
That dag argument looks suspicious, how come you include it?
dag (dag) | Also look for cycles due to relationships in the DAG. For each
DAG node, the parenting connection on its children is also considered when
searching for cycles. - Reference
If I create a cube and a cone, and parent constrain the cube to the cone,
then do
cmds.cycleCheck('pCube1.r', dag=True, list=True)
I get
# Result: [u'pCube1.rotateY',
u'pCube1_parentConstraint1.constraintRotateY',
u'pCube1.rotateX',
u'pCube1_parentConstraint1.constraintRotateX',
Are you able to post an example or reproducible of one of the cycle check
problems you are seeing?
Looking through the results, the first one is a parent constraint on a
joint. This is just how parent constraints work - the constraint outputs
the rotation and translation to the joint, while the
