griefith/test
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
89a3478e35c2d629b88ba89fb268adb6c00a0c3a
test/scripts/startup/bl_ui/node_add_menu_geometry.py

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

948 lines
42 KiB
Python
Raw Normal View History

License Headers: Set copyright to "Blender Authors", add AUTHORS Listing the "Blender Foundation" as copyright holder implied the Blender Foundation holds copyright to files which may include work from many developers. While keeping copyright on headers makes sense for isolated libraries, Blender's own code may be refactored or moved between files in a way that makes the per file copyright holders less meaningful. Copyright references to the "Blender Foundation" have been replaced with "Blender Authors", with the exception of `./extern/` since these this contains libraries which are more isolated, any changed to license headers there can be handled on a case-by-case basis. Some directories in `./intern/` have also been excluded: - `./intern/cycles/` it's own `AUTHORS` file is planned. - `./intern/opensubdiv/`. An "AUTHORS" file has been added, using the chromium projects authors file as a template. Design task: #110784 Ref !110783.
2023-08-16 00:20:26 +10:00
# SPDX-FileCopyrightText: 2022-2023 Blender Authors
License headers: use SPDX-FileCopyrightText in all sources
2023-06-15 13:09:04 +10:00
#
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
# SPDX-License-Identifier: GPL-2.0-or-later
License headers: use SPDX-FileCopyrightText in all sources
2023-06-15 13:09:04 +10:00
Nodes: support searching for specific math operations in Add menu Previously, it was possible to search for specific math operations in link-drag-search but not in the normal add menu. This patch adds support for searching for specific operations in various math nodes. A good trick for adding e.g. a vector add node is to search for `vadd` (similarly with `iadd`). The menu itself looks unchanged. This patch only adds additional elements to the search. Pull Request: https://projects.blender.org/blender/blender/pulls/138534
2025-05-08 04:28:22 +02:00
import bpy
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
from bpy.types import Menu
from bl_ui import node_add_menu
I18n: disambiguate messages - "Lines" in the sense of number of lines - "Number" can mean "amount, count" or "index, offset" - "Second" can be an ordinal number or a unit - "Root": add the brush curve to the "square root falloff" sense - "Strip" can be a sequence or a type of hair rendering - "Constant" in the sense of a value, for the Geometry Nodes add submenu (#105447). Additionally, extract: - "Press a key" from the Keymap preferences. - "MaskLayer", upon new mask layer creation Ref #43295, #105447
2023-03-03 14:44:21 +01:00
from bpy.app.translations import (
pgettext_iface as iface_,
contexts as i18n_contexts,
)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_ATTRIBUTE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_ATTRIBUTE"
bl_label = "Attribute"
def draw(self, _context):
layout = self.layout
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeAttributeStatistic")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeAttributeDomainSize")
layout.separator()
Geometry Nodes: new Blur Attribute node The Blur Attribute node mixes values of neighboring elements in meshes and curves. Currently it supports points, edges and faces on meshes and points on curves. In theory, support for face corners could be added, but useful semantics are not obvious yet. The node calculates a weighted average of each element with its neighbors (based on curve/mesh topology). The weight of the element itself is always 1, and the weight of the neighbor elements is controlled by the weight input socket. In the future, more options for how different elements are weight can be added (e.g. smoothing groups and selection). The node can perform multiple blurring iterations to achieve a blurrier result. Generally, it is better to do multiple iterations in one node instead of using multiple blur nodes because it has better performance in the current implementation. We use the term "Blur" (instead of "Smooth") because smoothing is generally more related to removing roughness from surfaces. When viewing the result of the Blur Attribute node in the viewport, it looks like an image is blurred. While the node can also be used to smooth surfaces, other/better algorithms exists for that purpose (which e.g. don't reduce the volume of the mesh to zero with too many iterations). Differential Revision: https://developer.blender.org/D13952
2022-12-07 18:22:44 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeBlurAttribute")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeCaptureAttribute")
node_add_menu.add_node_type(layout, "GeometryNodeRemoveAttribute")
Geometry Nodes: improve search weights of some nodes
2024-04-22 18:22:05 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeStoreNamedAttribute", search_weight=1.0)
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_COLOR(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_COLOR"
bl_label = "Color"
Nodes: support searching for color blend modes in Add menu This is a follow up to #138534. It adds support for searching for all color blend operations. It's supported in Geometry Nodes, Compositor and Shader Nodes. Pull Request: https://projects.blender.org/blender/blender/pulls/138581
2025-05-09 04:02:50 +02:00
def draw(self, context):
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout = self.layout
Geometry Nodes: add support for blackbody shader node This adds the existing Blackbody shader node to geometry nodes, with the same functionality. Pull Request: https://projects.blender.org/blender/blender/pulls/114768
2023-12-13 10:10:06 +01:00
node_add_menu.add_node_type(layout, "ShaderNodeBlackbody")
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "ShaderNodeValToRGB")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "ShaderNodeRGBCurve")
layout.separator()
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeCombineColor")
Nodes: support searching for color blend modes in Add menu This is a follow up to #138534. It adds support for searching for all color blend operations. It's supported in Geometry Nodes, Compositor and Shader Nodes. Pull Request: https://projects.blender.org/blender/blender/pulls/138581
2025-05-09 04:02:50 +02:00
node_add_menu.add_color_mix_node(context, layout)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "FunctionNodeSeparateColor")
Fix: Node assets are missing from the Add menu for certain catalog names Add > Utilities submenus for Color and Field do not include assets from the correctly named catalogs due to typos: "Utilties/Color" and "Utilties/Field" respectively. Pull Request: https://projects.blender.org/blender/blender/pulls/122416
2024-05-29 05:44:47 +02:00
node_add_menu.draw_assets_for_catalog(layout, "Utilities/Color")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_CURVE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_CURVE"
bl_label = "Curve"
def draw(self, _context):
layout = self.layout
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_CURVE_READ")
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
layout.menu("NODE_MT_geometry_node_GEO_CURVE_SAMPLE")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_CURVE_WRITE")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout.separator()
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_CURVE_OPERATIONS")
layout.menu("NODE_MT_geometry_node_GEO_PRIMITIVES_CURVE")
layout.menu("NODE_MT_geometry_node_curve_topology")
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
class NODE_MT_geometry_node_GEO_CURVE_READ(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_CURVE_READ"
bl_label = "Read"
def draw(self, _context):
layout = self.layout
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeInputCurveHandlePositions")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeCurveLength")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeInputTangent")
node_add_menu.add_node_type(layout, "GeometryNodeInputCurveTilt")
node_add_menu.add_node_type(layout, "GeometryNodeCurveEndpointSelection")
node_add_menu.add_node_type(layout, "GeometryNodeCurveHandleTypeSelection")
node_add_menu.add_node_type(layout, "GeometryNodeInputSplineCyclic")
node_add_menu.add_node_type(layout, "GeometryNodeSplineLength")
node_add_menu.add_node_type(layout, "GeometryNodeSplineParameter")
node_add_menu.add_node_type(layout, "GeometryNodeInputSplineResolution")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Curve/Read")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
Cleanup: make format
2023-01-16 14:39:10 +01:00
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
class NODE_MT_geometry_node_GEO_CURVE_SAMPLE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_CURVE_SAMPLE"
bl_label = "Sample"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeSampleCurve")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Curve/Sample")
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_CURVE_WRITE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_CURVE_WRITE"
bl_label = "Write"
def draw(self, _context):
layout = self.layout
Geometry Nodes: Set Curve Normal This node allows for curves to have their evaluated normal mode changed between MINIMUM_TWIST and Z_UP. A selection input allows for choosing which spline in the curves object will be affected. Differential Revision: D16118
2022-10-03 15:50:21 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeSetCurveNormal")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeSetCurveRadius")
node_add_menu.add_node_type(layout, "GeometryNodeSetCurveTilt")
node_add_menu.add_node_type(layout, "GeometryNodeSetCurveHandlePositions")
node_add_menu.add_node_type(layout, "GeometryNodeCurveSetHandles")
node_add_menu.add_node_type(layout, "GeometryNodeSetSplineCyclic")
node_add_menu.add_node_type(layout, "GeometryNodeSetSplineResolution")
node_add_menu.add_node_type(layout, "GeometryNodeCurveSplineType")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Curve/Write")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_CURVE_OPERATIONS(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_CURVE_OPERATIONS"
bl_label = "Operations"
def draw(self, _context):
layout = self.layout
Geometry Nodes: add conversion nodes for Grease Pencil and Curves This adds two new nodes: * `Grease Pencil to Curves`: Converts each grease pencil layer into an instance that contains curves. * `Curves to Grease Pencil`: Converts top-level curve instances into grease pencil layers. This opens up many new opportunities: * Use grease pencil as input to other procedural systems that don't necessarily output grease pencil. * Generate grease pencil from scratch using geometry nodes. * Temporarily convert grease pencil data to curves to use more powerful features for curves processing. Some data on layers are not attributes yet unfortunately, so there is some special case handling for the `opacity` attribute. This was previously discussed at the geometry nodes workshop: https://devtalk.blender.org/t/2024-05-13-geometry-nodes-workshop-notes/34760#grease-pencil-14 Pull Request: https://projects.blender.org/blender/blender/pulls/124279
2024-07-22 12:29:26 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeCurvesToGreasePencil")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeCurveToMesh")
node_add_menu.add_node_type(layout, "GeometryNodeCurveToPoints")
node_add_menu.add_node_type(layout, "GeometryNodeDeformCurvesOnSurface")
node_add_menu.add_node_type(layout, "GeometryNodeFillCurve")
node_add_menu.add_node_type(layout, "GeometryNodeFilletCurve")
Geometry Nodes: new Interpolate Curves node This adds a new `Interpolate Curves` node. It allows generating new curves between a set of existing guide curves. This is essential for procedural hair. Usage: - One has to provide a set of guide curves and a set of root positions for the generated curves. New curves are created starting from these root positions. The N closest guide curves are used for the interpolation. - An additional up vector can be provided for every guide curve and root position. This is typically a surface normal or nothing. This allows generating child curves that are properly oriented based on the surface orientation. - Sometimes a point should only be interpolated using a subset of the guides. This can be achieved using the `Guide Group ID` and `Point Group ID` inputs. The curve generated at a specific point will only take the guides with the same id into account. This allows e.g. for hair parting. - The `Max Neighbors` input limits how many guide curves are taken into account for every interpolated curve. Differential Revision: https://developer.blender.org/D16642
2023-01-20 12:09:29 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInterpolateCurves")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeResampleCurve")
node_add_menu.add_node_type(layout, "GeometryNodeReverseCurve")
node_add_menu.add_node_type(layout, "GeometryNodeSubdivideCurve")
node_add_menu.add_node_type(layout, "GeometryNodeTrimCurve")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Curve/Operations")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_PRIMITIVES_CURVE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_PRIMITIVES_CURVE"
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
bl_label = "Primitives"
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
def draw(self, _context):
layout = self.layout
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeCurveArc")
node_add_menu.add_node_type(layout, "GeometryNodeCurvePrimitiveBezierSegment")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeCurvePrimitiveCircle")
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeCurvePrimitiveLine")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeCurveSpiral")
node_add_menu.add_node_type(layout, "GeometryNodeCurveQuadraticBezier")
node_add_menu.add_node_type(layout, "GeometryNodeCurvePrimitiveQuadrilateral")
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeCurveStar")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Curve/Primitives")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
class NODE_MT_geometry_node_curve_topology(Menu):
bl_idname = "NODE_MT_geometry_node_curve_topology"
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
bl_label = "Topology"
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeCurveOfPoint")
Geometry Nodes: Sort Add menu entries * In Input → Scene, move: * `Scene Time` above `Self Object` * In Geometry, move: * `Geometry to Instance` above `Join Geometry` * In Curve → Topology, move: * `Curve of Point` above `Offset Pint in Curve` * In Mesh → Read, move: * `Face Group Boundaries` above `Face Neighbors` * `Edges to Face Groups` above `Edge Vertices`
2023-08-24 16:09:58 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeOffsetPointInCurve")
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
node_add_menu.add_node_type(layout, "GeometryNodePointsOfCurve")
Cleanup: Make format
2023-09-26 17:05:36 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Curve/Topology")
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
Cleanup: Avoid capitals in Geometry Nodes Grease Pencil add menu The capitals were only used for API compatibility when the add menu was first added, they're not needed for new menus. Better to avoid since they're non-standard for menu names.
2025-04-08 09:51:28 -04:00
class NODE_MT_geometry_node_grease_pencil_read(Menu):
bl_idname = "NODE_MT_geometry_node_grease_pencil_read"
Geometry Nodes: Add "Grease Pencil" menu This adds a new Grease Pencil menu and moves the existing Grease Pencil related nodes into it. Pull Request: https://projects.blender.org/blender/blender/pulls/136498
2025-03-25 16:38:18 +01:00
bl_label = "Read"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeInputNamedLayerSelection")
node_add_menu.draw_assets_for_catalog(layout, "Grease Pencil/Read")
Cleanup: Avoid capitals in Geometry Nodes Grease Pencil add menu The capitals were only used for API compatibility when the add menu was first added, they're not needed for new menus. Better to avoid since they're non-standard for menu names.
2025-04-08 09:51:28 -04:00
class NODE_MT_geometry_node_grease_pencil_write(Menu):
bl_idname = "NODE_MT_geometry_node_grease_pencil_write"
Geometry Nodes: Add `Set Grease Pencil Color` node Adds a new `Set Grease Pencil Color` node. It was already possible to write to the color and opacity attributes using the `Store Named Attribute` node, but this required the user to know the names of the "built in" attributes. Similar to how we can set other built-in attributes (e.g. the curve radius) this adds a node to write to the following Grease Pencil attributes: * `vertex_color` (point domain): The color of a point (the alpha value is used as a mix factor with the base material color). * `opacity` (point domain): The opacity of a point. * `fill_color` (curve domain): The fill color of a stroke (the alpha value is used as a mix factor with the base material color). * `fill_opacity` (curve domain): The fill opacity of a stroke. For consistency with other nodes, there is a mode to switch between writing to the points (`Stroke` mode) and the fills (`Fill` mode). Pull Request: https://projects.blender.org/blender/blender/pulls/136260
2025-04-05 12:11:26 +02:00
bl_label = "Write"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeSetGreasePencilColor")
Geometry Nodes: Add node to set the Grease Pencil depth order Adds a new node to set the Grease Pencil depth ordering. Here are the options: * 2D Layers: Uses the Layer order + Stroke order to calculate the depth ordering. * 3D Location: Uses the 3D position of the points as the depth. This reflects the same setting that is available in the Grease Pencil object-data properties. The node is added to the `Grease Pencil` > `Write` menu. Resolves #129458. Pull Request: https://projects.blender.org/blender/blender/pulls/135914
2025-04-08 15:24:51 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSetGreasePencilDepth")
Geometry Nodes: Add `Set Grease Pencil Color` node Adds a new `Set Grease Pencil Color` node. It was already possible to write to the color and opacity attributes using the `Store Named Attribute` node, but this required the user to know the names of the "built in" attributes. Similar to how we can set other built-in attributes (e.g. the curve radius) this adds a node to write to the following Grease Pencil attributes: * `vertex_color` (point domain): The color of a point (the alpha value is used as a mix factor with the base material color). * `opacity` (point domain): The opacity of a point. * `fill_color` (curve domain): The fill color of a stroke (the alpha value is used as a mix factor with the base material color). * `fill_opacity` (curve domain): The fill opacity of a stroke. For consistency with other nodes, there is a mode to switch between writing to the points (`Stroke` mode) and the fills (`Fill` mode). Pull Request: https://projects.blender.org/blender/blender/pulls/136260
2025-04-05 12:11:26 +02:00
node_add_menu.draw_assets_for_catalog(layout, "Grease Pencil/Write")
Cleanup: Avoid capitals in Geometry Nodes Grease Pencil add menu The capitals were only used for API compatibility when the add menu was first added, they're not needed for new menus. Better to avoid since they're non-standard for menu names.
2025-04-08 09:51:28 -04:00
class NODE_MT_geometry_node_grease_pencil_operations(Menu):
bl_idname = "NODE_MT_geometry_node_grease_pencil_operations"
Geometry Nodes: Add "Grease Pencil" menu This adds a new Grease Pencil menu and moves the existing Grease Pencil related nodes into it. Pull Request: https://projects.blender.org/blender/blender/pulls/136498
2025-03-25 16:38:18 +01:00
bl_label = "Operations"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeGreasePencilToCurves")
node_add_menu.add_node_type(layout, "GeometryNodeMergeLayers")
node_add_menu.draw_assets_for_catalog(layout, "Grease Pencil/Operations")
Cleanup: Avoid capitals in Geometry Nodes Grease Pencil add menu The capitals were only used for API compatibility when the add menu was first added, they're not needed for new menus. Better to avoid since they're non-standard for menu names.
2025-04-08 09:51:28 -04:00
class NODE_MT_geometry_node_grease_pencil(Menu):
bl_idname = "NODE_MT_geometry_node_grease_pencil"
Geometry Nodes: Add "Grease Pencil" menu This adds a new Grease Pencil menu and moves the existing Grease Pencil related nodes into it. Pull Request: https://projects.blender.org/blender/blender/pulls/136498
2025-03-25 16:38:18 +01:00
bl_label = "Grease Pencil"
def draw(self, _context):
layout = self.layout
Cleanup: Avoid capitals in Geometry Nodes Grease Pencil add menu The capitals were only used for API compatibility when the add menu was first added, they're not needed for new menus. Better to avoid since they're non-standard for menu names.
2025-04-08 09:51:28 -04:00
layout.menu("NODE_MT_geometry_node_grease_pencil_read")
layout.menu("NODE_MT_geometry_node_grease_pencil_write")
Geometry Nodes: Add "Grease Pencil" menu This adds a new Grease Pencil menu and moves the existing Grease Pencil related nodes into it. Pull Request: https://projects.blender.org/blender/blender/pulls/136498
2025-03-25 16:38:18 +01:00
layout.separator()
Cleanup: Avoid capitals in Geometry Nodes Grease Pencil add menu The capitals were only used for API compatibility when the add menu was first added, they're not needed for new menus. Better to avoid since they're non-standard for menu names.
2025-04-08 09:51:28 -04:00
layout.menu("NODE_MT_geometry_node_grease_pencil_operations")
Geometry Nodes: Add "Grease Pencil" menu This adds a new Grease Pencil menu and moves the existing Grease Pencil related nodes into it. Pull Request: https://projects.blender.org/blender/blender/pulls/136498
2025-03-25 16:38:18 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_GEOMETRY(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_GEOMETRY"
bl_label = "Geometry"
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
def draw(self, _context):
layout = self.layout
layout.menu("NODE_MT_geometry_node_GEO_GEOMETRY_READ")
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
layout.menu("NODE_MT_geometry_node_GEO_GEOMETRY_SAMPLE")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_GEOMETRY_WRITE")
User Inteface: Missing separator in Geometry Nodes > Add Node > Geometry menu This separator was missing in the original change in the menus (d4e638baac4).
2023-01-16 12:23:50 +01:00
layout.separator()
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_GEOMETRY_OPERATIONS")
layout.separator()
node_add_menu.add_node_type(layout, "GeometryNodeGeometryToInstance")
UI: support adding a search weight to menu entries for menu-search The goal is to support better search experience in the cases where we want to explicitly influence the ordering instead of relying only on general heuristics. We used to support this already at some point I think, but not anymore since we started using menu-search. The implementation is fairly straight forward. It mainly just forwards the search weight from the menu definition to the search code through various required steps. The main annoying thing is that changing the signature of e.g. `uiItemFullO_ptr` is fairly involved. Even using default parameters for these functions is a bit annoying and becomes fairly unreadable and error-prone on the call-site. For now, I worked around this by storing the search weight on the `uiLayout` and to copy it to the `uiBut` from there. That seems preferable until we have a better solution for adding parameters to all the `uiItem*` functions. Pull Request: https://projects.blender.org/blender/blender/pulls/120572
2024-04-16 12:18:45 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeJoinGeometry", search_weight=1.0)
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Cleanup: make format
2023-01-16 14:39:10 +01:00
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_GEOMETRY_READ(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_GEOMETRY_READ"
bl_label = "Read"
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
def draw(self, context):
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeInputID")
node_add_menu.add_node_type(layout, "GeometryNodeInputIndex")
Geometry Nodes: improve search weights of some nodes
2024-04-22 18:22:05 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeInputNamedAttribute", search_weight=1.0)
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInputNormal")
Geometry Nodes: improve search weights of some nodes
2024-04-22 18:22:05 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeInputPosition", search_weight=1.0)
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInputRadius")
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
if context.space_data.geometry_nodes_type == 'TOOL':
node_add_menu.add_node_type(layout, "GeometryNodeToolSelection")
Geometry Nodes: Add Active Element tool node This pull request adds an "Active Element" node that exposes the active vertex, edge, or face index to the geometry node tool context. The presence of an active element is available as a boolean. This node enables the creation of "active-to-selected" style operators. Co-authored-by: Hans Goudey <hans@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/121333
2024-05-20 21:01:30 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeToolActiveElement")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Geometry/Read")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_GEOMETRY_WRITE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_GEOMETRY_WRITE"
bl_label = "Write"
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
def draw(self, context):
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout = self.layout
Geometry Nodes: allow naming geometry sets This adds a new `name` member to the `GeometrySet` class. This name can be set with the new `Set Geometry Name` node. Currently, the name is only used in the spreadsheet when displaying instances. The main purpose of this name is to help debugging in instance trees. However, in the future it may also be used when exporting instance trees or when creating separate objects from them. Note, the name is not expected to be unique, it is fully in user control. Naming geometries is necessary to make the spreadsheet more useful for instances, because currently the user has no information for which geometry is used by each instance. We also want to use this name to improve the integration with grease pencil where sometimes layers become instances with the same name. Pull Request: https://projects.blender.org/blender/blender/pulls/114910
2024-07-09 17:03:54 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSetGeometryName")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeSetID")
Geometry Nodes: improve search weights of some nodes
2024-04-22 18:22:05 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSetPosition", search_weight=1.0)
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
if context.space_data.geometry_nodes_type == 'TOOL':
node_add_menu.add_node_type(layout, "GeometryNodeToolSetSelection")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Geometry/Write")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
Cleanup: make format
2023-01-16 14:39:10 +01:00
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_GEOMETRY_OPERATIONS(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_GEOMETRY_OPERATIONS"
bl_label = "Operations"
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
def draw(self, _context):
layout = self.layout
Geometry Nodes: new Bake node This adds a new `Bake` node which allows saving and loading intermediate geometries. Typical use cases we want address with this currently are: * Bake some data for use with a render engine. * Bake parts of the node tree explicitly for better performance. For now, the format that is written to disk is not considered to be an import/export format. It's not guaranteed that data written with one Blender version can be read by another Blender version. For that it's better to use proper interchange formats. Better support for those will be added eventually as well. We also plan an `Import Bake` node that allows reading the blender-specific baked data independent of the Bake node and at different frames. The baking works very similar to the baking in the simulation zone (UI and implementation wise). Major differences are: * The Bake node has a `Bake Still` and `Bake Animation` mode. * The Bake node doesn't do automatic caching. Implementation details: * Refactored how we create the Python operators for moving socket items so that it also makes sense for non-zones. * The `ModifierCache` stores an independent map of `SimulationNodeCache` and `BakeNodeCache`, but both share a common data structure for the actually baked data. * For baking, the `Bake` node is added as a side-effect-node in the modifier. This will make sure that the node is baked even if it's currently not connected to the output. * Had to add a new `DEG_id_tag_update_for_side_effect_request` function that is used during baking. It's necessary because I want to evaluate the object again even though none of its inputs changed. The reevaluation is necessary to create the baked data. Using `DEG_id_tag_update` technically works as well, but has the problem that it also uses the `DEG_UPDATE_SOURCE_USER_EDIT` flag which (rightly) invalidates simulation caches which shouldn't happen here. * Slightly refactored the timeline drawing so that it can also show the baked ranges of Bake nodes. It does not show anything for baked nodes with a in Still mode though. * The bake operator is refactored to bake a list of `NodeBakeRequest` which makes the code easier to follow compared to the previous nested `ObjectBakeData > ModifierBakeData > NodeBakeData` data structure. * The bake operators are disabled when the .blend file is not yet saved. This is technically only necessary when the bake path depends on the .blend file path but seems ok to force the user anyway (otherwise the bake path may be lost as well if it's set explicitly). * The same operators are used to bake and delete single bakes in `Bake` nodes and `Simulation Zones`. On top of that, there are separate operators of baking and deleting all simulation bakes (those ignore bake nodes). * The `Bake` node remembers which inputs have been fields and thus may be baked as attributes. For that it uses an `Is Attribute` flag on the socket item. This is needed because the baked data may still contain attribute data, even if the inputs to the bake node are disconnected. * Similar to simulation zones, the behavior of `Bake` nodes is passed into the geometry nodes evaluation from the outside (from the modifier only currently). This is done by providing the new `GeoNodesBakeParams` in `GeoNodesCallData` when executing geometry nodes. Next Steps (mostly because they also involve simulations): * Visualize nodes that have not been evaluated in the last evaluation. * Fix issue with seemingly loosing baked data after undo. * Improve error handling when baked data is not found. * Show bake node in link drag search. * Higher level tools for managing bakes. Pull Request: https://projects.blender.org/blender/blender/pulls/115466
2023-12-18 13:01:06 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeBake")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeBoundBox")
node_add_menu.add_node_type(layout, "GeometryNodeConvexHull")
node_add_menu.add_node_type(layout, "GeometryNodeDeleteGeometry")
node_add_menu.add_node_type(layout, "GeometryNodeDuplicateElements")
node_add_menu.add_node_type(layout, "GeometryNodeMergeByDistance")
Geometry Nodes: Sort Elements node Implements the design in #109983 Pull Request: https://projects.blender.org/blender/blender/pulls/114194
2024-01-12 14:30:34 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeSortElements")
UI: support adding a search weight to menu entries for menu-search The goal is to support better search experience in the cases where we want to explicitly influence the ordering instead of relying only on general heuristics. We used to support this already at some point I think, but not anymore since we started using menu-search. The implementation is fairly straight forward. It mainly just forwards the search weight from the menu definition to the search code through various required steps. The main annoying thing is that changing the signature of e.g. `uiItemFullO_ptr` is fairly involved. Even using default parameters for these functions is a bit annoying and becomes fairly unreadable and error-prone on the call-site. For now, I worked around this by storing the search weight on the `uiLayout` and to copy it to the `uiBut` from there. That seems preferable until we have a better solution for adding parameters to all the `uiItem*` functions. Pull Request: https://projects.blender.org/blender/blender/pulls/120572
2024-04-16 12:18:45 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeTransform", search_weight=1.0)
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.separator()
node_add_menu.add_node_type(layout, "GeometryNodeSeparateComponents")
node_add_menu.add_node_type(layout, "GeometryNodeSeparateGeometry")
Geometry Nodes: new Split to Instances node This node allows splitting up a geometry into groups. A group is defined as all elements with the same group id. The output contains an instance per group. The `Group ID` output can be used for further deterministic processing. The node supports meshes, curves, point clouds and instances. It only works on the top-level geometry, so it does not go into nested instances because it also generates new instances. Co-authored-by: Hans Goudey <hans@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/113083
2023-10-18 10:26:23 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSplitToInstances")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Geometry/Operations")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
Cleanup: make format
2023-01-16 14:39:10 +01:00
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_GEOMETRY_SAMPLE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_GEOMETRY_SAMPLE"
bl_label = "Sample"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeProximity")
Geometry Nodes: new Index of Nearest node The node outputs the index of the closest element to itself. See #102387 for the original design. This is different from the Sample Nearest node in two important ways: * It does not have a geometry input, instead the geometry is taken from the field evaluation context. * The node can exclude the "current" element from the search. * The group id input can be used to build subsets of elements that only consider each other as neighbors and ignore elements with other ids. Pull Request: https://projects.blender.org/blender/blender/pulls/104619
2023-04-22 13:11:51 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeIndexOfNearest")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeRaycast")
node_add_menu.add_node_type(layout, "GeometryNodeSampleIndex")
node_add_menu.add_node_type(layout, "GeometryNodeSampleNearest")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Geometry/Sample")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_INPUT(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_INPUT"
bl_label = "Input"
Geometry Nodes: Add STL Import Node This commit adds an initial STL import node, the first of the nodes from the current Google Summer of Code Project [0]. The importer is refactored to output a mesh pointer, and a node is added to wrap around the importer. The node supports error messages from the importer. A new experimental option is added to hide the nodes by default until they're ready to be exposed generally. 0: https://devtalk.blender.org/t/gsoc-2024-geometry-nodes-file-import-nodes/34482) Pull Request: https://projects.blender.org/blender/blender/pulls/122418
2024-06-10 20:47:37 +02:00
def draw(self, context):
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout = self.layout
layout.menu("NODE_MT_geometry_node_GEO_INPUT_CONSTANT")
Geometry Nodes: support attaching gizmos to input values This adds support for attaching gizmos for input values. The goal is to make it easier for users to set input values intuitively in the 3D viewport. We went through multiple different possible designs until we settled on the one implemented here. We picked it for it's flexibility and ease of use when using geometry node assets. The core principle in the design is that **gizmos are attached to existing input values instead of being the input value themselves**. This actually fits the existing concept of gizmos in Blender well, but may be a bit unintutitive in a node setup at first. The attachment is done using links in the node editor. The most basic usage of the node is to link a Value node to the new Linear Gizmo node. This attaches the gizmo to the input value and allows you to change it from the 3D view. The attachment is indicated by the gizmo icon in the sockets which are controlled by a gizmo as well as the back-link (notice the double link) when the gizmo is active. The core principle makes it straight forward to control the same node setup from the 3D view with gizmos, or by manually changing input values, or by driving the input values procedurally. If the input value is controlled indirectly by other inputs, it's often possible to **automatically propagate** the gizmo to the actual input. Backpropagation does not work for all nodes, although more nodes can be supported over time. This patch adds the first three gizmo nodes which cover common use cases: * **Linear Gizmo**: Creates a gizmo that controls a float or integer value using a linear movement of e.g. an arrow in the 3D viewport. * **Dial Gizmo**: Creates a circular gizmo in the 3D viewport that can be rotated to change the attached angle input. * **Transform Gizmo**: Creates a simple gizmo for location, rotation and scale. In the future, more built-in gizmos and potentially the ability for custom gizmos could be added. All gizmo nodes have a **Transform** geometry output. Using it is optional but it is recommended when the gizmo is used to control inputs that affect a geometry. When it is used, Blender will automatically transform the gizmos together with the geometry that they control. To achieve this, the output should be merged with the generated geometry using the *Join Geometry* node. The data contained in *Transform* output is not visible geometry, but just internal information that helps Blender to give a better user experience when using gizmos. The gizmo nodes have a multi-input socket. This allows **controlling multiple values** with the same gizmo. Only a small set of **gizmo shapes** is supported initially. It might be extended in the future but one goal is to give the gizmos used by different node group assets a familiar look and feel. A similar constraint exists for **colors**. Currently, one can choose from a fixed set of colors which can be modified in the theme settings. The set of **visible gizmos** is determined by a multiple factors because it's not really feasible to show all possible gizmos at all times. To see any of the geometry nodes gizmos, the "Active Modifier" option has to be enabled in the "Viewport Gizmos" popover. Then all gizmos are drawn for which at least one of the following is true: * The gizmo controls an input of the active modifier of the active object. * The gizmo controls a value in a selected node in an open node editor. * The gizmo controls a pinned value in an open node editor. Pinning works by clicking the gizmo icon next to the value. Pull Request: https://projects.blender.org/blender/blender/pulls/112677
2024-07-10 16:18:47 +02:00
if context.space_data.geometry_nodes_type != 'TOOL':
layout.menu("NODE_MT_geometry_node_GEO_INPUT_GIZMO")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_INPUT_GROUP")
Geometry Nodes: Move import nodes out of experimental The import nodes are considered complete enough to expose without the experimental option. This commit removes the option so they will be exposed in 4.5. There are still some possible future improvements, including automatic caching, possibly exposing more input sockets, and possibly including imported paths in the "Internal Dependencies" panel. Those are considered non blocking though. Pull Request: https://projects.blender.org/blender/blender/pulls/135957
2025-03-17 13:54:48 +01:00
layout.menu("NODE_MT_category_import")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_INPUT_SCENE")
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
class NODE_MT_geometry_node_GEO_INPUT_CONSTANT(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_INPUT_CONSTANT"
bl_label = "Constant"
I18n: disambiguate messages - "Lines" in the sense of number of lines - "Number" can mean "amount, count" or "index, offset" - "Second" can be an ordinal number or a unit - "Root": add the brush curve to the "square root falloff" sense - "Strip" can be a sequence or a type of hair rendering - "Constant" in the sense of a value, for the Geometry Nodes add submenu (#105447). Additionally, extract: - "Press a key" from the Keymap preferences. - "MaskLayer", upon new mask layer creation Ref #43295, #105447
2023-03-03 14:44:21 +01:00
bl_translation_context = i18n_contexts.id_nodetree
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "FunctionNodeInputBool")
Geometry Nodes: Add "Collection" and "Object" input nodes Pull Request: https://projects.blender.org/blender/blender/pulls/131075
2024-12-04 15:01:44 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInputCollection")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "FunctionNodeInputColor")
Geometry Nodes: Image Input Node Add a simple node to choose an image data-block. Ref T102854 Differential Revision: https://developer.blender.org/D16644
2022-12-09 15:50:00 -06:00
node_add_menu.add_node_type(layout, "GeometryNodeInputImage")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "FunctionNodeInputInt")
node_add_menu.add_node_type(layout, "GeometryNodeInputMaterial")
Geometry Nodes: Add "Collection" and "Object" input nodes Pull Request: https://projects.blender.org/blender/blender/pulls/131075
2024-12-04 15:01:44 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInputObject")
Geometry Nodes: new Input Rotation node This adds a new node input node for a constant rotation. Similar nodes exist for vector, integer, boolean, etc. already. Pull Request: https://projects.blender.org/blender/blender/pulls/120345
2024-05-06 19:04:30 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeInputRotation")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "FunctionNodeInputString")
node_add_menu.add_node_type(layout, "ShaderNodeValue")
node_add_menu.add_node_type(layout, "FunctionNodeInputVector")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Input/Constant")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_INPUT_GROUP(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_INPUT_GROUP"
bl_label = "Group"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "NodeGroupInput")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Input/Group")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_INPUT_SCENE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_INPUT_SCENE"
bl_label = "Scene"
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
def draw(self, context):
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout = self.layout
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
if context.space_data.geometry_nodes_type == 'TOOL':
node_add_menu.add_node_type(layout, "GeometryNodeTool3DCursor")
Geometry Nodes: Add Active Camera input node This adds a new "Active Camera" input geometry node, per #105761. The node outputs the the scene's current active camera. It is available from Input > Scene > Active Camera in the geometry nodes Add menu. Typical usage would be to connect this node to an Object Info node to obtain its transform. This works as expected when the camera's transform is animated, and also when there are markers on the timeline that change the active camera. In order to support the aforementioned changes in the active camera, this implementation adds depsgraph relations for all cameras referenced by timeline markers. This eliminates the complexity of updating the depsgraph whenever the scene switches to a different active camera, but of course it comes at the cost of including more objects than strictly necessary in the depsgraph for scenes that switch cameras. Dynamically updating the depsgraph upon camera changes could be a future improvement if there proves to be sufficient need for it. Pull Request: https://projects.blender.org/blender/blender/pulls/113431
2023-12-12 19:11:06 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInputActiveCamera")
Geometry Nodes: new Camera Info Node This adds a new Camera Info node to Geometry Nodes. It provides information about the passed in camera like its projection matrix and focus distance. This can be used for camera culling which was must more complex before. It also allows building other view-dependent effects. Pull Request: https://projects.blender.org/blender/blender/pulls/135311
2025-03-28 22:54:13 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeCameraInfo")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeCollectionInfo")
node_add_menu.add_node_type(layout, "GeometryNodeImageInfo")
node_add_menu.add_node_type(layout, "GeometryNodeIsViewport")
Node Tools: Add mouse position node, wait for cursor option Add a "Mouse Position" node that outputs the location of the mouse cursor in region space and the overall size of the region, both in pixel units. Both outputs are integers to help reflect their pixel units. If there the mouse position is ever accessible in sub-pixels, they can easily be changed to floats. Also add a "Wait for Cursor" option similar to the one for some built-in operators that delay's the operator's execution until there is a mouse click in the viewport. That way the operator can be called from menus even though it is interactive. This option is placed in the node editor header. When there are more options, it will be part of an "Options" popover panel similar to the existing "Modes" and "types" popovers. Combined with the viewport transform node, and other nodes like Raycast, these features can allow making tools that create geometry where you click in the scene. Pull Request: https://projects.blender.org/blender/blender/pulls/121043
2024-04-26 20:14:25 +02:00
if context.space_data.geometry_nodes_type == 'TOOL':
node_add_menu.add_node_type(layout, "GeometryNodeToolMousePosition")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeObjectInfo")
Nodes: support searching for frame/seconds to find Scene Time node Previously, one had to search for "Time" to get the Scene Time node which provides access to the current frame and second. Intuitively I often start searching for "frame" or "seconds" instead and only later remember what I actually have to search for. This patch improves the UX by allowing to create a Scene Time node by searching for "frame" or "seconds" directly. This works in Geometry Nodes and the compositor. Pull Request: https://projects.blender.org/blender/blender/pulls/138927
2025-05-15 20:56:33 +02:00
node_add_menu.add_node_type_with_subnames(context, layout, "GeometryNodeInputSceneTime", ["Frame", "Seconds"])
Geometry Nodes: Sort Add menu entries * In Input → Scene, move: * `Scene Time` above `Self Object` * In Geometry, move: * `Geometry to Instance` above `Join Geometry` * In Curve → Topology, move: * `Curve of Point` above `Offset Pint in Curve` * In Mesh → Read, move: * `Face Group Boundaries` above `Face Neighbors` * `Edges to Face Groups` above `Edge Vertices`
2023-08-24 16:09:58 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSelfObject")
Geometry Nodes: Add Viewport Transform node Add a node that outputs the transform of the viewport relative to the self object's transform. This node can be used to build effects like billboarding or aligning geometry to the current view. In combination with the mouse position node in the future it will allow tools like generating geometry at the mouse click position. There are two output matrices. The first is the projection matrix that takes positions in camera space and applies the final perspective projection. The other is the "view" matrix which contains the location and rotation of the camera. These are separate because though their combination is useful, it isn't used like a typical rotation/transform matrix. Pull Request: https://projects.blender.org/blender/blender/pulls/118680
2024-04-26 19:47:19 +02:00
if context.space_data.geometry_nodes_type == 'TOOL':
node_add_menu.add_node_type(layout, "GeometryNodeViewportTransform")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Input/Scene")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Geometry Nodes: support attaching gizmos to input values This adds support for attaching gizmos for input values. The goal is to make it easier for users to set input values intuitively in the 3D viewport. We went through multiple different possible designs until we settled on the one implemented here. We picked it for it's flexibility and ease of use when using geometry node assets. The core principle in the design is that **gizmos are attached to existing input values instead of being the input value themselves**. This actually fits the existing concept of gizmos in Blender well, but may be a bit unintutitive in a node setup at first. The attachment is done using links in the node editor. The most basic usage of the node is to link a Value node to the new Linear Gizmo node. This attaches the gizmo to the input value and allows you to change it from the 3D view. The attachment is indicated by the gizmo icon in the sockets which are controlled by a gizmo as well as the back-link (notice the double link) when the gizmo is active. The core principle makes it straight forward to control the same node setup from the 3D view with gizmos, or by manually changing input values, or by driving the input values procedurally. If the input value is controlled indirectly by other inputs, it's often possible to **automatically propagate** the gizmo to the actual input. Backpropagation does not work for all nodes, although more nodes can be supported over time. This patch adds the first three gizmo nodes which cover common use cases: * **Linear Gizmo**: Creates a gizmo that controls a float or integer value using a linear movement of e.g. an arrow in the 3D viewport. * **Dial Gizmo**: Creates a circular gizmo in the 3D viewport that can be rotated to change the attached angle input. * **Transform Gizmo**: Creates a simple gizmo for location, rotation and scale. In the future, more built-in gizmos and potentially the ability for custom gizmos could be added. All gizmo nodes have a **Transform** geometry output. Using it is optional but it is recommended when the gizmo is used to control inputs that affect a geometry. When it is used, Blender will automatically transform the gizmos together with the geometry that they control. To achieve this, the output should be merged with the generated geometry using the *Join Geometry* node. The data contained in *Transform* output is not visible geometry, but just internal information that helps Blender to give a better user experience when using gizmos. The gizmo nodes have a multi-input socket. This allows **controlling multiple values** with the same gizmo. Only a small set of **gizmo shapes** is supported initially. It might be extended in the future but one goal is to give the gizmos used by different node group assets a familiar look and feel. A similar constraint exists for **colors**. Currently, one can choose from a fixed set of colors which can be modified in the theme settings. The set of **visible gizmos** is determined by a multiple factors because it's not really feasible to show all possible gizmos at all times. To see any of the geometry nodes gizmos, the "Active Modifier" option has to be enabled in the "Viewport Gizmos" popover. Then all gizmos are drawn for which at least one of the following is true: * The gizmo controls an input of the active modifier of the active object. * The gizmo controls a value in a selected node in an open node editor. * The gizmo controls a pinned value in an open node editor. Pinning works by clicking the gizmo icon next to the value. Pull Request: https://projects.blender.org/blender/blender/pulls/112677
2024-07-10 16:18:47 +02:00
class NODE_MT_geometry_node_GEO_INPUT_GIZMO(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_INPUT_GIZMO"
bl_label = "Gizmo"
def draw(self, context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeGizmoDial")
node_add_menu.add_node_type(layout, "GeometryNodeGizmoLinear")
node_add_menu.add_node_type(layout, "GeometryNodeGizmoTransform")
Fix: Nodes: Missing builtin categories for handling asset catalogs The current behavior for the Node Editor's Add menu is to list the user's asset catalogs at the root level of the menu. However, an exception is made if the catalog has the same name as a builtin menu. In such case, the asset catalog is appended to that builtin menu, instead of being drawn at the root level. How this is currently implemented right now is to have a hard-coded set of builtin menus in `add_menu_assets.cc`. Certain menus are missing from this set, particularly newer ones, which may be an oversight during the creation of these menus. This patch adds those menus to that list, which are as follows: - Input/Gizmo - Input/Import - Grease Pencil (and all its submenus) - Texture (in Compositor Nodes) Pull Request: https://projects.blender.org/blender/blender/pulls/138870
2025-05-14 16:12:29 +02:00
node_add_menu.draw_assets_for_catalog(layout, "Input/Gizmo")
Geometry Nodes: support attaching gizmos to input values This adds support for attaching gizmos for input values. The goal is to make it easier for users to set input values intuitively in the 3D viewport. We went through multiple different possible designs until we settled on the one implemented here. We picked it for it's flexibility and ease of use when using geometry node assets. The core principle in the design is that **gizmos are attached to existing input values instead of being the input value themselves**. This actually fits the existing concept of gizmos in Blender well, but may be a bit unintutitive in a node setup at first. The attachment is done using links in the node editor. The most basic usage of the node is to link a Value node to the new Linear Gizmo node. This attaches the gizmo to the input value and allows you to change it from the 3D view. The attachment is indicated by the gizmo icon in the sockets which are controlled by a gizmo as well as the back-link (notice the double link) when the gizmo is active. The core principle makes it straight forward to control the same node setup from the 3D view with gizmos, or by manually changing input values, or by driving the input values procedurally. If the input value is controlled indirectly by other inputs, it's often possible to **automatically propagate** the gizmo to the actual input. Backpropagation does not work for all nodes, although more nodes can be supported over time. This patch adds the first three gizmo nodes which cover common use cases: * **Linear Gizmo**: Creates a gizmo that controls a float or integer value using a linear movement of e.g. an arrow in the 3D viewport. * **Dial Gizmo**: Creates a circular gizmo in the 3D viewport that can be rotated to change the attached angle input. * **Transform Gizmo**: Creates a simple gizmo for location, rotation and scale. In the future, more built-in gizmos and potentially the ability for custom gizmos could be added. All gizmo nodes have a **Transform** geometry output. Using it is optional but it is recommended when the gizmo is used to control inputs that affect a geometry. When it is used, Blender will automatically transform the gizmos together with the geometry that they control. To achieve this, the output should be merged with the generated geometry using the *Join Geometry* node. The data contained in *Transform* output is not visible geometry, but just internal information that helps Blender to give a better user experience when using gizmos. The gizmo nodes have a multi-input socket. This allows **controlling multiple values** with the same gizmo. Only a small set of **gizmo shapes** is supported initially. It might be extended in the future but one goal is to give the gizmos used by different node group assets a familiar look and feel. A similar constraint exists for **colors**. Currently, one can choose from a fixed set of colors which can be modified in the theme settings. The set of **visible gizmos** is determined by a multiple factors because it's not really feasible to show all possible gizmos at all times. To see any of the geometry nodes gizmos, the "Active Modifier" option has to be enabled in the "Viewport Gizmos" popover. Then all gizmos are drawn for which at least one of the following is true: * The gizmo controls an input of the active modifier of the active object. * The gizmo controls a value in a selected node in an open node editor. * The gizmo controls a pinned value in an open node editor. Pinning works by clicking the gizmo icon next to the value. Pull Request: https://projects.blender.org/blender/blender/pulls/112677
2024-07-10 16:18:47 +02:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_INSTANCE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_INSTANCE"
bl_label = "Instances"
def draw(self, _context):
layout = self.layout
Geometry Nodes: improve search weights of some nodes
2024-04-22 18:22:05 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeInstanceOnPoints", search_weight=2.0)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeInstancesToPoints")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.separator()
Geometry Nodes: improve search weights of some nodes
2024-04-22 18:22:05 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeRealizeInstances", search_weight=1.0)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeRotateInstances")
node_add_menu.add_node_type(layout, "GeometryNodeScaleInstances")
node_add_menu.add_node_type(layout, "GeometryNodeTranslateInstances")
Geometry Nodes: new Set Instance Transform node This node allows replacing the transformation of every instance by providing a matrix. Before, this was only possible by using the Store Named Attribute node. It's more common in Blender to have specialized built-in nodes for built-in attributes (e.g. Set Position, and Set ID). Pull Request: https://projects.blender.org/blender/blender/pulls/121473
2024-05-28 16:34:37 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSetInstanceTransform")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout.separator()
Geometry Nodes: new Instance Bounds Node This adds a new Instance Bounds nodes which provides an easy and efficient way to get the bounding box of each instance. Nested instances or not taken into account to compute the bounding box. That would result in a major performance degredation because one would have to basically realize all instances to do that. Also see #135933 for some examples. Pull Request: https://projects.blender.org/blender/blender/pulls/135933
2025-04-17 13:34:26 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeInputInstanceBounds")
Geometry Nodes: new Instance Transform attribute input node New node to access `instance_transform` built-in attribute of instances. Pull Request: https://projects.blender.org/blender/blender/pulls/122477
2024-05-31 12:55:40 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeInstanceTransform")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeInputInstanceRotation")
node_add_menu.add_node_type(layout, "GeometryNodeInputInstanceScale")
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_MATERIAL(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_MATERIAL"
bl_label = "Material"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeReplaceMaterial")
layout.separator()
node_add_menu.add_node_type(layout, "GeometryNodeInputMaterialIndex")
node_add_menu.add_node_type(layout, "GeometryNodeMaterialSelection")
layout.separator()
Geometry Nodes: improve search weights of some nodes
2024-04-22 18:22:05 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSetMaterial", search_weight=1.0)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeSetMaterialIndex")
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_GEO_MESH(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_MESH"
bl_label = "Mesh"
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
def draw(self, _context):
layout = self.layout
layout.menu("NODE_MT_geometry_node_GEO_MESH_READ")
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
layout.menu("NODE_MT_geometry_node_GEO_MESH_SAMPLE")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_MESH_WRITE")
layout.separator()
layout.menu("NODE_MT_geometry_node_GEO_MESH_OPERATIONS")
layout.menu("NODE_MT_category_PRIMITIVES_MESH")
layout.menu("NODE_MT_geometry_node_mesh_topology")
layout.menu("NODE_MT_category_GEO_UV")
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
class NODE_MT_geometry_node_GEO_MESH_READ(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_MESH_READ"
bl_label = "Read"
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
def draw(self, context):
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeInputMeshEdgeAngle")
node_add_menu.add_node_type(layout, "GeometryNodeInputMeshEdgeNeighbors")
Geometry Nodes: Sort Add menu entries * In Input → Scene, move: * `Scene Time` above `Self Object` * In Geometry, move: * `Geometry to Instance` above `Join Geometry` * In Curve → Topology, move: * `Curve of Point` above `Offset Pint in Curve` * In Mesh → Read, move: * `Face Group Boundaries` above `Face Neighbors` * `Edges to Face Groups` above `Edge Vertices`
2023-08-24 16:09:58 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeInputMeshEdgeVertices")
Fix: wrong sorting in Add menu in recent commit `Edges to Face Groups` comes after `Edge Vertices`, didn't notice it was plural. Thanks Dalai for pointing it out.
2023-08-24 16:15:43 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeEdgesToFaceGroups")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInputMeshFaceArea")
node_add_menu.add_node_type(layout, "GeometryNodeMeshFaceSetBoundaries")
Geometry Nodes: Sort Add menu entries * In Input → Scene, move: * `Scene Time` above `Self Object` * In Geometry, move: * `Geometry to Instance` above `Join Geometry` * In Curve → Topology, move: * `Curve of Point` above `Offset Pint in Curve` * In Mesh → Read, move: * `Face Group Boundaries` above `Face Neighbors` * `Edges to Face Groups` above `Edge Vertices`
2023-08-24 16:09:58 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeInputMeshFaceNeighbors")
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
if context.space_data.geometry_nodes_type == 'TOOL':
node_add_menu.add_node_type(layout, "GeometryNodeToolFaceSet")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInputMeshFaceIsPlanar")
node_add_menu.add_node_type(layout, "GeometryNodeInputShadeSmooth")
Geometry Nodes: Expose sharp edge status with builtin nodes Change the existing "Is Shade Smooth" node to be named "Is Face Smooth" and add a new "Is Edge Smooth" node. Also give the "Set Shade Smooth" node the ability to set face or edge smoothness. The fact that the nodes process "smooth" data reversed from the builtin "sharp" attributes can be reversed with versioning in a separate commit. While it's tempting to abstract the sharpness status into a single node, face and edge smoothness are accessed separately in edit mode, and the subtlety of interacting with data on different domains would make that confusing. Instead, a separate "Is Shade Smooth" node group asset will give all the sharp elements taking into account both builtin attributes. The fact that sharpness is stored separately on two domains makes the best design for simple operations non-obvious. For example, you should be able to remove all sharpness or make everything flat with a single node. The behavior depends on whether the two attributes exist and the combination of values between the domains. --- ![image](/attachments/c3f053c4-2b0f-44ac-9227-62071065fe56) ![image](/attachments/fd489fb3-314b-42ff-a5a9-e79578cbdfe7) Pull Request: https://projects.blender.org/blender/blender/pulls/112029
2023-09-06 17:12:27 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeInputEdgeSmooth")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeInputMeshIsland")
node_add_menu.add_node_type(layout, "GeometryNodeInputShortestEdgePaths")
node_add_menu.add_node_type(layout, "GeometryNodeInputMeshVertexNeighbors")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Mesh/Read")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
class NODE_MT_geometry_node_GEO_MESH_SAMPLE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_MESH_SAMPLE"
bl_label = "Sample"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeSampleNearestSurface")
node_add_menu.add_node_type(layout, "GeometryNodeSampleUVSurface")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Mesh/Sample")
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_MESH_WRITE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_MESH_WRITE"
bl_label = "Write"
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
def draw(self, context):
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout = self.layout
Geometry Nodes: Move tool-specific nodes to proper menus Instead of putting all the tool specific nodes (inputs, operations, etc) in a single menu, use the existing categories. This is similar to how the shader editor shows nodes depending on which render engine is enabled. It's also more scalable for when more tool-specific nodes are added. --- I discussed this with Pablo on Tuesday-- it came up when we talked about the organization of the compositor add menu. Pull Request: https://projects.blender.org/blender/blender/pulls/111449
2023-08-24 13:34:15 +02:00
if context.space_data.geometry_nodes_type == 'TOOL':
node_add_menu.add_node_type(layout, "GeometryNodeToolSetFaceSet")
Mesh: Add "free" custom normals Add a "dumb vector" storage option for custom normals, with the "custom_normal" attribute. Adjust the mesh normals caching to provide this attribute if it's available, and add a geometry node to store custom normals. ## Free Normals They're called "free" in the sense that they're just direction vectors in the object's local space, rather than the existing "smooth corner fan space" storage. They're also "free" in that they make further normals calculation very inexpensive, since we just use the custom normals instead. That's a big improvement from the existing custom normals storage, which usually significantly decreases viewport performance. For example, in a simple test file just storing the vertex normals on a UV sphere, using free normals gives 25 times better playback performance and 10% lower memory usage. Free normals are adjusted when applying a transformation to the entire mesh or when realizing instances, but in general they're not updated for vertex deformations. ## Set Mesh Normal Node The new geometry node allows storing free custom normals as well as the existing corner fan space normals. When free normals are chosen, free normals can be stored on vertices, faces, or face corners. Using the face corner domain is necessary to bake existing mixed sharp and smooth edges into the custom normal vectors. The node also has a mode for storing edge and mesh sharpness, meant as a "soft" replacement to the "Set Shade Smooth" node that's a bit more convenient. ## Normal Input Node The normal node outputs free custom normals mixed to whatever domain is requested. A "true normal" output that ignores custom normals and sharpness is added as well. Across Blender, custom normals are generally accessed via face and vertex normals, when "true normals" are not requested explicitly. In many cases that means they are mixed from the face corner domain. ## Future Work 1. There are many places where propagation of free normals could be improved. They should probably be normalized after mixing, and it may be useful to not just use 0 vectors for new elements. To keep the scope of this change smaller, that sort of thing generally isn't handled here. Searching `CD_NORMAL` gives a hint of where better propagation could be useful. 2. Free normals are displayed properly in edit mode, but the existing custom normal editing operators don't work with free normals yet. This will hopefully be fairly straightforward since custom normals are usually converted to `float3` for editing anyway. Edit mode changes aren't included here because they're unnecessary for the procedural custom normals use cases. 3. Most importers can probably switch to using free normals instead, or at least provide an option for it. That will give a significant import performance improvement, and an improvement of Blender's FPS for imported scenes too. Pull Request: https://projects.blender.org/blender/blender/pulls/132583
2025-04-04 19:16:51 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSetMeshNormal")
Fix: Correct order of nodes in the Mesh > Write menu The ordering of geometry nodes in the menus is intended to be alphabetic, but the new "Set Face Set" node was listed _after_ the "Set Shade Smooth" node in the Mesh > Write menu. This fixes the order. Pull Request: https://projects.blender.org/blender/blender/pulls/114475
2023-11-04 11:02:59 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeSetShadeSmooth")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Mesh/Write")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_geometry_node_GEO_MESH_OPERATIONS(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_MESH_OPERATIONS"
bl_label = "Operations"
Cleanup: remove unused argument signified from used arguments in Python Also simplify import for `_bpy._utils_previews`.
2023-03-23 15:31:14 +11:00
def draw(self, context):
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeDualMesh")
node_add_menu.add_node_type(layout, "GeometryNodeEdgePathsToCurves")
node_add_menu.add_node_type(layout, "GeometryNodeEdgePathsToSelection")
node_add_menu.add_node_type(layout, "GeometryNodeExtrudeMesh")
node_add_menu.add_node_type(layout, "GeometryNodeFlipFaces")
node_add_menu.add_node_type(layout, "GeometryNodeMeshBoolean")
node_add_menu.add_node_type(layout, "GeometryNodeMeshToCurve")
Geometry Nodes: Add volume grid creation nodes Add three nodes to the currently experimental volume grid nodes: - **Mesh to Density Grid** - **Mesh to SDF Grid** - **Points to SDF Grid** These nodes are just wrappers over basic OpenVDB utilities. The difference from existing volume nodes is that they output a grid directly instead of a geometry set. See the design here: https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 Pull Request: https://projects.blender.org/blender/blender/pulls/118761
2024-02-28 22:15:10 +01:00
if context.preferences.experimental.use_new_volume_nodes:
node_add_menu.add_node_type(layout, "GeometryNodeMeshToDensityGrid")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeMeshToPoints")
Geometry Nodes: Add volume grid creation nodes Add three nodes to the currently experimental volume grid nodes: - **Mesh to Density Grid** - **Mesh to SDF Grid** - **Points to SDF Grid** These nodes are just wrappers over basic OpenVDB utilities. The difference from existing volume nodes is that they output a grid directly instead of a geometry set. See the design here: https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 Pull Request: https://projects.blender.org/blender/blender/pulls/118761
2024-02-28 22:15:10 +01:00
if context.preferences.experimental.use_new_volume_nodes:
node_add_menu.add_node_type(layout, "GeometryNodeMeshToSDFGrid")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeMeshToVolume")
node_add_menu.add_node_type(layout, "GeometryNodeScaleElements")
node_add_menu.add_node_type(layout, "GeometryNodeSplitEdges")
node_add_menu.add_node_type(layout, "GeometryNodeSubdivideMesh")
node_add_menu.add_node_type(layout, "GeometryNodeSubdivisionSurface")
node_add_menu.add_node_type(layout, "GeometryNodeTriangulate")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Mesh/Operations")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_PRIMITIVES_MESH(Menu):
bl_idname = "NODE_MT_category_PRIMITIVES_MESH"
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
bl_label = "Primitives"
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeMeshCone")
node_add_menu.add_node_type(layout, "GeometryNodeMeshCube")
node_add_menu.add_node_type(layout, "GeometryNodeMeshCylinder")
node_add_menu.add_node_type(layout, "GeometryNodeMeshGrid")
node_add_menu.add_node_type(layout, "GeometryNodeMeshIcoSphere")
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeMeshCircle")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeMeshLine")
Fix T101610: UV Sphere missing from geometry nodes menu Caused by 837144b4577f161baf1625f8a5478c83a088ea0f
2022-10-05 10:53:12 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeMeshUVSphere")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Mesh/Primitives")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: Formatting in geometry nodes add menu Also remove the caps from the new menu idname. That was only done for backwards compatibility with old menu names at some point.
2024-06-10 15:38:43 -04:00
class NODE_MT_category_import(Menu):
bl_idname = "NODE_MT_category_import"
Geometry Nodes: Add STL Import Node This commit adds an initial STL import node, the first of the nodes from the current Google Summer of Code Project [0]. The importer is refactored to output a mesh pointer, and a node is added to wrap around the importer. The node supports error messages from the importer. A new experimental option is added to hide the nodes by default until they're ready to be exposed generally. 0: https://devtalk.blender.org/t/gsoc-2024-geometry-nodes-file-import-nodes/34482) Pull Request: https://projects.blender.org/blender/blender/pulls/122418
2024-06-10 20:47:37 +02:00
bl_label = "Import"
def draw(self, _context):
layout = self.layout
Geometry Nodes: Move import nodes out of experimental The import nodes are considered complete enough to expose without the experimental option. This commit removes the option so they will be exposed in 4.5. There are still some possible future improvements, including automatic caching, possibly exposing more input sockets, and possibly including imported paths in the "Internal Dependencies" panel. Those are considered non blocking though. Pull Request: https://projects.blender.org/blender/blender/pulls/135957
2025-03-17 13:54:48 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeImportCSV", label="CSV (.csv)")
node_add_menu.add_node_type(layout, "GeometryNodeImportOBJ", label="Wavefront (.obj)")
node_add_menu.add_node_type(layout, "GeometryNodeImportPLY", label="Stanford PLY (.ply)")
node_add_menu.add_node_type(layout, "GeometryNodeImportSTL", label="STL (.stl)")
node_add_menu.add_node_type(layout, "GeometryNodeImportText", label="Text (.txt)")
Geometry Nodes: add Import VDB node This adds an Import VDB node. It loads all the grids from a .vdb file and hence outputs a Volume geometry instead of an individual grid. The grids are cached through the existing volume grid file cache, so they are automatically deduplicated when volume grids are loaded from files in other ways. Pull Request: https://projects.blender.org/blender/blender/pulls/138380
2025-05-06 04:13:11 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeImportVDB", label="OpenVDB (.vdb)")
Geometry Nodes: Add STL Import Node This commit adds an initial STL import node, the first of the nodes from the current Google Summer of Code Project [0]. The importer is refactored to output a mesh pointer, and a node is added to wrap around the importer. The node supports error messages from the importer. A new experimental option is added to hide the nodes by default until they're ready to be exposed generally. 0: https://devtalk.blender.org/t/gsoc-2024-geometry-nodes-file-import-nodes/34482) Pull Request: https://projects.blender.org/blender/blender/pulls/122418
2024-06-10 20:47:37 +02:00
node_add_menu.draw_assets_for_catalog(layout, "Input/Import")
Cleanup: format
2022-09-27 16:36:27 +10:00
Cleanup: Formatting in geometry nodes add menu Also remove the caps from the new menu idname. That was only done for backwards compatibility with old menu names at some point.
2024-06-10 15:38:43 -04:00
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
class NODE_MT_geometry_node_mesh_topology(Menu):
bl_idname = "NODE_MT_geometry_node_mesh_topology"
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
bl_label = "Topology"
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
def draw(self, _context):
layout = self.layout
Geometry Nodes: Add Corners of Edge node Adds the "Corners of Edge" topology node to geometry nodes. Combining this node with the "Face of Corner" node allows getting informations about the faces connected to an edge. The behavior is slightly non-obvious-- the node only gives the corner neighbors that come *before* the current edge in directly neighboring faces. This allows the operation to be easily reversed and reduces redundancy between nodes. See the devtalk thread: https://devtalk.blender.org/t/29379 Pull Request: https://projects.blender.org/blender/blender/pulls/107968
2023-05-31 15:25:48 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeCornersOfEdge")
Cleanup: quiet various pylint warnings
2023-04-13 13:14:05 +10:00
node_add_menu.add_node_type(layout, "GeometryNodeCornersOfFace")
node_add_menu.add_node_type(layout, "GeometryNodeCornersOfVertex")
node_add_menu.add_node_type(layout, "GeometryNodeEdgesOfCorner")
node_add_menu.add_node_type(layout, "GeometryNodeEdgesOfVertex")
node_add_menu.add_node_type(layout, "GeometryNodeFaceOfCorner")
node_add_menu.add_node_type(layout, "GeometryNodeOffsetCornerInFace")
node_add_menu.add_node_type(layout, "GeometryNodeVertexOfCorner")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Mesh/Topology")
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_OUTPUT(Menu):
bl_idname = "NODE_MT_category_GEO_OUTPUT"
bl_label = "Output"
def draw(self, _context):
layout = self.layout
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "NodeGroupOutput")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeViewer")
Geometry Nodes: support custom warnings in node groups This implements the `Warning` node that allows node groups to communicate expectations about input values to the user. By default, the `Warning` node is only evaluated if the node group that contains it is evaluated in any way. This is better than always evaluating it, because that could trigger lots of unnecessary evaluation in parts of the potentially large node tree which should be ignored. In this basic mode, the output of the node should not be connected to anything and it must not be in a zone. For more fine-grained control for when the `Warning` node should be evaluated, one can use the boolean output which is just a pass-through of the `Show` input. If this output is used, the `Warning` node will only be evaluated if its output is used. A simple way to use it is to control a Switch node with it that e.g. "disables" a specific output when the inputs are invalid. In this case, the `Warning` node may also be in a zone. The node allows the user to choose between 3 severity levels: Error, Warning and Info. Those are the same levels that we use internally. Currently, the error and warning mode are pretty much the same, but that may change in the future. Pull Request: https://projects.blender.org/blender/blender/pulls/125544
2024-08-29 16:03:25 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeWarning")
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_POINT(Menu):
bl_idname = "NODE_MT_category_GEO_POINT"
bl_label = "Point"
Cleanup: remove unused argument signified from used arguments in Python Also simplify import for `_bpy._utils_previews`.
2023-03-23 15:31:14 +11:00
def draw(self, context):
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout = self.layout
Fix #119099: Distribute points in volume node missing in add menu Mistake in 860f3ed7943929a096ecceaaa68499a1a60869aa
2024-03-05 16:11:01 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeDistributePointsInVolume")
Geometry Nodes: Add volume grid conversion nodes Adds two nodes as "grid" equivalents to the existing volume nodes: - **Grid to Mesh** - **Distribute Points in Grid** The code for the latter is just duplicated for now. In a later step old node can be replaced by versioning with two new nodes. Pull Request: https://projects.blender.org/blender/blender/pulls/118830
2024-02-29 01:20:27 +01:00
if context.preferences.experimental.use_new_volume_nodes:
node_add_menu.add_node_type(layout, "GeometryNodeDistributePointsInGrid")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeDistributePointsOnFaces")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.separator()
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodePoints")
Geometry Nodes: Points to Curves node New node to converts groups of points to curves. Groups of points defined as `Curve Group ID` attribute. `Weight` in curve is used for sort points in each group. Points of result curves propagate attributes from original points. Implicit conversion of other geometry types is not supported currently. Pull Request: https://projects.blender.org/blender/blender/pulls/109610
2023-08-29 16:52:20 +02:00
node_add_menu.add_node_type(layout, "GeometryNodePointsToCurves")
Geometry Nodes: Add volume grid creation nodes Add three nodes to the currently experimental volume grid nodes: - **Mesh to Density Grid** - **Mesh to SDF Grid** - **Points to SDF Grid** These nodes are just wrappers over basic OpenVDB utilities. The difference from existing volume nodes is that they output a grid directly instead of a geometry set. See the design here: https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 Pull Request: https://projects.blender.org/blender/blender/pulls/118761
2024-02-28 22:15:10 +01:00
if context.preferences.experimental.use_new_volume_nodes:
node_add_menu.add_node_type(layout, "GeometryNodePointsToSDFGrid")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodePointsToVertices")
node_add_menu.add_node_type(layout, "GeometryNodePointsToVolume")
layout.separator()
node_add_menu.add_node_type(layout, "GeometryNodeSetPointRadius")
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Geometry Nodes: add simulation support This adds support for building simulations with geometry nodes. A new `Simulation Input` and `Simulation Output` node allow maintaining a simulation state across multiple frames. Together these two nodes form a `simulation zone` which contains all the nodes that update the simulation state from one frame to the next. A new simulation zone can be added via the menu (`Simulation > Simulation Zone`) or with the node add search. The simulation state contains a geometry by default. However, it is possible to add multiple geometry sockets as well as other socket types. Currently, field inputs are evaluated and stored for the preceding geometry socket in the order that the sockets are shown. Simulation state items can be added by linking one of the empty sockets to something else. In the sidebar, there is a new panel that allows adding, removing and reordering these sockets. The simulation nodes behave as follows: * On the first frame, the inputs of the `Simulation Input` node are evaluated to initialize the simulation state. In later frames these sockets are not evaluated anymore. The `Delta Time` at the first frame is zero, but the simulation zone is still evaluated. * On every next frame, the `Simulation Input` node outputs the simulation state of the previous frame. Nodes in the simulation zone can edit that data in arbitrary ways, also taking into account the `Delta Time`. The new simulation state has to be passed to the `Simulation Output` node where it is cached and forwarded. * On a frame that is already cached or baked, the nodes in the simulation zone are not evaluated, because the `Simulation Output` node can return the previously cached data directly. It is not allowed to connect sockets from inside the simulation zone to the outside without going through the `Simulation Output` node. This is a necessary restriction to make caching and sub-frame interpolation work. Links can go into the simulation zone without problems though. Anonymous attributes are not propagated by the simulation nodes unless they are explicitly stored in the simulation state. This is unfortunate, but currently there is no practical and reliable alternative. The core problem is detecting which anonymous attributes will be required for the simulation and afterwards. While we can detect this for the current evaluation, we can't look into the future in time to see what data will be necessary. We intend to make it easier to explicitly pass data through a simulation in the future, even if the simulation is in a nested node group. There is a new `Simulation Nodes` panel in the physics tab in the properties editor. It allows baking all simulation zones on the selected objects. The baking options are intentially kept at a minimum for this MVP. More features for simulation baking as well as baking in general can be expected to be added separately. All baked data is stored on disk in a folder next to the .blend file. #106937 describes how baking is implemented in more detail. Volumes can not be baked yet and materials are lost during baking for now. Packing the baked data into the .blend file is not yet supported. The timeline indicates which frames are currently cached, baked or cached but invalidated by user-changes. Simulation input and output nodes are internally linked together by their `bNode.identifier` which stays the same even if the node name changes. They are generally added and removed together. However, there are still cases where "dangling" simulation nodes can be created currently. Those generally don't cause harm, but would be nice to avoid this in more cases in the future. Co-authored-by: Hans Goudey <h.goudey@me.com> Co-authored-by: Lukas Tönne <lukas@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/104924
2023-05-03 13:18:51 +02:00
class NODE_MT_category_simulation(Menu):
bl_idname = "NODE_MT_category_simulation"
bl_label = "Simulation"
def draw(self, _context):
layout = self.layout
Geometry Nodes: remove "Zone" from menu entries This was accepted in #128384. The term "zone" is known well enough now that it's not really necessary to show it in the menu anymore.
2024-09-30 17:09:00 +02:00
node_add_menu.add_simulation_zone(layout, label="Simulation")
Geometry Nodes: add simulation support This adds support for building simulations with geometry nodes. A new `Simulation Input` and `Simulation Output` node allow maintaining a simulation state across multiple frames. Together these two nodes form a `simulation zone` which contains all the nodes that update the simulation state from one frame to the next. A new simulation zone can be added via the menu (`Simulation > Simulation Zone`) or with the node add search. The simulation state contains a geometry by default. However, it is possible to add multiple geometry sockets as well as other socket types. Currently, field inputs are evaluated and stored for the preceding geometry socket in the order that the sockets are shown. Simulation state items can be added by linking one of the empty sockets to something else. In the sidebar, there is a new panel that allows adding, removing and reordering these sockets. The simulation nodes behave as follows: * On the first frame, the inputs of the `Simulation Input` node are evaluated to initialize the simulation state. In later frames these sockets are not evaluated anymore. The `Delta Time` at the first frame is zero, but the simulation zone is still evaluated. * On every next frame, the `Simulation Input` node outputs the simulation state of the previous frame. Nodes in the simulation zone can edit that data in arbitrary ways, also taking into account the `Delta Time`. The new simulation state has to be passed to the `Simulation Output` node where it is cached and forwarded. * On a frame that is already cached or baked, the nodes in the simulation zone are not evaluated, because the `Simulation Output` node can return the previously cached data directly. It is not allowed to connect sockets from inside the simulation zone to the outside without going through the `Simulation Output` node. This is a necessary restriction to make caching and sub-frame interpolation work. Links can go into the simulation zone without problems though. Anonymous attributes are not propagated by the simulation nodes unless they are explicitly stored in the simulation state. This is unfortunate, but currently there is no practical and reliable alternative. The core problem is detecting which anonymous attributes will be required for the simulation and afterwards. While we can detect this for the current evaluation, we can't look into the future in time to see what data will be necessary. We intend to make it easier to explicitly pass data through a simulation in the future, even if the simulation is in a nested node group. There is a new `Simulation Nodes` panel in the physics tab in the properties editor. It allows baking all simulation zones on the selected objects. The baking options are intentially kept at a minimum for this MVP. More features for simulation baking as well as baking in general can be expected to be added separately. All baked data is stored on disk in a folder next to the .blend file. #106937 describes how baking is implemented in more detail. Volumes can not be baked yet and materials are lost during baking for now. Packing the baked data into the .blend file is not yet supported. The timeline indicates which frames are currently cached, baked or cached but invalidated by user-changes. Simulation input and output nodes are internally linked together by their `bNode.identifier` which stays the same even if the node name changes. They are generally added and removed together. However, there are still cases where "dangling" simulation nodes can be created currently. Those generally don't cause harm, but would be nice to avoid this in more cases in the future. Co-authored-by: Hans Goudey <h.goudey@me.com> Co-authored-by: Lukas Tönne <lukas@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/104924
2023-05-03 13:18:51 +02:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_TEXT(Menu):
bl_idname = "NODE_MT_category_GEO_TEXT"
bl_label = "Text"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeStringJoin")
Geometry Nodes: Match String node Adds "Starts With", "Ends With", and "Compare" string operations as a standalone node. Pull Request: https://projects.blender.org/blender/blender/pulls/136021
2025-04-03 02:57:39 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeMatchString")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "FunctionNodeReplaceString")
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeSliceString")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.separator()
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeStringLength")
Geometry Nodes: Find in String node Add a node that finds the number of times a substring occurs in a string, and the position of the start of the first match. See the PR description for more rational and details. Pull Request: https://projects.blender.org/blender/blender/pulls/129270
2024-12-24 17:12:19 +01:00
node_add_menu.add_node_type(layout, "FunctionNodeFindInString")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeStringToCurves")
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeValueToString")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout.separator()
node_add_menu.add_node_type(layout, "FunctionNodeInputSpecialCharacters")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Utilities/Text")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_TEXTURE(Menu):
bl_idname = "NODE_MT_category_GEO_TEXTURE"
bl_label = "Texture"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "ShaderNodeTexBrick")
node_add_menu.add_node_type(layout, "ShaderNodeTexChecker")
Geometry Nodes: Implement Gabor noise node This patch ports the Gabor noise shader texture node into Geometry Nodes. Pull Request: https://projects.blender.org/blender/blender/pulls/125718
2024-08-14 08:48:17 +02:00
node_add_menu.add_node_type(layout, "ShaderNodeTexGabor")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "ShaderNodeTexGradient")
node_add_menu.add_node_type(layout, "GeometryNodeImageTexture")
node_add_menu.add_node_type(layout, "ShaderNodeTexMagic")
node_add_menu.add_node_type(layout, "ShaderNodeTexNoise")
node_add_menu.add_node_type(layout, "ShaderNodeTexVoronoi")
node_add_menu.add_node_type(layout, "ShaderNodeTexWave")
node_add_menu.add_node_type(layout, "ShaderNodeTexWhiteNoise")
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_UTILITIES(Menu):
bl_idname = "NODE_MT_category_GEO_UTILITIES"
bl_label = "Utilities"
Geometry Nodes: Matrix socket type, attribute type, and initial nodes Implements the design from #116067. The socket type is called "Matrix" but it is often referred to as "Transform" when that's what it is semantically. The attribute type is "4x4 Matrix" since that's a lower level choice. Currently matrix sockets are always passed around internally as `float4x4`, but that can be optimized in the future when smaller types would give the same behavior. A new "Matrix" utilities category has the following set of initial nodes" - **Combine Transform** - **Separate Transform** - **Multiply Matrices** - **Transform Direction** - **Transform Vector** - **Invert Matrix** - **Transpose Matrix** The nodes and socket type are behind an experimental flag for now, which will give us time to make sure it's the right set of initial nodes. The viewer node overlay doesn't support matrices-- they aren't supported for rendering in general. They also aren't supported in the modifier interface currently. But they are supported in the spreadsheet, where the value is displayed in a tooltip. Pull Request: https://projects.blender.org/blender/blender/pulls/116166
2024-02-13 18:59:36 +01:00
def draw(self, context):
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout = self.layout
layout.menu("NODE_MT_geometry_node_GEO_COLOR")
layout.menu("NODE_MT_category_GEO_TEXT")
layout.menu("NODE_MT_category_GEO_VECTOR")
layout.separator()
layout.menu("NODE_MT_category_GEO_UTILITIES_FIELD")
layout.menu("NODE_MT_category_GEO_UTILITIES_MATH")
Geometry Nodes: remove experimental option for matrix socket and nodes This makes the matrix socket and initial set of corresponding nodes non-experimental. That means, they'll be part of the next release. Pull Request: https://projects.blender.org/blender/blender/pulls/120539
2024-04-17 10:34:13 +02:00
layout.menu("NODE_MT_category_utilities_matrix")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_category_GEO_UTILITIES_ROTATION")
Nodes: improve handling of deprecated nodes In 4.1 we deprecate the `Rotate Euler` node in favor of the `Rotate Rotation` node which uses the new rotation socket type. The node is not removed (for now) because that would come with compatibility issues. More generally, we'll likely run into the situation where nodes are deprecated more often in the future, without actually removing them to keep compatibility. This patch improves how such nodes are handled in the UI. The patch does three things: * Adds a new `Utilities > Deprecated` entry in the add node menu in geometry nodes. * Moves search items which are deprecated to the bottom in the search results (currently, this only works in English, can be fixed in bcon3). * Adds a new `bNodeType->deprecation_notice` that will result in a deprecation warning when the node is used. Pull Request: https://projects.blender.org/blender/blender/pulls/117905
2024-02-06 19:08:01 +01:00
layout.menu("NODE_MT_category_GEO_UTILITIES_DEPRECATED")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.separator()
Geometry Nodes: add Closures and Bundles behind experimental feature flag This implements bundles and closures which are described in more detail in this blog post: https://code.blender.org/2024/11/geometry-nodes-workshop-october-2024/ tl;dr: * Bundles are containers that allow storing multiple socket values in a single value. Each value in the bundle is identified by a name. Bundles can be nested. * Closures are functions that are created with the Closure Zone and can be evaluated with the Evaluate Closure node. To use the patch, the `Bundle and Closure Nodes` experimental feature has to be enabled. This is necessary, because these features are not fully done yet and still need iterations to improve the workflow before they can be officially released. These iterations are easier to do in `main` than in a separate branch though. That's because this patch is quite large and somewhat prone to merge conflicts. Also other work we want to do, depends on this. This adds the following new nodes: * Combine Bundle: can pack multiple values into one. * Separate Bundle: extracts values from a bundle. * Closure Zone: outputs a closure zone for use in the `Evaluate Closure` node. * Evaluate Closure: evaluates the passed in closure. Things that will be added soon after this lands: * Fields in bundles and closures. The way this is done changes with #134811, so I rather implement this once both are in `main`. * UI features for keeping sockets in sync (right now there are warnings only). One bigger issue is the limited support for lazyness. For example, all inputs of a Combine Bundle node will be evaluated, even if they are not all needed. The same is true for all captured values of a closure. This is a deeper limitation that needs to be resolved at some point. This will likely be done after an initial version of this patch is done. Pull Request: https://projects.blender.org/blender/blender/pulls/128340
2025-04-03 15:44:06 +02:00
if context.preferences.experimental.use_bundle_and_closure_nodes:
node_add_menu.add_closure_zone(layout, label="Closure")
node_add_menu.add_node_type(layout, "GeometryNodeEvaluateClosure")
Geometry Nodes: remove "Zone" from menu entries This was accepted in #128384. The term "zone" is known well enough now that it's not really necessary to show it in the menu anymore.
2024-09-30 17:09:00 +02:00
node_add_menu.add_foreach_geometry_element_zone(layout, label="For Each Element")
Fix: Sort Index Switch node alphabetically in add menu
2024-01-29 14:17:10 -05:00
node_add_menu.add_node_type(layout, "GeometryNodeIndexSwitch")
Geometry Nodes: Menu Switch Node This patch adds support for _Menu Switch_ nodes and enum definitions in node trees more generally. The design is based on the outcome of the [2022 Nodes Workshop](https://code.blender.org/2022/11/geometry-nodes-workshop-2022/#menu-switch). The _Menu Switch_ node is an advanced version of the _Switch_ node which has a customizable **menu input socket** instead of a simple boolean. The _items_ of this menu are owned by the node itself. Each item has a name and description and unique identifier that is used internally. A menu _socket_ represents a concrete value out of the list of items. To enable selection of an enum value for unconnected sockets the menu is presented as a dropdown list like built-in enums. When the socket is connected a shared pointer to the enum definition is propagated along links and stored in socket default values. This allows node groups to expose a menu from an internal menu switch as a parameter. The enum definition is a runtime copy of the enum items in DNA that allows sharing. A menu socket can have multiple connections, which can lead to ambiguity. If two or more different menu source nodes are connected to a socket it gets marked as _undefined_. Any connection to an undefined menu socket is invalid as a hint to users that there is a problem. A warning/error is also shown on nodes with undefined menu sockets. At runtime the value of a menu socket is the simple integer identifier. This can also be a field in geometry nodes. The identifier is unique within each enum definition, and it is persistent even when items are added, removed, or changed. Changing the name of an item does not affect the internal identifier, so users can rename enum items without breaking existing input values. This also persists if, for example, a linked node group is temporarily unavailable. Pull Request: https://projects.blender.org/blender/blender/pulls/113445
2024-01-26 12:40:01 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeMenuSwitch")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "FunctionNodeRandomValue")
Geometry Nodes: remove "Zone" from menu entries This was accepted in #128384. The term "zone" is known well enough now that it's not really necessary to show it in the menu anymore.
2024-09-30 17:09:00 +02:00
node_add_menu.add_repeat_zone(layout, label="Repeat")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeSwitch")
Geometry Nodes: add Closures and Bundles behind experimental feature flag This implements bundles and closures which are described in more detail in this blog post: https://code.blender.org/2024/11/geometry-nodes-workshop-october-2024/ tl;dr: * Bundles are containers that allow storing multiple socket values in a single value. Each value in the bundle is identified by a name. Bundles can be nested. * Closures are functions that are created with the Closure Zone and can be evaluated with the Evaluate Closure node. To use the patch, the `Bundle and Closure Nodes` experimental feature has to be enabled. This is necessary, because these features are not fully done yet and still need iterations to improve the workflow before they can be officially released. These iterations are easier to do in `main` than in a separate branch though. That's because this patch is quite large and somewhat prone to merge conflicts. Also other work we want to do, depends on this. This adds the following new nodes: * Combine Bundle: can pack multiple values into one. * Separate Bundle: extracts values from a bundle. * Closure Zone: outputs a closure zone for use in the `Evaluate Closure` node. * Evaluate Closure: evaluates the passed in closure. Things that will be added soon after this lands: * Fields in bundles and closures. The way this is done changes with #134811, so I rather implement this once both are in `main`. * UI features for keeping sockets in sync (right now there are warnings only). One bigger issue is the limited support for lazyness. For example, all inputs of a Combine Bundle node will be evaluated, even if they are not all needed. The same is true for all captured values of a closure. This is a deeper limitation that needs to be resolved at some point. This will likely be done after an initial version of this patch is done. Pull Request: https://projects.blender.org/blender/blender/pulls/128340
2025-04-03 15:44:06 +02:00
if context.preferences.experimental.use_bundle_and_closure_nodes:
node_add_menu.add_node_type(layout, "GeometryNodeCombineBundle")
node_add_menu.add_node_type(layout, "GeometryNodeSeparateBundle")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: improve handling of deprecated nodes In 4.1 we deprecate the `Rotate Euler` node in favor of the `Rotate Rotation` node which uses the new rotation socket type. The node is not removed (for now) because that would come with compatibility issues. More generally, we'll likely run into the situation where nodes are deprecated more often in the future, without actually removing them to keep compatibility. This patch improves how such nodes are handled in the UI. The patch does three things: * Adds a new `Utilities > Deprecated` entry in the add node menu in geometry nodes. * Moves search items which are deprecated to the bottom in the search results (currently, this only works in English, can be fixed in bcon3). * Adds a new `bNodeType->deprecation_notice` that will result in a deprecation warning when the node is used. Pull Request: https://projects.blender.org/blender/blender/pulls/117905
2024-02-06 19:08:01 +01:00
class NODE_MT_category_GEO_UTILITIES_DEPRECATED(Menu):
bl_idname = "NODE_MT_category_GEO_UTILITIES_DEPRECATED"
bl_label = "Deprecated"
def draw(self, context):
layout = self.layout
Geometry Nodes: Add Align Rotation to Vector node A version of "Align Euler to Vector" with the rotation socket instead of the vector Euler socket. Other than that, and a few cleanups to use newer math functions, the node is the same. The old node is just "Deprecated" for now. We could remove it with versioning, but we can also wait to do that. In a simple test this node is about 1.7 times faster than the old one. Pull Request: https://projects.blender.org/blender/blender/pulls/118565
2024-04-30 15:52:11 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeAlignEulerToVector")
Nodes: improve handling of deprecated nodes In 4.1 we deprecate the `Rotate Euler` node in favor of the `Rotate Rotation` node which uses the new rotation socket type. The node is not removed (for now) because that would come with compatibility issues. More generally, we'll likely run into the situation where nodes are deprecated more often in the future, without actually removing them to keep compatibility. This patch improves how such nodes are handled in the UI. The patch does three things: * Adds a new `Utilities > Deprecated` entry in the add node menu in geometry nodes. * Moves search items which are deprecated to the bottom in the search results (currently, this only works in English, can be fixed in bcon3). * Adds a new `bNodeType->deprecation_notice` that will result in a deprecation warning when the node is used. Pull Request: https://projects.blender.org/blender/blender/pulls/117905
2024-02-06 19:08:01 +01:00
node_add_menu.add_node_type(layout, "FunctionNodeRotateEuler")
Fix: Redundant submenus are created in the Add menu for certain catalog names A few of the recently added submenus are not included in the list of builtin menus, so node assets under those catalog names will generate redundant submenus. Fixes same issue as b49c84276c for newly added nested menus. Pull Request: https://projects.blender.org/blender/blender/pulls/122855
2024-06-06 23:39:00 +02:00
node_add_menu.draw_assets_for_catalog(layout, "Utilities/Deprecated")
Nodes: improve handling of deprecated nodes In 4.1 we deprecate the `Rotate Euler` node in favor of the `Rotate Rotation` node which uses the new rotation socket type. The node is not removed (for now) because that would come with compatibility issues. More generally, we'll likely run into the situation where nodes are deprecated more often in the future, without actually removing them to keep compatibility. This patch improves how such nodes are handled in the UI. The patch does three things: * Adds a new `Utilities > Deprecated` entry in the add node menu in geometry nodes. * Moves search items which are deprecated to the bottom in the search results (currently, this only works in English, can be fixed in bcon3). * Adds a new `bNodeType->deprecation_notice` that will result in a deprecation warning when the node is used. Pull Request: https://projects.blender.org/blender/blender/pulls/117905
2024-02-06 19:08:01 +01:00
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_category_GEO_UTILITIES_FIELD(Menu):
bl_idname = "NODE_MT_category_GEO_UTILITIES_FIELD"
bl_label = "Field"
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeAccumulateField")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
node_add_menu.add_node_type(layout, "GeometryNodeFieldAtIndex")
node_add_menu.add_node_type(layout, "GeometryNodeFieldOnDomain")
Geometry Nodes: Field Statistic Nodes Adds field versions of the operations from Attribute Statistic, can support grouping via Group IDs. These operations are added as separate nodes: `Field Average`, `Field Min & Max`, & `Field Variance` which group the different statistic operations according to their use. Supported Data Types: - Field Average - (Float, Vector) - Field Min & Max - (Float, Integer, Vector) - Field Variance - (Float, Vector) Pull Request: https://projects.blender.org/blender/blender/pulls/134640
2025-04-08 17:12:08 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeFieldAverage")
node_add_menu.add_node_type(layout, "GeometryNodeFieldMinAndMax")
node_add_menu.add_node_type(layout, "GeometryNodeFieldVariance")
Fix: Node assets are missing from the Add menu for certain catalog names Add > Utilities submenus for Color and Field do not include assets from the correctly named catalogs due to typos: "Utilties/Color" and "Utilties/Field" respectively. Pull Request: https://projects.blender.org/blender/blender/pulls/122416
2024-05-29 05:44:47 +02:00
node_add_menu.draw_assets_for_catalog(layout, "Utilities/Field")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_category_GEO_UTILITIES_ROTATION(Menu):
bl_idname = "NODE_MT_category_GEO_UTILITIES_ROTATION"
bl_label = "Rotation"
def draw(self, _context):
layout = self.layout
Geometry Nodes: Add Align Rotation to Vector node A version of "Align Euler to Vector" with the rotation socket instead of the vector Euler socket. Other than that, and a few cleanups to use newer math functions, the node is the same. The old node is just "Deprecated" for now. We could remove it with versioning, but we can also wait to do that. In a simple test this node is about 1.7 times faster than the old one. Pull Request: https://projects.blender.org/blender/blender/pulls/118565
2024-04-30 15:52:11 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeAlignRotationToVector")
Geometry Nodes: new Axes to Rotation node This adds a new `Axes to Rotation` node which creates a new rotation. In many cases, the primary and secondary axis inputs are a normal and tangent of a mesh or curve. This provides a simpler and more direct way to create this rotation compared to using two `Align Rotation to Vector` nodes. This more direct way of computing the rotation also allows us to optimize the case better. The node rotates one axis (X, Y or Z) to the given primary axis direction. Then it rotates around that primary direction to align the second axis to the given secondary direction. Ideally, both input axes are orthogonal. However, the node still creates the "best" rotation when they are not orthogonal. If one or the axes is zero or both are (close to) parallel, the resulting rotation is unstable. There is not too much the node can do to make it more stable. Pull Request: https://projects.blender.org/blender/blender/pulls/104416
2024-05-08 13:34:14 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeAxesToRotation")
Geometry Nodes: Initial basic rotation socket nodes This PR adds an initial set of nodes using the new rotation socket. 6 nodes build rotations or convert them to other formats, a 7th rotates a vector with a rotation, and the last inverts rotations. The design task #109965 describes the choice to use separate nodes for the rotation construction and separation operations. In the future, a "Switch Node" operator (#111438) will help to make working with these separated nodes faster. - **Axis Angle to Rotation** - **Rotation to Axis Angle** - **Combine Quaternion** - **Separate Quaternion** - **Euler to Rotation** - **Rotation to Euler** - **Rotate Vector** - **Invert Rotation** See #92967 Pull Request: https://projects.blender.org/blender/blender/pulls/109030
2023-08-24 14:58:55 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeAxisAngleToRotation")
node_add_menu.add_node_type(layout, "FunctionNodeEulerToRotation")
node_add_menu.add_node_type(layout, "FunctionNodeInvertRotation")
Geometry Nodes: Add Rotate Rotation node This is meant as a replacement for the Rotate Euler node. Overall it should be more performant, and the clarity given by the separate socket type should help distinguish its purpose. The Rotate Euler node is removed from search and the add menu by this commit. In the future it can be versioned away. That isn't done now to avoid a breaking API change and to make this commit less risky. Pull Request: https://projects.blender.org/blender/blender/pulls/116106
2024-02-01 14:29:30 +01:00
node_add_menu.add_node_type(layout, "FunctionNodeRotateRotation")
Geometry Nodes: Initial basic rotation socket nodes This PR adds an initial set of nodes using the new rotation socket. 6 nodes build rotations or convert them to other formats, a 7th rotates a vector with a rotation, and the last inverts rotations. The design task #109965 describes the choice to use separate nodes for the rotation construction and separation operations. In the future, a "Switch Node" operator (#111438) will help to make working with these separated nodes faster. - **Axis Angle to Rotation** - **Rotation to Axis Angle** - **Combine Quaternion** - **Separate Quaternion** - **Euler to Rotation** - **Rotation to Euler** - **Rotate Vector** - **Invert Rotation** See #92967 Pull Request: https://projects.blender.org/blender/blender/pulls/109030
2023-08-24 14:58:55 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeRotateVector")
node_add_menu.add_node_type(layout, "FunctionNodeRotationToAxisAngle")
node_add_menu.add_node_type(layout, "FunctionNodeRotationToEuler")
node_add_menu.add_node_type(layout, "FunctionNodeRotationToQuaternion")
node_add_menu.add_node_type(layout, "FunctionNodeQuaternionToRotation")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Utilities/Rotation")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
Cleanup: make format
2023-01-16 14:39:10 +01:00
Geometry Nodes: Matrix socket type, attribute type, and initial nodes Implements the design from #116067. The socket type is called "Matrix" but it is often referred to as "Transform" when that's what it is semantically. The attribute type is "4x4 Matrix" since that's a lower level choice. Currently matrix sockets are always passed around internally as `float4x4`, but that can be optimized in the future when smaller types would give the same behavior. A new "Matrix" utilities category has the following set of initial nodes" - **Combine Transform** - **Separate Transform** - **Multiply Matrices** - **Transform Direction** - **Transform Vector** - **Invert Matrix** - **Transpose Matrix** The nodes and socket type are behind an experimental flag for now, which will give us time to make sure it's the right set of initial nodes. The viewer node overlay doesn't support matrices-- they aren't supported for rendering in general. They also aren't supported in the modifier interface currently. But they are supported in the spreadsheet, where the value is displayed in a tooltip. Pull Request: https://projects.blender.org/blender/blender/pulls/116166
2024-02-13 18:59:36 +01:00
class NODE_MT_category_utilities_matrix(Menu):
bl_idname = "NODE_MT_category_utilities_matrix"
bl_label = "Matrix"
def draw(self, _context):
layout = self.layout
Geometry Nodes: support working with raw matrix values These nodes allow working with the raw values that make up a matrix. This can be used to construct a 4x4 matrix directly, without using the `Combine Transform` node. This allows building transforms with arbitrary skew, or projection matrices. Pull Request: https://projects.blender.org/blender/blender/pulls/121283
2024-05-01 21:31:08 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeCombineMatrix")
Geometry Nodes: Matrix socket type, attribute type, and initial nodes Implements the design from #116067. The socket type is called "Matrix" but it is often referred to as "Transform" when that's what it is semantically. The attribute type is "4x4 Matrix" since that's a lower level choice. Currently matrix sockets are always passed around internally as `float4x4`, but that can be optimized in the future when smaller types would give the same behavior. A new "Matrix" utilities category has the following set of initial nodes" - **Combine Transform** - **Separate Transform** - **Multiply Matrices** - **Transform Direction** - **Transform Vector** - **Invert Matrix** - **Transpose Matrix** The nodes and socket type are behind an experimental flag for now, which will give us time to make sure it's the right set of initial nodes. The viewer node overlay doesn't support matrices-- they aren't supported for rendering in general. They also aren't supported in the modifier interface currently. But they are supported in the spreadsheet, where the value is displayed in a tooltip. Pull Request: https://projects.blender.org/blender/blender/pulls/116166
2024-02-13 18:59:36 +01:00
node_add_menu.add_node_type(layout, "FunctionNodeCombineTransform")
Geometry Nodes: add Matrix Determinant node Pull Request: https://projects.blender.org/blender/blender/pulls/128212
2024-09-30 21:30:10 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeMatrixDeterminant", label="Determinant")
Geometry Nodes: Matrix socket type, attribute type, and initial nodes Implements the design from #116067. The socket type is called "Matrix" but it is often referred to as "Transform" when that's what it is semantically. The attribute type is "4x4 Matrix" since that's a lower level choice. Currently matrix sockets are always passed around internally as `float4x4`, but that can be optimized in the future when smaller types would give the same behavior. A new "Matrix" utilities category has the following set of initial nodes" - **Combine Transform** - **Separate Transform** - **Multiply Matrices** - **Transform Direction** - **Transform Vector** - **Invert Matrix** - **Transpose Matrix** The nodes and socket type are behind an experimental flag for now, which will give us time to make sure it's the right set of initial nodes. The viewer node overlay doesn't support matrices-- they aren't supported for rendering in general. They also aren't supported in the modifier interface currently. But they are supported in the spreadsheet, where the value is displayed in a tooltip. Pull Request: https://projects.blender.org/blender/blender/pulls/116166
2024-02-13 18:59:36 +01:00
node_add_menu.add_node_type(layout, "FunctionNodeInvertMatrix")
node_add_menu.add_node_type(layout, "FunctionNodeMatrixMultiply")
Geometry Nodes: Add Project point matrix node With the matrix socket being introduced into geometry nodes, we are starting to deal with more complex transforms like perspective projection. For those matrices projecting a point is not as simple as just matrix multiplication, there has to be an additional normalization step after. To solve that in an intuitive way consistent with how it's typically solved in code, add a new "Project Point" node. The canonical use case for now is in combination with the mouse position, viewport transform, and raycast nodes, to find where the mouse clicked on the edited geometry. Pull Request: https://projects.blender.org/blender/blender/pulls/120597
2024-04-24 15:56:33 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeProjectPoint")
Geometry Nodes: support working with raw matrix values These nodes allow working with the raw values that make up a matrix. This can be used to construct a 4x4 matrix directly, without using the `Combine Transform` node. This allows building transforms with arbitrary skew, or projection matrices. Pull Request: https://projects.blender.org/blender/blender/pulls/121283
2024-05-01 21:31:08 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeSeparateMatrix")
Geometry Nodes: Matrix socket type, attribute type, and initial nodes Implements the design from #116067. The socket type is called "Matrix" but it is often referred to as "Transform" when that's what it is semantically. The attribute type is "4x4 Matrix" since that's a lower level choice. Currently matrix sockets are always passed around internally as `float4x4`, but that can be optimized in the future when smaller types would give the same behavior. A new "Matrix" utilities category has the following set of initial nodes" - **Combine Transform** - **Separate Transform** - **Multiply Matrices** - **Transform Direction** - **Transform Vector** - **Invert Matrix** - **Transpose Matrix** The nodes and socket type are behind an experimental flag for now, which will give us time to make sure it's the right set of initial nodes. The viewer node overlay doesn't support matrices-- they aren't supported for rendering in general. They also aren't supported in the modifier interface currently. But they are supported in the spreadsheet, where the value is displayed in a tooltip. Pull Request: https://projects.blender.org/blender/blender/pulls/116166
2024-02-13 18:59:36 +01:00
node_add_menu.add_node_type(layout, "FunctionNodeSeparateTransform")
node_add_menu.add_node_type(layout, "FunctionNodeTransformDirection")
node_add_menu.add_node_type(layout, "FunctionNodeTransformPoint")
node_add_menu.add_node_type(layout, "FunctionNodeTransposeMatrix")
node_add_menu.draw_assets_for_catalog(layout, "Utilities/Matrix")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
class NODE_MT_category_GEO_UTILITIES_MATH(Menu):
bl_idname = "NODE_MT_category_GEO_UTILITIES_MATH"
bl_label = "Math"
Nodes: support searching for specific math operations in Add menu Previously, it was possible to search for specific math operations in link-drag-search but not in the normal add menu. This patch adds support for searching for specific operations in various math nodes. A good trick for adding e.g. a vector add node is to search for `vadd` (similarly with `iadd`). The menu itself looks unchanged. This patch only adds additional elements to the search. Pull Request: https://projects.blender.org/blender/blender/pulls/138534
2025-05-08 04:28:22 +02:00
def draw(self, context):
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout = self.layout
Nodes: support searching for specific math operations in Add menu Previously, it was possible to search for specific math operations in link-drag-search but not in the normal add menu. This patch adds support for searching for specific operations in various math nodes. A good trick for adding e.g. a vector add node is to search for `vadd` (similarly with `iadd`). The menu itself looks unchanged. This patch only adds additional elements to the search. Pull Request: https://projects.blender.org/blender/blender/pulls/138534
2025-05-08 04:28:22 +02:00
node_add_menu.add_node_type_with_searchable_enum(context, layout, "FunctionNodeBooleanMath", "operation")
node_add_menu.add_node_type_with_searchable_enum(context, layout, "FunctionNodeIntegerMath", "operation")
UI: Nodes re-organize the nodes in alphabetical order This was a regression introduced after the 3.3 release. This fix T101452
2022-09-29 11:08:21 +02:00
node_add_menu.add_node_type(layout, "ShaderNodeClamp")
node_add_menu.add_node_type(layout, "FunctionNodeCompare")
node_add_menu.add_node_type(layout, "ShaderNodeFloatCurve")
node_add_menu.add_node_type(layout, "FunctionNodeFloatToInt")
Geometry Nodes: new Hash Value node This node hashes various types into an integer. Note that hashes cannot generally used as unique identifiers because they are not guaranteed to be unique. It can be used to generate somewhat stable randomness though in cases where White Noise does not offer enough flexibility. It uses hash functions from BLI_noise.hh. These are also used in the White Noise node. Pull Request: https://projects.blender.org/blender/blender/pulls/110769
2024-08-30 16:42:29 +02:00
node_add_menu.add_node_type(layout, "FunctionNodeHashValue")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "ShaderNodeMapRange")
Nodes: support searching for specific math operations in Add menu Previously, it was possible to search for specific math operations in link-drag-search but not in the normal add menu. This patch adds support for searching for specific operations in various math nodes. A good trick for adding e.g. a vector add node is to search for `vadd` (similarly with `iadd`). The menu itself looks unchanged. This patch only adds additional elements to the search. Pull Request: https://projects.blender.org/blender/blender/pulls/138534
2025-05-08 04:28:22 +02:00
node_add_menu.add_node_type_with_searchable_enum(context, layout, "ShaderNodeMath", "operation")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "ShaderNodeMix")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Utilities/Math")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_UV(Menu):
bl_idname = "NODE_MT_category_GEO_UV"
bl_label = "UV"
def draw(self, _context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeUVPackIslands")
node_add_menu.add_node_type(layout, "GeometryNodeUVUnwrap")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Mesh/UV")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_VECTOR(Menu):
bl_idname = "NODE_MT_category_GEO_VECTOR"
bl_label = "Vector"
Nodes: support searching for specific math operations in Add menu Previously, it was possible to search for specific math operations in link-drag-search but not in the normal add menu. This patch adds support for searching for specific operations in various math nodes. A good trick for adding e.g. a vector add node is to search for `vadd` (similarly with `iadd`). The menu itself looks unchanged. This patch only adds additional elements to the search. Pull Request: https://projects.blender.org/blender/blender/pulls/138534
2025-05-08 04:28:22 +02:00
def draw(self, context):
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout = self.layout
node_add_menu.add_node_type(layout, "ShaderNodeVectorCurve")
Nodes: support searching for specific math operations in Add menu Previously, it was possible to search for specific math operations in link-drag-search but not in the normal add menu. This patch adds support for searching for specific operations in various math nodes. A good trick for adding e.g. a vector add node is to search for `vadd` (similarly with `iadd`). The menu itself looks unchanged. This patch only adds additional elements to the search. Pull Request: https://projects.blender.org/blender/blender/pulls/138534
2025-05-08 04:28:22 +02:00
node_add_menu.add_node_type_with_searchable_enum(context, layout, "ShaderNodeVectorMath", "operation")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
node_add_menu.add_node_type(layout, "ShaderNodeVectorRotate")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.separator()
node_add_menu.add_node_type(layout, "ShaderNodeCombineXYZ")
props = node_add_menu.add_node_type(layout, "ShaderNodeMix", label=iface_("Mix Vector"))
ops = props.settings.add()
ops.name = "data_type"
ops.value = "'VECTOR'"
node_add_menu.add_node_type(layout, "ShaderNodeSeparateXYZ")
Geometry Nodes: Fix Support for extending nested menus with assets The builtin asset catalog paths weren't properly updated after more nesting was added to the geometry nodes add menu. This commit resolves that and a few other issues extending menus like nested menus in mesh edit mode. Unfortunately this requires some boilerplate code duplicating the menu structure currently.
2023-09-26 17:01:30 -04:00
node_add_menu.draw_assets_for_catalog(layout, "Utilities/Vector")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_VOLUME(Menu):
bl_idname = "NODE_MT_category_GEO_VOLUME"
bl_label = "Volume"
I18n: disambiguate a few messages - "Lens" can be a transparent object used in cameras, or specifically its property of focal length - "Empty" can be an adjective meaning void, or an object type. The latter is already disambiguated using `ID_ID` - "New" and "Old" are adjectives that can have agreements in some languages - "Modified" is an adjective that can have agreement in some languages - "Clipping" can be a property of a camera, or a behavior of the mirror modifier - "Value" in HSV nodes, see #105113 - "Area" in the Face Area geometry node, can mean a measurement or a window type - "New" is an adjective that can have agreement - "Tab" can be a UI element or a whitespace character - "Volume" can mean a measurement or an object type. The latter is already disambiguated using `ID_ID` These changes introduce the new `BLT_I18NCONTEXT_TIME` translation context. They also remove `BLT_I18NCONTEXT_VIRTUAL_REALITY`, which I added at one point but then couldn't find which messages I wanted to fix with it. Ref #43295 Pull Request: #106718
2023-02-23 22:00:57 +01:00
bl_translation_context = i18n_contexts.id_id
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: remove unused argument signified from used arguments in Python Also simplify import for `_bpy._utils_previews`.
2023-03-23 15:31:14 +11:00
def draw(self, context):
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout = self.layout
Geometry Nodes: initial Volume Grid socket support This is the initial implementation for the volume grid sockets that has been discussed during the November 2023 geometry nodes workshop. It adds initial support for passing volume grids around in sockets. Furthermore, it adds two new nodes. Both are initially hidden under the "New Volume Nodes" experimental option until we have a few mode nodes. * **Get Named Grid**: Gets or extracts a volume grid from a volume geometry based on the grid's name. * **Store Named Grid**: Puts a volume grid back into a volume with a name. `SocketValueVariant` is extended to support grids besides single values and fields. Next steps: * Implement grid socket shape and inferencing (currently, they just look like single values). * Add implicit conversions between grid types. * Implement nodes that operate on the grids (#116021). * Improved spreadsheet and viewer support. Links: * https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 * https://devtalk.blender.org/t/2023-11-06-geometry-nodes-workshop-notes/32007#volumes-3 Co-authored-by: Jacques Lucke <jacques@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/115270
2023-12-20 22:33:17 +01:00
if context.preferences.experimental.use_new_volume_nodes:
layout.menu("NODE_MT_geometry_node_GEO_VOLUME_READ")
Geometry Nodes: Sample grid node This simple node finds the values of a volume grid at positions in the local space used in geometry nodes evaluation. There are three interpolation modes to choose how to mix values between neighboring voxels. For the implementation, first the values are sampled with the grid's type directly, then implicit type conversions are used to get the final type. This makes gives us flexibility in case there aren't exact matches in support between grid types and Blender types. Pull Request: https://projects.blender.org/blender/blender/pulls/118397
2024-02-22 17:58:09 +01:00
layout.menu("NODE_MT_geometry_node_volume_sample")
Geometry Nodes: initial Volume Grid socket support This is the initial implementation for the volume grid sockets that has been discussed during the November 2023 geometry nodes workshop. It adds initial support for passing volume grids around in sockets. Furthermore, it adds two new nodes. Both are initially hidden under the "New Volume Nodes" experimental option until we have a few mode nodes. * **Get Named Grid**: Gets or extracts a volume grid from a volume geometry based on the grid's name. * **Store Named Grid**: Puts a volume grid back into a volume with a name. `SocketValueVariant` is extended to support grids besides single values and fields. Next steps: * Implement grid socket shape and inferencing (currently, they just look like single values). * Add implicit conversions between grid types. * Implement nodes that operate on the grids (#116021). * Improved spreadsheet and viewer support. Links: * https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 * https://devtalk.blender.org/t/2023-11-06-geometry-nodes-workshop-notes/32007#volumes-3 Co-authored-by: Jacques Lucke <jacques@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/115270
2023-12-20 22:33:17 +01:00
layout.menu("NODE_MT_geometry_node_GEO_VOLUME_WRITE")
layout.separator()
layout.menu("NODE_MT_geometry_node_GEO_VOLUME_OPERATIONS")
layout.menu("NODE_MT_geometry_node_GEO_VOLUME_PRIMITIVES")
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Geometry Nodes: initial Volume Grid socket support This is the initial implementation for the volume grid sockets that has been discussed during the November 2023 geometry nodes workshop. It adds initial support for passing volume grids around in sockets. Furthermore, it adds two new nodes. Both are initially hidden under the "New Volume Nodes" experimental option until we have a few mode nodes. * **Get Named Grid**: Gets or extracts a volume grid from a volume geometry based on the grid's name. * **Store Named Grid**: Puts a volume grid back into a volume with a name. `SocketValueVariant` is extended to support grids besides single values and fields. Next steps: * Implement grid socket shape and inferencing (currently, they just look like single values). * Add implicit conversions between grid types. * Implement nodes that operate on the grids (#116021). * Improved spreadsheet and viewer support. Links: * https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 * https://devtalk.blender.org/t/2023-11-06-geometry-nodes-workshop-notes/32007#volumes-3 Co-authored-by: Jacques Lucke <jacques@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/115270
2023-12-20 22:33:17 +01:00
class NODE_MT_geometry_node_GEO_VOLUME_READ(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_VOLUME_READ"
bl_label = "Read"
def draw(self, context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeGetNamedGrid")
New Grid Info node for reading grid transforms and background value These are generic properties of grids (not stored in voxels) which are useful to know in geometry nodes. The transform in particular defines the voxel size. Background value is used outside of active voxels. Pull Request: https://projects.blender.org/blender/blender/pulls/138592
2025-05-12 13:46:40 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeGridInfo")
Geometry Nodes: initial Volume Grid socket support This is the initial implementation for the volume grid sockets that has been discussed during the November 2023 geometry nodes workshop. It adds initial support for passing volume grids around in sockets. Furthermore, it adds two new nodes. Both are initially hidden under the "New Volume Nodes" experimental option until we have a few mode nodes. * **Get Named Grid**: Gets or extracts a volume grid from a volume geometry based on the grid's name. * **Store Named Grid**: Puts a volume grid back into a volume with a name. `SocketValueVariant` is extended to support grids besides single values and fields. Next steps: * Implement grid socket shape and inferencing (currently, they just look like single values). * Add implicit conversions between grid types. * Implement nodes that operate on the grids (#116021). * Improved spreadsheet and viewer support. Links: * https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 * https://devtalk.blender.org/t/2023-11-06-geometry-nodes-workshop-notes/32007#volumes-3 Co-authored-by: Jacques Lucke <jacques@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/115270
2023-12-20 22:33:17 +01:00
node_add_menu.draw_assets_for_catalog(layout, "Volume/Read")
class NODE_MT_geometry_node_GEO_VOLUME_WRITE(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_VOLUME_WRITE"
bl_label = "Write"
def draw(self, context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeStoreNamedGrid")
node_add_menu.draw_assets_for_catalog(layout, "Volume/Write")
Geometry Nodes: Sample grid node This simple node finds the values of a volume grid at positions in the local space used in geometry nodes evaluation. There are three interpolation modes to choose how to mix values between neighboring voxels. For the implementation, first the values are sampled with the grid's type directly, then implicit type conversions are used to get the final type. This makes gives us flexibility in case there aren't exact matches in support between grid types and Blender types. Pull Request: https://projects.blender.org/blender/blender/pulls/118397
2024-02-22 17:58:09 +01:00
class NODE_MT_geometry_node_volume_sample(Menu):
bl_idname = "NODE_MT_geometry_node_volume_sample"
bl_label = "Sample"
def draw(self, context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeSampleGrid")
Geometry Nodes: Sample Grid Index node This (experimental, for now) node retrieve's voxel values at specific voxel indices for a grid input. It's similar to the Sample Grid node (77cba3d5518d8b75da78), but there is no interpolation, and it uses indices instead of positions. Pull Request: https://projects.blender.org/blender/blender/pulls/118690
2024-05-07 21:53:22 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSampleGridIndex")
Geometry Nodes: Sample grid node This simple node finds the values of a volume grid at positions in the local space used in geometry nodes evaluation. There are three interpolation modes to choose how to mix values between neighboring voxels. For the implementation, first the values are sampled with the grid's type directly, then implicit type conversions are used to get the final type. This makes gives us flexibility in case there aren't exact matches in support between grid types and Blender types. Pull Request: https://projects.blender.org/blender/blender/pulls/118397
2024-02-22 17:58:09 +01:00
node_add_menu.draw_assets_for_catalog(layout, "Volume/Sample")
Geometry Nodes: initial Volume Grid socket support This is the initial implementation for the volume grid sockets that has been discussed during the November 2023 geometry nodes workshop. It adds initial support for passing volume grids around in sockets. Furthermore, it adds two new nodes. Both are initially hidden under the "New Volume Nodes" experimental option until we have a few mode nodes. * **Get Named Grid**: Gets or extracts a volume grid from a volume geometry based on the grid's name. * **Store Named Grid**: Puts a volume grid back into a volume with a name. `SocketValueVariant` is extended to support grids besides single values and fields. Next steps: * Implement grid socket shape and inferencing (currently, they just look like single values). * Add implicit conversions between grid types. * Implement nodes that operate on the grids (#116021). * Improved spreadsheet and viewer support. Links: * https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 * https://devtalk.blender.org/t/2023-11-06-geometry-nodes-workshop-notes/32007#volumes-3 Co-authored-by: Jacques Lucke <jacques@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/115270
2023-12-20 22:33:17 +01:00
class NODE_MT_geometry_node_GEO_VOLUME_OPERATIONS(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_VOLUME_OPERATIONS"
bl_label = "Operations"
def draw(self, context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeVolumeToMesh")
Geometry Nodes: Add volume grid conversion nodes Adds two nodes as "grid" equivalents to the existing volume nodes: - **Grid to Mesh** - **Distribute Points in Grid** The code for the latter is just duplicated for now. In a later step old node can be replaced by versioning with two new nodes. Pull Request: https://projects.blender.org/blender/blender/pulls/118830
2024-02-29 01:20:27 +01:00
if context.preferences.experimental.use_new_volume_nodes:
node_add_menu.add_node_type(layout, "GeometryNodeGridToMesh")
Geometry Nodes: Add SDF grid boolean nodes Add a simple node to compute the intersection, difference, or union between SDF grids. This should be the first new use case for the new volume grid nodes that wasn't possible before. For naming and multi-inputs, the node uses the same design as the mesh boolean node. We considered splitting each operation into a separate node, but though most users considered these different "modes" of the same operation. One thing to keep in mind is that it's important for the grids to have exactly the same transform. If they have different transforms, the second grid must be resampled to match the first, because the OpenVDB CSG tools have that requirement. Resampling is expensive (for SDF grids it means a grid -> mesh -> grid round trip) and should be avoided. Pull Request: https://projects.blender.org/blender/blender/pulls/118879
2024-04-23 14:48:59 +02:00
node_add_menu.add_node_type(layout, "GeometryNodeSDFGridBoolean")
Geometry Nodes: initial Volume Grid socket support This is the initial implementation for the volume grid sockets that has been discussed during the November 2023 geometry nodes workshop. It adds initial support for passing volume grids around in sockets. Furthermore, it adds two new nodes. Both are initially hidden under the "New Volume Nodes" experimental option until we have a few mode nodes. * **Get Named Grid**: Gets or extracts a volume grid from a volume geometry based on the grid's name. * **Store Named Grid**: Puts a volume grid back into a volume with a name. `SocketValueVariant` is extended to support grids besides single values and fields. Next steps: * Implement grid socket shape and inferencing (currently, they just look like single values). * Add implicit conversions between grid types. * Implement nodes that operate on the grids (#116021). * Improved spreadsheet and viewer support. Links: * https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 * https://devtalk.blender.org/t/2023-11-06-geometry-nodes-workshop-notes/32007#volumes-3 Co-authored-by: Jacques Lucke <jacques@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/115270
2023-12-20 22:33:17 +01:00
node_add_menu.draw_assets_for_catalog(layout, "Volume/Operations")
class NODE_MT_geometry_node_GEO_VOLUME_PRIMITIVES(Menu):
bl_idname = "NODE_MT_geometry_node_GEO_VOLUME_PRIMITIVES"
bl_label = "Primitives"
def draw(self, context):
layout = self.layout
node_add_menu.add_node_type(layout, "GeometryNodeVolumeCube")
node_add_menu.draw_assets_for_catalog(layout, "Volume/Primitives")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_category_GEO_GROUP(Menu):
bl_idname = "NODE_MT_category_GEO_GROUP"
bl_label = "Group"
def draw(self, context):
layout = self.layout
node_add_menu.draw_node_group_add_menu(context, layout)
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_assets_for_catalog(layout, self.bl_label)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
Cleanup: format
2022-09-27 16:36:27 +10:00
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
class NODE_MT_geometry_node_add_all(Menu):
bl_idname = "NODE_MT_geometry_node_add_all"
bl_label = ""
Geometry Nodes: Initial tool-specific nodes Add three new nodes for operations and inputs specific to node group operators. - **Selection** Whether elements are selected in the viewport - **Set Selection** Sets the edit/sculpt selection, on the point, face, or curve domains - **3D Cursor** Gives the location and rotation of the 3D cursor, in the local space of the modified object. - **Face Set** The face set value from mesh sculpt mode, and whether the attribute exists. - **Set Face Set** Set sculpt face set values. In the add menu and search, the nodes are only visible in the "Tool" context of the geometry node editor. They also give errors when executed by a modifier. Pull Request: https://projects.blender.org/blender/blender/pulls/109517
2023-08-04 20:59:04 +02:00
def draw(self, context):
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout = self.layout
layout.menu("NODE_MT_geometry_node_GEO_ATTRIBUTE")
layout.menu("NODE_MT_geometry_node_GEO_INPUT")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_category_GEO_OUTPUT")
layout.separator()
layout.menu("NODE_MT_geometry_node_GEO_GEOMETRY")
layout.separator()
layout.menu("NODE_MT_geometry_node_GEO_CURVE")
Cleanup: Avoid capitals in Geometry Nodes Grease Pencil add menu The capitals were only used for API compatibility when the add menu was first added, they're not needed for new menus. Better to avoid since they're non-standard for menu names.
2025-04-08 09:51:28 -04:00
layout.menu("NODE_MT_geometry_node_grease_pencil")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout.menu("NODE_MT_geometry_node_GEO_INSTANCE")
layout.menu("NODE_MT_geometry_node_GEO_MESH")
layout.menu("NODE_MT_category_GEO_POINT")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_category_GEO_VOLUME")
layout.separator()
Geometry Nodes: add simulation support This adds support for building simulations with geometry nodes. A new `Simulation Input` and `Simulation Output` node allow maintaining a simulation state across multiple frames. Together these two nodes form a `simulation zone` which contains all the nodes that update the simulation state from one frame to the next. A new simulation zone can be added via the menu (`Simulation > Simulation Zone`) or with the node add search. The simulation state contains a geometry by default. However, it is possible to add multiple geometry sockets as well as other socket types. Currently, field inputs are evaluated and stored for the preceding geometry socket in the order that the sockets are shown. Simulation state items can be added by linking one of the empty sockets to something else. In the sidebar, there is a new panel that allows adding, removing and reordering these sockets. The simulation nodes behave as follows: * On the first frame, the inputs of the `Simulation Input` node are evaluated to initialize the simulation state. In later frames these sockets are not evaluated anymore. The `Delta Time` at the first frame is zero, but the simulation zone is still evaluated. * On every next frame, the `Simulation Input` node outputs the simulation state of the previous frame. Nodes in the simulation zone can edit that data in arbitrary ways, also taking into account the `Delta Time`. The new simulation state has to be passed to the `Simulation Output` node where it is cached and forwarded. * On a frame that is already cached or baked, the nodes in the simulation zone are not evaluated, because the `Simulation Output` node can return the previously cached data directly. It is not allowed to connect sockets from inside the simulation zone to the outside without going through the `Simulation Output` node. This is a necessary restriction to make caching and sub-frame interpolation work. Links can go into the simulation zone without problems though. Anonymous attributes are not propagated by the simulation nodes unless they are explicitly stored in the simulation state. This is unfortunate, but currently there is no practical and reliable alternative. The core problem is detecting which anonymous attributes will be required for the simulation and afterwards. While we can detect this for the current evaluation, we can't look into the future in time to see what data will be necessary. We intend to make it easier to explicitly pass data through a simulation in the future, even if the simulation is in a nested node group. There is a new `Simulation Nodes` panel in the physics tab in the properties editor. It allows baking all simulation zones on the selected objects. The baking options are intentially kept at a minimum for this MVP. More features for simulation baking as well as baking in general can be expected to be added separately. All baked data is stored on disk in a folder next to the .blend file. #106937 describes how baking is implemented in more detail. Volumes can not be baked yet and materials are lost during baking for now. Packing the baked data into the .blend file is not yet supported. The timeline indicates which frames are currently cached, baked or cached but invalidated by user-changes. Simulation input and output nodes are internally linked together by their `bNode.identifier` which stays the same even if the node name changes. They are generally added and removed together. However, there are still cases where "dangling" simulation nodes can be created currently. Those generally don't cause harm, but would be nice to avoid this in more cases in the future. Co-authored-by: Hans Goudey <h.goudey@me.com> Co-authored-by: Lukas Tönne <lukas@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/104924
2023-05-03 13:18:51 +02:00
layout.menu("NODE_MT_category_simulation")
layout.separator()
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.menu("NODE_MT_geometry_node_GEO_MATERIAL")
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout.menu("NODE_MT_category_GEO_TEXTURE")
layout.menu("NODE_MT_category_GEO_UTILITIES")
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
layout.separator()
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
layout.menu("NODE_MT_category_GEO_GROUP")
Shading Nodes: Refactor Add menu Refactor the Add menu in Shading nodes, with manually created menus, inspired by Geometry Nodes and more recently the Compositor. Minor sorting adjustments by splitting categories in groups, with separators in between groups, and sorted alphabetically. Shading node group assets are also populated in the menus. This is the first part of the re-organization of the Add menu, part of #111746 Pull Request: https://projects.blender.org/blender/blender/pulls/111798
2023-09-01 20:46:12 +02:00
layout.menu("NODE_MT_category_layout")
Nodes: Add node group assets in add menu This patch builds on the work from bdb57541475f to add node group assets directly in the node editor add menu. Assets are added after separators to distinguish them, but otherwise they look like any other node. The catalog trees from all configured libraries are used to build the menu hierarchy. Only catalogs with matching asset types are used though. There are a few limitations of this initial version. For now this only supports geometry nodes. Support for other built-in node systems just requires some refactoring of the corresponding add menu though. Lazy loading will be added in a followup commit. For now there is a label the first time the menu is opened. Like the search menu integration, re-saving asset library files in 3.4 is required, if it hasn't been done already. Implementation wise, there is a some ugly code here. A lot of that is because the asset system isn't complete. The RNA API doesn't work well yet, and the system isn't built to interact with multiple libraries at once. It's also ugly because of the way we combine automatic menu generation with builtin menus. As noted in a code comment, these two systems could be merged completely so that the menus for builtin nodes are also generated in the same way. Differential Revision: https://developer.blender.org/D16135
2022-11-01 16:09:49 +01:00
node_add_menu.draw_root_assets(layout)
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
classes = (
NODE_MT_geometry_node_add_all,
NODE_MT_geometry_node_GEO_ATTRIBUTE,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_geometry_node_GEO_INPUT,
NODE_MT_geometry_node_GEO_INPUT_CONSTANT,
NODE_MT_geometry_node_GEO_INPUT_GROUP,
NODE_MT_geometry_node_GEO_INPUT_SCENE,
NODE_MT_category_GEO_OUTPUT,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_geometry_node_GEO_CURVE,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_geometry_node_GEO_CURVE_READ,
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
NODE_MT_geometry_node_GEO_CURVE_SAMPLE,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_geometry_node_GEO_CURVE_WRITE,
NODE_MT_geometry_node_GEO_CURVE_OPERATIONS,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_geometry_node_GEO_PRIMITIVES_CURVE,
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
NODE_MT_geometry_node_curve_topology,
Cleanup: Avoid capitals in Geometry Nodes Grease Pencil add menu The capitals were only used for API compatibility when the add menu was first added, they're not needed for new menus. Better to avoid since they're non-standard for menu names.
2025-04-08 09:51:28 -04:00
NODE_MT_geometry_node_grease_pencil,
NODE_MT_geometry_node_grease_pencil_read,
NODE_MT_geometry_node_grease_pencil_write,
NODE_MT_geometry_node_grease_pencil_operations,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_geometry_node_GEO_GEOMETRY,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_geometry_node_GEO_GEOMETRY_READ,
NODE_MT_geometry_node_GEO_GEOMETRY_WRITE,
NODE_MT_geometry_node_GEO_GEOMETRY_OPERATIONS,
NODE_MT_geometry_node_GEO_GEOMETRY_SAMPLE,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_geometry_node_GEO_INSTANCE,
NODE_MT_geometry_node_GEO_MESH,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_geometry_node_GEO_MESH_READ,
Geometry Nodes: Tweak menu location of sample nodes There was an inconsistency between geometry sample nodes and mesh/curve sample nodes, where the latter didn't have a special "Sample" category, and we categorized as "Operations", which they were not. Also put the sample category between "Read" and "Write" since the verb name is more consistent and sampling is an advanced form of reading.
2023-02-03 16:26:30 -05:00
NODE_MT_geometry_node_GEO_MESH_SAMPLE,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_geometry_node_GEO_MESH_WRITE,
NODE_MT_geometry_node_GEO_MESH_OPERATIONS,
NODE_MT_category_GEO_UV,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_category_PRIMITIVES_MESH,
Cleanup: Formatting in geometry nodes add menu Also remove the caps from the new menu idname. That was only done for backwards compatibility with old menu names at some point.
2024-06-10 15:38:43 -04:00
NODE_MT_category_import,
Geometry Nodes: Curve and mesh topology access nodes This patch contains an initial set of nodes to access basic mesh topology information, as explored in T100020. The nodes allow six direct topology mappings for meshes: - **Corner -> Face** The face a corner is in, the index in the face - **Vertex -> Edge** Choose an edge attached to the vertex - **Vertex -> Corner** Choose a corner attached to the vertex - **Corner -> Edge** The next and previous edge at each face corner - **Corner -> Vertex** The vertex associated with a corner - **Corner -> Corner** Offset a corner index within a face And two new topology mappings for curves: - **Curve -> Points** Choose a point within a curve - **Point -> Curve** The curve a point is in, the index in the curve The idea is that some of the 16 possible mesh mappings are more important, and that this is a useful set of nodes to start exploring this area. For mappings with an arbitrary number of connections, we must sort them and use an index to choose a single element, because geometry nodes does not support list fields. Note that the sort index has repeating behavior as it goes over the "Total" number of connections, and negative sort indices choose from the end. Currently which of the "start" elements is used is determined by the field context, so the "Field at Index" and "Interpolate Domain" nodes will be quite important. Also, currently the "Sort Index" inputs are clamped to the number of connections. One important feature that isn't implemented here is using the winding order for the output elements. This can be a separate mode for some of these nodes. It will be optional because of the performance impact. There are several todos for separate commits after this: - Rename "Control Point Neighbors" to be consistent with this naming - Version away the "Vertex Neighbors" node which is fully redundant now - Implement a special case for when no weights are used for performance - De-duplicating some of the sorting logic between the nodes - Improve performance and memory use of topology mappings - Look into caching some of the mappings on meshes Differential Revision: https://developer.blender.org/D16029
2022-09-28 14:38:27 -05:00
NODE_MT_geometry_node_mesh_topology,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_category_GEO_POINT,
Geometry Nodes: add simulation support This adds support for building simulations with geometry nodes. A new `Simulation Input` and `Simulation Output` node allow maintaining a simulation state across multiple frames. Together these two nodes form a `simulation zone` which contains all the nodes that update the simulation state from one frame to the next. A new simulation zone can be added via the menu (`Simulation > Simulation Zone`) or with the node add search. The simulation state contains a geometry by default. However, it is possible to add multiple geometry sockets as well as other socket types. Currently, field inputs are evaluated and stored for the preceding geometry socket in the order that the sockets are shown. Simulation state items can be added by linking one of the empty sockets to something else. In the sidebar, there is a new panel that allows adding, removing and reordering these sockets. The simulation nodes behave as follows: * On the first frame, the inputs of the `Simulation Input` node are evaluated to initialize the simulation state. In later frames these sockets are not evaluated anymore. The `Delta Time` at the first frame is zero, but the simulation zone is still evaluated. * On every next frame, the `Simulation Input` node outputs the simulation state of the previous frame. Nodes in the simulation zone can edit that data in arbitrary ways, also taking into account the `Delta Time`. The new simulation state has to be passed to the `Simulation Output` node where it is cached and forwarded. * On a frame that is already cached or baked, the nodes in the simulation zone are not evaluated, because the `Simulation Output` node can return the previously cached data directly. It is not allowed to connect sockets from inside the simulation zone to the outside without going through the `Simulation Output` node. This is a necessary restriction to make caching and sub-frame interpolation work. Links can go into the simulation zone without problems though. Anonymous attributes are not propagated by the simulation nodes unless they are explicitly stored in the simulation state. This is unfortunate, but currently there is no practical and reliable alternative. The core problem is detecting which anonymous attributes will be required for the simulation and afterwards. While we can detect this for the current evaluation, we can't look into the future in time to see what data will be necessary. We intend to make it easier to explicitly pass data through a simulation in the future, even if the simulation is in a nested node group. There is a new `Simulation Nodes` panel in the physics tab in the properties editor. It allows baking all simulation zones on the selected objects. The baking options are intentially kept at a minimum for this MVP. More features for simulation baking as well as baking in general can be expected to be added separately. All baked data is stored on disk in a folder next to the .blend file. #106937 describes how baking is implemented in more detail. Volumes can not be baked yet and materials are lost during baking for now. Packing the baked data into the .blend file is not yet supported. The timeline indicates which frames are currently cached, baked or cached but invalidated by user-changes. Simulation input and output nodes are internally linked together by their `bNode.identifier` which stays the same even if the node name changes. They are generally added and removed together. However, there are still cases where "dangling" simulation nodes can be created currently. Those generally don't cause harm, but would be nice to avoid this in more cases in the future. Co-authored-by: Hans Goudey <h.goudey@me.com> Co-authored-by: Lukas Tönne <lukas@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/104924
2023-05-03 13:18:51 +02:00
NODE_MT_category_simulation,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_category_GEO_VOLUME,
Geometry Nodes: initial Volume Grid socket support This is the initial implementation for the volume grid sockets that has been discussed during the November 2023 geometry nodes workshop. It adds initial support for passing volume grids around in sockets. Furthermore, it adds two new nodes. Both are initially hidden under the "New Volume Nodes" experimental option until we have a few mode nodes. * **Get Named Grid**: Gets or extracts a volume grid from a volume geometry based on the grid's name. * **Store Named Grid**: Puts a volume grid back into a volume with a name. `SocketValueVariant` is extended to support grids besides single values and fields. Next steps: * Implement grid socket shape and inferencing (currently, they just look like single values). * Add implicit conversions between grid types. * Implement nodes that operate on the grids (#116021). * Improved spreadsheet and viewer support. Links: * https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 * https://devtalk.blender.org/t/2023-11-06-geometry-nodes-workshop-notes/32007#volumes-3 Co-authored-by: Jacques Lucke <jacques@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/115270
2023-12-20 22:33:17 +01:00
NODE_MT_geometry_node_GEO_VOLUME_READ,
Geometry Nodes: Sample grid node This simple node finds the values of a volume grid at positions in the local space used in geometry nodes evaluation. There are three interpolation modes to choose how to mix values between neighboring voxels. For the implementation, first the values are sampled with the grid's type directly, then implicit type conversions are used to get the final type. This makes gives us flexibility in case there aren't exact matches in support between grid types and Blender types. Pull Request: https://projects.blender.org/blender/blender/pulls/118397
2024-02-22 17:58:09 +01:00
NODE_MT_geometry_node_volume_sample,
Geometry Nodes: initial Volume Grid socket support This is the initial implementation for the volume grid sockets that has been discussed during the November 2023 geometry nodes workshop. It adds initial support for passing volume grids around in sockets. Furthermore, it adds two new nodes. Both are initially hidden under the "New Volume Nodes" experimental option until we have a few mode nodes. * **Get Named Grid**: Gets or extracts a volume grid from a volume geometry based on the grid's name. * **Store Named Grid**: Puts a volume grid back into a volume with a name. `SocketValueVariant` is extended to support grids besides single values and fields. Next steps: * Implement grid socket shape and inferencing (currently, they just look like single values). * Add implicit conversions between grid types. * Implement nodes that operate on the grids (#116021). * Improved spreadsheet and viewer support. Links: * https://devtalk.blender.org/t/volumes-in-geometry-nodes-proposal/31917 * https://devtalk.blender.org/t/2023-11-06-geometry-nodes-workshop-notes/32007#volumes-3 Co-authored-by: Jacques Lucke <jacques@blender.org> Pull Request: https://projects.blender.org/blender/blender/pulls/115270
2023-12-20 22:33:17 +01:00
NODE_MT_geometry_node_GEO_VOLUME_WRITE,
NODE_MT_geometry_node_GEO_VOLUME_OPERATIONS,
NODE_MT_geometry_node_GEO_VOLUME_PRIMITIVES,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_geometry_node_GEO_MATERIAL,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_category_GEO_TEXTURE,
NODE_MT_category_GEO_UTILITIES,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_geometry_node_GEO_COLOR,
NODE_MT_category_GEO_TEXT,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_category_GEO_VECTOR,
User Interface: Re-organization of Geometry Nodes Add Node Menu The menus are growing too large. This patches move some categories under sub-menus, and shuffle some entries around. We already had sub-categories split by separators. This change now goes a step further and embrace 3-level menus. Inspired by the "Simpler Add Menu" add-on by Quackers (waiting to hear back to know Quackers real name). Inspired by the "Simpler Add Menu" add-on by Alfonso Martinez II. Differential Revision: https://developer.blender.org/D16993
2023-01-09 18:09:22 +01:00
NODE_MT_category_GEO_UTILITIES_FIELD,
NODE_MT_category_GEO_UTILITIES_MATH,
NODE_MT_category_GEO_UTILITIES_ROTATION,
Geometry Nodes: support attaching gizmos to input values This adds support for attaching gizmos for input values. The goal is to make it easier for users to set input values intuitively in the 3D viewport. We went through multiple different possible designs until we settled on the one implemented here. We picked it for it's flexibility and ease of use when using geometry node assets. The core principle in the design is that **gizmos are attached to existing input values instead of being the input value themselves**. This actually fits the existing concept of gizmos in Blender well, but may be a bit unintutitive in a node setup at first. The attachment is done using links in the node editor. The most basic usage of the node is to link a Value node to the new Linear Gizmo node. This attaches the gizmo to the input value and allows you to change it from the 3D view. The attachment is indicated by the gizmo icon in the sockets which are controlled by a gizmo as well as the back-link (notice the double link) when the gizmo is active. The core principle makes it straight forward to control the same node setup from the 3D view with gizmos, or by manually changing input values, or by driving the input values procedurally. If the input value is controlled indirectly by other inputs, it's often possible to **automatically propagate** the gizmo to the actual input. Backpropagation does not work for all nodes, although more nodes can be supported over time. This patch adds the first three gizmo nodes which cover common use cases: * **Linear Gizmo**: Creates a gizmo that controls a float or integer value using a linear movement of e.g. an arrow in the 3D viewport. * **Dial Gizmo**: Creates a circular gizmo in the 3D viewport that can be rotated to change the attached angle input. * **Transform Gizmo**: Creates a simple gizmo for location, rotation and scale. In the future, more built-in gizmos and potentially the ability for custom gizmos could be added. All gizmo nodes have a **Transform** geometry output. Using it is optional but it is recommended when the gizmo is used to control inputs that affect a geometry. When it is used, Blender will automatically transform the gizmos together with the geometry that they control. To achieve this, the output should be merged with the generated geometry using the *Join Geometry* node. The data contained in *Transform* output is not visible geometry, but just internal information that helps Blender to give a better user experience when using gizmos. The gizmo nodes have a multi-input socket. This allows **controlling multiple values** with the same gizmo. Only a small set of **gizmo shapes** is supported initially. It might be extended in the future but one goal is to give the gizmos used by different node group assets a familiar look and feel. A similar constraint exists for **colors**. Currently, one can choose from a fixed set of colors which can be modified in the theme settings. The set of **visible gizmos** is determined by a multiple factors because it's not really feasible to show all possible gizmos at all times. To see any of the geometry nodes gizmos, the "Active Modifier" option has to be enabled in the "Viewport Gizmos" popover. Then all gizmos are drawn for which at least one of the following is true: * The gizmo controls an input of the active modifier of the active object. * The gizmo controls a value in a selected node in an open node editor. * The gizmo controls a pinned value in an open node editor. Pinning works by clicking the gizmo icon next to the value. Pull Request: https://projects.blender.org/blender/blender/pulls/112677
2024-07-10 16:18:47 +02:00
NODE_MT_geometry_node_GEO_INPUT_GIZMO,
Geometry Nodes: Matrix socket type, attribute type, and initial nodes Implements the design from #116067. The socket type is called "Matrix" but it is often referred to as "Transform" when that's what it is semantically. The attribute type is "4x4 Matrix" since that's a lower level choice. Currently matrix sockets are always passed around internally as `float4x4`, but that can be optimized in the future when smaller types would give the same behavior. A new "Matrix" utilities category has the following set of initial nodes" - **Combine Transform** - **Separate Transform** - **Multiply Matrices** - **Transform Direction** - **Transform Vector** - **Invert Matrix** - **Transpose Matrix** The nodes and socket type are behind an experimental flag for now, which will give us time to make sure it's the right set of initial nodes. The viewer node overlay doesn't support matrices-- they aren't supported for rendering in general. They also aren't supported in the modifier interface currently. But they are supported in the spreadsheet, where the value is displayed in a tooltip. Pull Request: https://projects.blender.org/blender/blender/pulls/116166
2024-02-13 18:59:36 +01:00
NODE_MT_category_utilities_matrix,
Nodes: improve handling of deprecated nodes In 4.1 we deprecate the `Rotate Euler` node in favor of the `Rotate Rotation` node which uses the new rotation socket type. The node is not removed (for now) because that would come with compatibility issues. More generally, we'll likely run into the situation where nodes are deprecated more often in the future, without actually removing them to keep compatibility. This patch improves how such nodes are handled in the UI. The patch does three things: * Adds a new `Utilities > Deprecated` entry in the add node menu in geometry nodes. * Moves search items which are deprecated to the bottom in the search results (currently, this only works in English, can be fixed in bcon3). * Adds a new `bNodeType->deprecation_notice` that will result in a deprecation warning when the node is used. Pull Request: https://projects.blender.org/blender/blender/pulls/117905
2024-02-06 19:08:01 +01:00
NODE_MT_category_GEO_UTILITIES_DEPRECATED,
Nodes: Use plain menus for geometry nodes add menu At the cost of slightly more boilerplate code, we can avoid the `NodeItem` and `NodeCategory` abstractions used to build the node add menu. This makes the menus more flexible and more obvious, which will make them easier to extend with assets. The identifiers for the new menu types are inconsistent with regular class naming for backwards compatibility with the old "category" menu naming. Also adds an item for the "Self Object" node missed in dd5131bd700c. Differential Revision: https://developer.blender.org/D15973
2022-09-26 12:36:13 -05:00
NODE_MT_category_GEO_GROUP,
)
if __name__ == "__main__": # only for live edit.
from bpy.utils import register_class
for cls in classes:
register_class(cls)
Reference in New Issue Copy Permalink