On 06/20/2011 06:33 PM, Jonathan Egstad wrote: > The Render base class attempts to correlate GeoInfos between two separate > time-sliced > GeometryLists by using the GeoInfo::out_id() hash, but as I recall it does > nothing to > correlate individual Primitives inside each respective GeoInfo. If I recall > there may > be a test for point counts to make sure that they haven't changed between > time slices.
Jon, thanks for taking the time but I think you didn't read my mail carefully. :) I have no issues with particle numbers changing over the shutter at all. I handle this w/o issues in my code. Most 3d apps let particles die mid frame, Nuke is no exception here. Since I wrote four industry-grade RIB exporters already, at various stages in my life, I can deal with this in my sleep to ensure the renderer gets stable topology. :P This thing I reported is a completely different issue. It is about particle data ending up in one GeoInfo but belonging into another. And again, this works or at least works better when I render the frame 1st with ScanlineRender. When I render with my renderer I get the munged up data (position and attributes). .mm _______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
