Hey Sergio, which version are you using, I can't repro in 2014. Cheers -A
----------------------------------------------- Ahmidou Lyazidi Director | TD | CG artist http://vimeo.com/ahmidou/videos http://www.cappuccino-films.com 2013/11/9 Sergio Mucino <[email protected]> > Okay. It's a bug then. Thanks! > > > On 07/11/2013 5:44 PM, Ahmidou.xsi wrote: > > There are a few cases where this is happening. It used to fo the same thing > when a camera was used in an ice tree and you undo the cam manipulation, but > they fixed it a few version ago. The only thing you can do is report it > > > Le 8 nov. 2013 à 08:51, Sergio Mucino <[email protected]> > <[email protected]> a écrit : > > I'm kinda puzzled by this. I have a Get Data node fetching the > .kine.local.pos data from a certain object. The funny thing is that if I take > this object and turn on ANY of its position limits (.kine.local), the ICE > node loses the reference! (It goes into error stating that the attribute > reference cannot be resolved). Removing the limits does not fix it... I have > to manually refresh the node (by changing the referenced property, and > setting it back to the one I need). Is there a reason why setting position > limits on an object (I have to yet test with rotations) will make a Get Data > node referencing said position go bonkers? Curious... > -- > <Sergio Mucino_Signature_email.gif> > > >
<<Sergio Mucino_Signature_email.gif>>
