Revision 5c2730f by Jacques Lucke (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 18, 2020, 11:25 (GMT) |
Geometry Nodes: use attribute api in point distribute node |
Revision 866a56f by Jacques Lucke (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 18, 2020, 11:20 (GMT) |
Geometry Nodes: initial generic attribute access API I will have to do a couple more iterations on this api in the upcoming weeks, but for now it should be good enough. The API adds an indirection for attribute access. That has the following benefits: * Most code does not have to care about how an attribute is stored internally. This is mainly necessary, because we have to deal with "legacy" attributes such as vertex weights and attributes that are embedded into other structs such as vertex positions. * When reading from an attribute, we generally don't care what domain the attribute is stored on. So we want to abstract away the interpolation that that adapts attributes from one domain to another domain (this is not actually implemented yet). Accessing attributes through this indirection does have a performance penalty. In later iterations of this API I want to reduce this penalty and extend the API so that performance critical code does not have to go through the indirection for every attribute access. Other possible improvements for later iterations include: * Actually implement interpolation between domains. * Don't use inheritance for the different attribute types. A single class for read access and one for write access might be enough, because we know all the ways in which attributes are stored internally. We don't want more different internal structures in the future. On the contrary, ideally we can consolidate the different storage formats in the future to reduce the need for this indirection. * Remove the need for heap allocations when creating attribute accessors. |
Revision 63a286e by Jacques Lucke (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 18, 2020, 11:00 (GMT) |
Functions: add float2 cpp type |
Revision 15c6390 by Dalai Felinto (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 18, 2020, 01:03 (GMT) |
Merge remote-tracking branch 'origin/master' into geometry-nodes |
Revision b05f841 by Dalai Felinto (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 18, 2020, 01:02 (GMT) |
Cleanup: Remove most of "#ifdef WITH_GEOMETRY_NODES" The ones around the simulation datablock are still there, since they are not needed for the features planned for master yet. |
Revision 0783a9a by Dalai Felinto (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 18, 2020, 01:02 (GMT) |
Cleanup: Remove all of "#ifdef WITH_POINT_CLOUD" Since Point Cloud was removed from experimental this is no longer needed. |
Revision 083cde0 by Dalai Felinto (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 18, 2020, 01:02 (GMT) |
Geometry Nodes: Unify icons -> use ICON_NODETREE for everything Until there is a icon made specially for this, the nodetree icon is up for grabs. Using it in the nodegroup + modifier + editor helps the users to make a connection on where to edit those modifiers. |
Revision 4db4177 by Dalai Felinto (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 17, 2020, 23:31 (GMT) |
Remove Point Cloud object from experimental The point cloud object is the only one that will support instancing at first. So we can expose it as a regular object. It is limited since it has no edit mode. But this is not different than the volume object. |
Revision c0f3d31 by Dalai Felinto (geometry-nodes, geometry-nodes-active-modifier-drawing, geometry-nodes-deduplicate-float-math, geometry-nodes-distribute-points, geometry-nodes-mix-attributes, geometry-nodes-point-separate-node, temp-geometry-nodes-distribute-points-cleanup) November 17, 2020, 23:30 (GMT) |
Remove Geometry Nodes Editor from experimental As part of preparing this work for master, with an initial subset of working functionalities the Geometry Nodes Editor can be exposed for everyone. (it also helps people that are testing the branch) |
November 17, 2020, 16:20 (GMT) |
use data type and domain enum in random attribute node |
November 17, 2020, 15:58 (GMT) |
initial attribute creation |
November 17, 2020, 15:39 (GMT) |
initial WriteAttribute |
November 17, 2020, 14:25 (GMT) |
initial random attribute node |
November 17, 2020, 14:22 (GMT) |
Geometry Nodes: Update boilerplate code for attributes |
November 17, 2020, 14:08 (GMT) |
cleanup |
November 17, 2020, 14:03 (GMT) |
Merge branch 'geometry-nodes' into geometry-nodes-attribute-nodes |
Revision f623b1a by Germano Cavalcante November 17, 2020, 13:36 (GMT) |
Transform: New feature to set a custom 'Snap With' Ref T66484 Basically the idea is to use a modal keymap to change the current Base Point defined by `Snap With` by one that can be chosen through snapping. {F9170047} I prefer to avoid using any of the modifier buttons (Shift, Alt, Ctrl) as they can be used in the future to allow navigation during transform operations. So the shortcut chosen in this patch is the {key B}. Note: This feature is not enabled if the scene snap option is Incremental or grid. Maniphest Tasks: T66484 Differential Revision: https://developer.blender.org/D9415 # Conflicts: # source/tools |
Revision 3e146e3 by Germano Cavalcante November 17, 2020, 13:36 (GMT) |
Enable modes according to the number of times the button is pressed |
Revision 1f9c4ed by Germano Cavalcante November 17, 2020, 13:36 (GMT) |
Remove multiple modes (always return the object to the initial position) |
Revision 96390f6 by Germano Cavalcante November 17, 2020, 13:36 (GMT) |
Fix: Scale operation and statusbar, Enable multi snappoints and snap inversion |
|
|
|


Master Commits
MiikaHweb | 2003-2021