Blender Git Commits

Geometry Nodes: Add initial scattering nodes

The first is a "Point Distribute" node, which takes a mesh and outputs a
pointcloud, scattering points randomly on the surface based on the input
density. The distribution algorithm is extremely basic at this point, and
doesn't take into account an attribute weight at each vertex.

The second node is a "Point Instance" node, which is mainly a placeholder
until the engineering design for how to work with instancing in geometry
nodes is decided. For now it just runs the same code that the convert
pointcloud to mesh operator uses.

Geometry Nodes: Add function to create a temporary pointcloud

We needed a "nomain" funciton similar to the one we have for meshes in
order to add a working pointcloud for the geometry nodes.

Geometry Nodes: Add utility to position point randomly on 3D triangle

Geometry Nodes: Add pointcloud support to geometry class

This adds another set of the same mesh functions but for pointclouds.
There are probably better ways to generalize this functionality, but that
may have to be rethought in the future anyway if we want to store
multiple of each type. And anyway it's handy to have a specific set of
"pointcloud" functions available in the node implementations.

More fixes for dyntopo undo and vertices (face data still isn't
implemented).

Merge branch 'master' into cycles_procedural_api

Geometry Nodes: Initial mesh boolean node

This uses the code from the rewritten boolean modifier from 2.91 as a node.
The implementation is about as minimal as it can get, since for now the use
case of this node is mostly to test multiple geometry outputs and inputs.

The boolean code requires a BMesh, so the node converts the input meshes
to BMesh, so the bmesh is added as a dependency to the nodes module.

Geometry Nodes: Add operation enum to boolean node

Cleanup: remove unused modifier property

Geometry Nodes: initial test trying to use id properties to initialize group inputs

The settings can only be set via Python currently. The matching between properties
and group inputs is based on the socket identifier (which is e.g. `Input_5`).
Maybe we'll have to use a different matching strategy in the future, will see.

Animation: Change active FCurve in box/circle/lasso select

Update the active FCurve when box/circle/lasso-selecting, such that after
the operator has finished the active curve is actually the last-operated-on
FCurve.

The operator already would deactivate the active FCurve. However, it would
not re-activate one any more, which caused the active keyframe to become
inactive.

Merge branch 'master' into xr-actions-D9124

Apply formatting

XR: Support operator properties for actions

Pointers to op properties are stored in the XR session state as
IDProperty* and applied upon op execution. The actual properties
themselves are stored as key map items (new "XR" and "XR Session"
key maps were added to the blender default key maps).

The "XR" key map is intended to store op properties for action sets
that are saved in add-on (e.g. the VR Scene Inspection add-on) prefs.
The "XR Session" key map is intended to store op properties for scene
action sets, with these properties used for the XR session.

In this way, scene action sets can configure properties without
worrying about overwriting properties for action sets saved in prefs.

Geometry Nodes: store id properties in nodes modifier

The properties are not used yet, but can already be accessed with Python
using `modifier.settings['setting name']`.

The plan is to use id properties to store the parameters that the modifier
passes into the geometry node group.

Fix build error when disabling WITH_XR_OPENXR

Merge branch 'geometry-nodes' into geometry-nodes-boolean-node

Ensure custom asset repository names are unique

These names are used as identifiers for the UI, we have to ensure their
uniqueness.

Fix T81874: Box Select Keyframes doesnt set an active keyframe

Set the active keyframe on box/circle/lasso select in the graph editor.

For every FCurve that is influenced by the select operator that doesn't
have an active keyframe yet, the right-most keyframe is marked as the
active Keyframe.

Note that what is seen as the active keyframe for the graph editor also
depends on the active FCurve, which is not changed by box/circle/lasso
select.

Geometry Nodes: support evaluation with more than one group input

Group inputs are not yet exposed in the modifier. For now I just added
a simple float setting that will be passed to every float input of the group.
Inputs of other types have some default value.