Blender Git Commits

Correct transform of instances

Merge branch 'master' into temp-geometry-nodes-instances-api-v2

Add implicit make instances real operation for "write" nodes

Other nodes that create new geometry instead of modifying existing geometry
should read the geometry like the point distribute node does in this branch.

Merge branch 'temp-geometry-nodes-instances-api-v2' of git.blender.org:blender into temp-geometry-nodes-instances-api-v2

Geometry Nodes: Instances API, support in point distribute node

This patch changes the object info node to always output an instance.
Theoretically, this change should be invisible to the user, because
we plan to make instances real on demand. The benefit is improved
performance because we can avoiding copying the input geometry when
it's only needed for read operations.

To make this work, we need a proper API to enable recursive reading
of instanced geometry. This is essential, because we can even have
collection instances in the `InstancesComponent`, which have no
geometry of their own. And then any object in that collection could
also contain an instance with a reference to another collection, etc.
That might seem crazy, but it's essential for many more complicated
workflows like the tree sample file.

Another consideration is that currently, every single instance contains
a reference to its data. This is inefficient since most of the time
there are many locations and only a few sets of unique data. When we
add the ability to instance a geometry set directly, this will be
more important. So this patch adds a `GeometryInstanceGroup` to support
this future optimization.

Two APIs to the instances component are provided here. First is a
callback approach that executes a function for every "final" geometry
set. This can be used to optimize for many instances, to avoid heap
allocations for each instance.

The second API is one that returns a vector of `GeometryInstanceGroup`.
This may be less efficient when there are many instances, but it makes
more complicated operations like point distribution that need to iterate
over input geometry multiple times much simpler.

Even then, this patch makes the point distribute code much more
complicated. It may be possible to simplify it further.

The last TODO is support for making instances real on demand, which
I am currently working on. The change to the object info node can't
land without it. The transform spaces may be incorrect too.

Differential Revision: https://developer.blender.org/D10327

Merge branch 'master' into temp-geometry-nodes-instances-api-v2

Add comments

Remove debugging code

Geometry Nodes: Point distribute support for instances

This completes the work to implement instancing on instances.
The density attribute works, and attributes are interpolated to the
output like before.

The code is much more complicated than before, and harder to understand.
Some cleanup is likely possible to help, but to an extent it is unavoidable.

Geometry Nodes: Better support instances in point instance node

This does the elimination by distance in a single step for all instances
instead of treating each input mesh separately.

This needs some cleanup, but the bigger TODO is that attribute interpolation
gets a fair amount more complex with this implementation. Needs more thought.

WIP implementation, double vectors, sort of weird

More progress converting the point distribute node to operations

I might not continue with this approach, it seems like building a
temporary vector of geometry components will be much simpler

Merge branch 'master' into temp-geometry-nodes-instances-api

WIP: Rewrite point distribute node to correctly support instances

This does not compile, and isn't close to finished.

Add a second idea for the instances API

Merge branch 'master' into temp-geometry-nodes-instances-api

Merge branch 'master' into temp-geometry-nodes-instances-api

Geometry Nodes: Support instances in the point instance node

Geometry Nodes: Output instanced geometry from the object info node

Geometry Nodes: First pass on instance geometry set API

I think a fair amount of this will change, but this API uses a callback on
each component of a geometry set and its instances recursively.

Example uses will come in a following commit.