Geometry Nodes: do not reference custom data layers when copying mesh
We can't use that for now, because the original mesh might be freed before the new copied mesh. When the original mesh is freed, the shared layers will be freed as well.
This can probably be improved in the future, so that we can actually share attribute arrays between meshes. An approach similar to how geometries and components are shared should work as well.
A geometry now contains zero or more geometry components. A geometry component is a subclass off GeometryComponent. Currently, there is a MeshComponent and PointCloudComponent.
A geometry contains at most one component of each type. Individual components can be shared between multiple geometries to avoid unnecessary copies. For that, each component has a user count that determines when the component will be freed and whether it is mutable.
Code working with geometries can either work with the components directly, or use the utility functions on the geometry that cover the most common operations.
In the future, additional component types can be added. For example, we'll probably need components for curves and volumes. Furthermore, something like an InstancesComponent can be added, which contains points with attributes and references a geometry/object/collection that is instanced on all the points.
Master Commits
MiikaHweb | 2003-2021