And it won't use a silly temp constraints methodology like the factory one does (was that ever addressed?), which means it will work as expected with constraint compensation on if the object is constrained, and won't suffer from direction constraints taking precedence over pose ones.
The match commands are probably the very first thing anybody doing any rigging/set dressing should replace from the factory ones, they are mostly useless outside the absolute simplest scenarios. On Tue, Dec 18, 2012 at 9:59 AM, César Sáez <cesa...@gmail.com> wrote: > There's an old bug when the rotation parameters have fcurves. > > The OM way always works: > objA.Kinematics.Global.Trasnform = objB.Kinematics.Global.Transform > > Cheers! > > On Mon, Dec 17, 2012 at 11:38 PM, Jeremie Passerin <gerem....@gmail.com>wrote: > >> >> Yeah that sounds like the bug we have too ! >> Good I'm not crazy. If someone has repro steps, I'll be happy to report >> it once more to the Softimage Beta. >> >> >> On 17 December 2012 14:29, Sam Cuttriss <tea...@gmail.com> wrote: >> >>> ah good good, >>> ive been getting this a bunch lately in 2012. >>> matches positions but often neglects rotation. >>> >> >> > -- Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!