[Bf-committers] Proposal for unifying nodes

Daniel Genrich daniel.genrich at gmx.net
Mon Jun 15 11:47:53 CEST 2009


I am also interested in unifying this thing but in a more general 
matter. I was thinking to also have the possibility of a modifier stack 
node. This would really safe me the trouble of getting the dependancies 
between physical simulations, animated objects and rigid objects rights. 
Would also solve how to get like one inflow object (fluid) used for 2 
simulations - pretty easy using nodes.

So just be sure to define it general enough like:
NodeData {
int type;

MyNode {
NodeData *data;


Just like the modifiers are defined :)

Aurel W. schrieb:
> 2009/6/15 Matt Ebb <matt at mke3.net>:
>> No they're not. Textures need to be completely independent:
>> coordinate in -> values out.
> The problem is, with every node operating on more, than just the
> current coordinate, as a filter node does, you would need to evaluate
> the incoming texture on every coordinate, which is needed for the
> calculation. It might make sense to evaluate an Image, with an certain
> quality from such a Texture Function and then pass it on as an Image.
> If you just stick to functions you end up with the exponential
> complexity, which I described. So in texture nodes you would need to
> mix those two data types, Images and Functions, to make all operations
> possible.
> Aurel
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list