Blender Git Commits

Blender Git "geometry-nodes-deduplicate-float-math" branch commits.

Page: 9 / 11

October 27, 2020, 14:53 (GMT)
Fix missing null check in recent commit
October 27, 2020, 14:43 (GMT)
Cleanup: Use proper C++ types
October 27, 2020, 13:59 (GMT)
Geometry Nodes: initial support for bool group inputs

Still need to work on the uilayout inside the modifier.
October 27, 2020, 13:54 (GMT)
Geometry Nodes: support vector inputs to geometry group
October 27, 2020, 12:44 (GMT)
Geometry Nodes: initial support for displaying group inputs in modifier

This uses the previously added id properties on the nodes modifier
to store values that are passed into the geometry node group.
October 27, 2020, 11:09 (GMT)
Geometry Nodes: enable nodes modifier in edit mode
October 27, 2020, 04:15 (GMT)
Geometry Nodes: Fix memory leak
October 27, 2020, 04:12 (GMT)
Merge branch 'master' into geometry-nodes
October 27, 2020, 04:00 (GMT)
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.
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.
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021