Blender Git Commit Log

BLI: support multiple arguments for value in *_as methods of Map

This allows us to build more complex values in-place in the map.
Before those values had to be build separately and then moved into the map.

Existing calls to the Map API remain unchanged.

Geometry Nodes: use virtual arrays in internal attribute api

A virtual array is a data structure that is similar to a normal array
in that its elements can be accessed by an index. However, a virtual
array does not have to be a contiguous array internally. Instead, its
elements can be layed out arbitrarily while element access happens
through a virtual function call. However, the virtual array data
structures are designed so that the virtual function call can be avoided
in cases where it could become a bottleneck.

Most commonly, a virtual array is backed by an actual array/span or
is a single value internally, that is the same for every index.
Besides those, there are many more specialized virtual arrays like the
ones that provides vertex positions based on the `MVert` struct or
vertex group weights.

Not all attributes used by geometry nodes are stored in simple contiguous
arrays. To provide uniform access to all kinds of attributes, the attribute
API has to provide virtual array functionality that hides the implementation
details of attributes.

Before this refactor, the attribute API provided its own virtual array
implementation as part of the `ReadAttribute` and `WriteAttribute` types.
That resulted in unnecessary code duplication with the virtual array system.
Even worse, it bound many algorithms used by geometry nodes to the specifics
of the attribute API, even though they could also use different data sources
(such as data from sockets, default values, later results of expressions, ...).

This refactor removes the `ReadAttribute` and `WriteAttribute` types and
replaces them with `GVArray` and `GVMutableArray` respectively. The `GV`
stands for "generic virtual". The "generic" means that the data type contained
in those virtual arrays is only known at run-time. There are the corresponding
statically typed types `VArray<T>` and `VMutableArray<T>` as well.

No regressions are expected from this refactor. It does come with one
improvement for users. The attribute API can convert the data type
on write now. This is especially useful when writing to builtin attributes
like `material_index` with e.g. the Attribute Math node (which usually
just writes to float attributes, while `material_index` is an integer attribute).

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

Merge branch 'master' into greasepencil-object

Merge branch 'master' into eevee-gpencil

Merge branch 'blender-v2.93-release'

Fix T87321: GPencil Arrange strokes not consistent with industry standards

Now if one stroke in the extremes of the stack is selected, other strokes are moved.

Reviewed By: pepeland, Dantti

Maniphest Tasks: T87321

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

Functions: extend virtual array functionality

This adds support for mutable virtual arrays and provides many utilities
for creating virtual arrays for various kinds of data. This commit is
preparation for D10994.

add missing include

cleanup

cleanup

cleanup

Fix test to not use Ankit's directory name.

Merge branch 'master' into virtual-array-attributes

Merge branch 'master' into temp-gpencil-bezier-stroke-type

USD Import: remove instancing functionality.

Temporarily removing collection-based instancing
experimental feature to simplify the review of
the current patch (differential D10700).
Instancing can be added back in a future patch.

Merge branch 'usd-importer-T81257-merge' of https://gitlab-master.nvidia.com/omniverse/blender into omniverse

USD Import: removed obsolete code.

USD Import: USDMaterialReader refactor.

Broke up more complex code into multiple functions
and reduced the nesting level of conditionals.

Geometry Nodes Curves: Add generic interpolattion to evaluated points

GPencil: Use geom update flags in update functions