I found the error of my ways, actually. When setting the VArray.P() as screen-space coordinates, I wasn't transforming the Z coordinate properly.
Everything is working fine now. :) Sorry for the noise, Ivan On Sun, Nov 13, 2011 at 11:23 PM, Ivan Busquets <ivanbusqu...@gmail.com>wrote: > Hi all, > > I'm having some trouble with the following scenario. > > I have a CameraOp that uses a custom LensNFunc. In my LensNFunc, I'm only > modifying the P() attribute of the passed in VArray. This works fine, > except for the fact that it messes up the motion vectors output of the > ScanlineRender. Even with a simple "perspective projection" function, I can > get the results to match those of a standard camera, except for the motion > vectors output. > > I've tried writing over both the MB and VEL channels of the VArrays passed > to my LensNFunction, but the ScanlineRender doesn't seem to care about them. > What does ScanlineRender use to compute motion vectors before writing them > out? > > FWIW, if I turn on multi-sampling in the ScanlineRender I do get a correct > result, so I assume my the scene is being split correctly, and my LensNFunc > is performing the perspective projection for each split, but for some > reason the motion vector output is way off. > > Any help / ideas? > > Thanks, > Ivan >
_______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
