tredeger
11-12-2006, 09:38 PM
Grrr arghh! I'm having trouble getting my attrs connected properly.
My destination attr is a multi called neutralPose. It's made up of 2 compound attrs- neutralPoseTranslate and neutralPoseRotate, each of which has an X,Y, and Z component.
I first tested the type of each attr using `getAttr -type myDestinationNode.destinationAttr`
just to make sure I have type compatibility.
My results:
getAttr -type "mwc.np" ;
// Result: TdataCompound //
getAttr -type mwc.np[0];
// Result: TdataCompound //
getAttr -type mwc.np[0].npt;
// Result: double3 //
getAttr -type mwc.np[0].nptx;
// Result: double //
--------------
ok, so for the source node, I created corresponding attrs:
addAttr -longName neutralPose -shortName np -numberOfChildren 2 -attributeType compound sourceNode;
addAttr -longName neutralPoseTranslate -shortName npt -attributeType double3 -parent neutralPose sourceNode;
addAttr -longName neutralPoseTranslateX -shortName nptx -attributeType double -parent neutralPoseTranslate sourceNode;
... and so forth
Now, I wire up the corresponding source and destination attrs. I've tried a number of permutations, currently I'm wiring up pretty much everything explicitly with a 'connectAttr' command':
.np --> .np[0]
.npt --> .np[0].npt
.nptx --> .np[0].nptx
etc.
In the connection editor, everything seems to be correct.
In the hypergraph, all the individual connects seem to be correct as well.
.np --> .np[0] has a light blue connection line
.npt --> .np[0].npt has a green connection line
.nptx --> .np[0].nptx etc. all have dark blue connection lines.
There is one grey dotted line but the graph won't indicate the attrs on mouseover.
So everything looks connected.
EXCEPT the source values are not driving the destination values. Does anyone know what's wrong with this? Thanks a tone in advance for any help. I've been trying just about every combination and i'm starting to feel like a monkey at a typewriter here.
My destination attr is a multi called neutralPose. It's made up of 2 compound attrs- neutralPoseTranslate and neutralPoseRotate, each of which has an X,Y, and Z component.
I first tested the type of each attr using `getAttr -type myDestinationNode.destinationAttr`
just to make sure I have type compatibility.
My results:
getAttr -type "mwc.np" ;
// Result: TdataCompound //
getAttr -type mwc.np[0];
// Result: TdataCompound //
getAttr -type mwc.np[0].npt;
// Result: double3 //
getAttr -type mwc.np[0].nptx;
// Result: double //
--------------
ok, so for the source node, I created corresponding attrs:
addAttr -longName neutralPose -shortName np -numberOfChildren 2 -attributeType compound sourceNode;
addAttr -longName neutralPoseTranslate -shortName npt -attributeType double3 -parent neutralPose sourceNode;
addAttr -longName neutralPoseTranslateX -shortName nptx -attributeType double -parent neutralPoseTranslate sourceNode;
... and so forth
Now, I wire up the corresponding source and destination attrs. I've tried a number of permutations, currently I'm wiring up pretty much everything explicitly with a 'connectAttr' command':
.np --> .np[0]
.npt --> .np[0].npt
.nptx --> .np[0].nptx
etc.
In the connection editor, everything seems to be correct.
In the hypergraph, all the individual connects seem to be correct as well.
.np --> .np[0] has a light blue connection line
.npt --> .np[0].npt has a green connection line
.nptx --> .np[0].nptx etc. all have dark blue connection lines.
There is one grey dotted line but the graph won't indicate the attrs on mouseover.
So everything looks connected.
EXCEPT the source values are not driving the destination values. Does anyone know what's wrong with this? Thanks a tone in advance for any help. I've been trying just about every combination and i'm starting to feel like a monkey at a typewriter here.