Anyone has some tips for this one?
On Wed, Feb 16, 2011 at 2:01 AM, Moritz Moeller <[email protected]> wrote: > So I had some code that used a LightContext* to get a resp. light's > matrix. This code always worked until and including Nuke 6.1 but now > occasionally crashes in 6.2. > So I replaced it with a direct call to the light itself. > > Looks like this > > _for_each ( const LightContext* l, lights ) { > LightOp* light( l->light() ); > > // old code, worked until 6.1, now sometimes crashes in 6.2 > ... l->transforms()->object_matrix().array() > > // new method, seems to work but causes below messages > ... light->matrix().array(); > > This triggers lots of those: > > MatrixArray::matrix(13) - Warning, matrix is unassigned > MatrixArray::matrix(19) - Warning, matrix is unassigned > MatrixArray::matrix(7) - Warning, matrix is unassigned > MatrixArray::matrix(13) - Warning, matrix is unassigned > MatrixArray::matrix(19) - Warning, matrix is unassigned > MatrixArray::matrix(7) - Warning, matrix is unassigned > > > What is happening here? > The light is fetched from a Scene that I create from a previously > validate()d GeoOp. > > More interesting although: what is the suggested & working[tm] way of > getting the xform of a LightOp, for rendering, in Nuke 6.2? > > And how is it possible that a minor Nuke version update makes working > code instable and there is zero info about this in any NDK/Nuke release > notes? > > > > .mm > _______________________________________________ > Nuke-dev mailing list > [email protected] > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > -- paolo berto the /*jupiter jazz*/ group — visual research mercenaries of jupiter jazz ltd. www.jupiter-jazz.com _______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
