Pixel space implies 0..width and ..height range instead of normalized, so I don't think that's right either.
Orthographic cameras don't need a division, maybe there's some code that does one but the w component would always be 1. On Thu, Jun 13, 2013 at 6:14 PM, Antony Riakiotakis <kal...@gmail.com> wrote: > +1 for not using camera here. Since you are transforming by the frame's > width/height, "pixel space" is more correct I think. > > Also I thought that even orthographic cameras need homogenous coordinate > division at the end, isn't that how it is in blender's pipeline? > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
