Blender Git Commits

Blender Git "temp-modifiers-instancing" branch commits.

Page: 5 / 7

October 27, 2020, 03:54 (GMT)
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.
October 27, 2020, 03:44 (GMT)
Geometry Nodes: Add utility to position point randomly on 3D triangle
October 27, 2020, 03:41 (GMT)
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.
October 26, 2020, 19:27 (GMT)
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.
October 26, 2020, 17:27 (GMT)
Cleanup: remove unused modifier property
October 26, 2020, 17:23 (GMT)
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.
October 26, 2020, 16:53 (GMT)
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.
October 26, 2020, 13:16 (GMT)
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.
October 26, 2020, 12:29 (GMT)
Geometry Nodes: connect group input and output by default
October 26, 2020, 12:27 (GMT)
Geometry Nodes: improve node tree evaluation

This change reduces the number of unnecessary copies of data
and avoids computing the same value more than once.
October 26, 2020, 11:27 (GMT)
Geometry Nodes: initial Transform node

Most of this code has been written by @HooglyBoogly.
I just changed the exec funtion so that it does not have to make
a copy of the mesh.
October 26, 2020, 11:25 (GMT)
Geometry Nodes: add utility method to check if a geometry has a mesh
October 26, 2020, 11:10 (GMT)
Merge branch 'master' into geometry-nodes
October 24, 2020, 12:38 (GMT)
Merge branch 'master' into geometry-nodes
October 23, 2020, 13:18 (GMT)
Merge branch 'master' into geometry-nodes
October 23, 2020, 13:13 (GMT)
Geometry Nodes: make some function nodes available

We might not want to have all those nodes in a final version.
Some of them have been added with particle nodes in mind.
However, to test the evaluation system it is useful to have a
couple of nodes available.

Those nodes should "just" work, because their implementation
is reused from the particle nodes project.
October 23, 2020, 13:09 (GMT)
Geometry Nodes: improve node group evaluation

This adds support for nodes that have a multi-function implementation.
That includes various function nodes like Math, Combine Vector, ...

Furthermore, there is support for implicit conversions now. So it should
work when one connects e.g. a float to an integer and vice versa.
October 23, 2020, 13:05 (GMT)
Nodes: add utility methods
October 23, 2020, 13:01 (GMT)
Functions: add utility method
October 23, 2020, 03:59 (GMT)
Geometry Nodes: Resolve some missing 3D viewport updates

These two functions "snode_notify" and "ED_node_tag_update_id" appear to
be mostly duplicates. However, there is already a case for each type of
built-in node tree, so it makes sense to add one for the geometry node
tree as well. This doesn't solve the update issues for changing number
in buttons, that must be handled somewhere else.
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021