Winner
09-20-2008, 01:38 AM
I`ve known about this problem for a while in maya.. and seemed to manage ok with workarounds... but now the strange issue with "getAttr -t" returning garbage values is really throwing a spanner in the works...
So does anyone have any workarounds? ( this is just for translation attributes.. thats all )
I`ve tried the usual ...constraining a new object to the one I'm trying to query and using that, direct connections instead of constraints, I even tried skinning an object to the one I`m trying to query, then using the skin deformation on a vertex to drive a locator! still got the same incorrect values..
whats up here? I just dont get it.
Anyone know what it is specifically in the DAG that causes it to throw these weird values back? any kind of heirarchical issues that could cause it?? ( Im simply tracking controllers on a character rig, nothing complex - just transforms ) any general fixes or workarounds yo u know about ?
( I have a motion trail script that I`ve taken through a whole game production, its pretty solid with a live update and stuff, only rarely had "getAttr -t" problems with it.. but now for some reason its just started creating messed up trails on a personal project Ive been working on for a while.. a real annoyance to be honest.. ).
So does anyone have any workarounds? ( this is just for translation attributes.. thats all )
I`ve tried the usual ...constraining a new object to the one I'm trying to query and using that, direct connections instead of constraints, I even tried skinning an object to the one I`m trying to query, then using the skin deformation on a vertex to drive a locator! still got the same incorrect values..
whats up here? I just dont get it.
Anyone know what it is specifically in the DAG that causes it to throw these weird values back? any kind of heirarchical issues that could cause it?? ( Im simply tracking controllers on a character rig, nothing complex - just transforms ) any general fixes or workarounds yo u know about ?
( I have a motion trail script that I`ve taken through a whole game production, its pretty solid with a live update and stuff, only rarely had "getAttr -t" problems with it.. but now for some reason its just started creating messed up trails on a personal project Ive been working on for a while.. a real annoyance to be honest.. ).