On 16/06/11 11:45, Moritz Moeller wrote:
On 06/16/2011 11:15 AM, Peter Pearson wrote:
On 16/06/11 10:54, Moritz Moeller wrote:
See subject. These are methods of DD::Image::Scene.
They're used by the scanline render to control motion blur.
Control? mb_scene() is a query/getter function, not a setter, unless I
miss something.
Yeah, mb_type() is a getter, mb_scene() returns a pointer to the scene
the scanline render uses to render the frames either side of the target
frame before it blends them (or to output them to motionvector channels).
If motionblur isn't enabled, mb_scene() should return NULL.
The reason I ask is that we see crashes inside Nuke (6.3b20) which are
related to GeoInfo objects becoming invalid while we access them.
They are fluctuating so likely related to threading/missing locks/locksg
going out of scope too early.
This only happens on particle geometry in some special cases.
I thought there may be some callbacks that now 'prep' geo when it is
queried at sub-frame time deltas and this could be one of them.
Is this with your own plugins, or are you seeing this with stock 6.3 nodes?
If the latter, can we have an example script which exhibits the problem
please?
Thanks,
Peter
--
Peter Pearson, Software Engineer
The Foundry, 6th Floor, The Communications Building,
48 Leicester Square, London, UK, WC2H 7LT
Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550
Web: www.thefoundry.co.uk
The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027
_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
