[Bf-committers] 2.60 feature(s)

j.bakker at atmind.nl j.bakker at atmind.nl
Wed Aug 24 22:25:37 CEST 2011

Hi pete!

We need to look into the stalling. I understand that the current
implementations can potentially stall the execution of the new system. We
need to verify if these nodes will only used near input nodes. If this is
the case it should be possible to stall the execution. The user won't see
the difference.

I also have "nodes with constant output", perhaps an idea to use it for the
coverage node. (I want to experiment this with the LogLum algorithm)


Original Message:
From: pete larabell xgl.asyliax at gmail.com
Date: Wed, 24 Aug 2011 14:36:39 -0500
To: bf-committers at blender.org, bf-vfx at blender.org,
lukas.toenne at googlemail.com, j.bakker at atmind.nl
Subject: 2.60 feature(s)

Also, what about jbakker's Compo?  These nodes (all 3) require full
buffer to operate, and would stall the whole execution branch they are

Anyone care to offer advice on when these rightfully should get submitted?


mail2web LIVE – Free email based on Microsoft® Exchange technology -

More information about the Bf-committers mailing list