PDA

View Full Version : node connection problem!!

M-J
10-04-2002, 03:06 PM
hi everyone,

i recently stumbled across a problem in maya while trying to write a MEL-script and i just don't seem to find a logical solution to this, so i thought maybe one of you knows:

well, the situation was that i had an object A which was pointConstrained to an object B, so the translate channels of A were controlled by B.
when i now use the command "connectionInfo -destinationFromSource B.tx/ty/tz" then i get the pointConstraint-Node as the destination for each of B's translate channels. now, when i use e.g. B's translateY channel as a driver for another object C via a set driven key then i don't get the pointConstraint-Node as a destination for that channel anymore, but i get C's driven channel.
that doesn't make any sense to me especially when i use the connectionInfo command on the constrained object A ("connectionInfo -sourceFromDestination A.tx/ty/tz") . then i get the pointConstraint-Node as a source for every translate channel of object A. so the connection is still there but it isn't listed anymore from B's point of view. what does that mean? how does maya know that there's still a pointConstraint-connection from B's translateY-channel to A's translateY-channel?

i hope you all get what i'm trying to say :-) and i hope someone can help me with that

thanx guys

MJ
playmesumch00ns
10-04-2002, 04:28 PM
As I understand it, you're connecting B's translateY channel output to the pointConstraint node, and also to C via a SDK. So, B has two 'children' from its node, and presumably the connectionInfo is just listing the latest one (which would be why connectionInfo on A gives you the correct result).

A more pertinent question to ask would be, "Does it work?" if the answer is yes, don't worry too much about it. If you want to find out if Maya still 'knows' where the connections are going, simply list the downstream connections of B in the hypergraph, my guess is you'll see both A and C below it.
M-J
10-04-2002, 05:12 PM
i thought about that as well...i mean that the command lists just the latest connections, but then that would really restrict you in accessing and querying the earlier made connections via a MEL-Script (which was the problem in my case)...not a very good solution in my opinion

well, might be i'm worrying too much :-)
CGTalk Moderation
01-13-2006, 06:00 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.