WIP: Geometry Nodes: new For-Each zone #112446

Draft
Jacques Lucke wants to merge 51 commits from JacquesLucke/blender:for-each-zone into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
Member

This patch currently only contains some initial ui boilerplate for the new zone type. It's not functional yet.

image

This patch currently only contains some initial ui boilerplate for the new zone type. It's not functional yet. ![image](/attachments/36a1431b-93bb-455d-af63-12617e235476)
Jacques Lucke added 1 commit 2023-09-16 14:49:39 +02:00
Jacques Lucke added 3 commits 2023-09-20 14:59:33 +02:00
Jacques Lucke added 3 commits 2023-09-20 18:12:02 +02:00
Jacques Lucke added 2 commits 2023-09-20 18:26:37 +02:00
Jacques Lucke added 6 commits 2023-09-30 22:10:48 +02:00
Jacques Lucke added 1 commit 2023-09-30 22:56:06 +02:00
Jacques Lucke added 2 commits 2023-10-04 11:44:52 +02:00
Jacques Lucke added 6 commits 2023-10-04 15:11:15 +02:00
Jacques Lucke added 3 commits 2023-10-04 16:20:03 +02:00
Jacques Lucke added 5 commits 2023-10-04 19:17:03 +02:00
Jacques Lucke added 4 commits 2023-10-06 18:26:04 +02:00
Jacques Lucke added 5 commits 2023-10-06 19:30:08 +02:00
Jacques Lucke added 4 commits 2023-10-07 00:53:42 +02:00
Jacques Lucke added 1 commit 2023-10-07 23:32:52 +02:00
Jacques Lucke added 5 commits 2023-10-08 16:58:48 +02:00
First-time contributor

what about Iliya's proposal #112456 ?
I think that is a better implementation (or al least a necessary one in addition).

most the time I need that (#112456) type of 'for each zone', and it could handle this proposal's behavior aswell, but this proposal's behavior can't replicate Ilya's proposal's behavior.

edit:
though it is unclear what Ilya meant. for example how would you set the iteration amount? also, us the rest of the geometry accessible, or only what is in the group?

I'd propose having a for each zone modeled after the duplicate elements node. the iteration amount would be a field tied to the geometry element.
Admittedly this for focused on doing data operations more than geometry operation. hmm... so perhaps have it both. you have the group ID and an iteration amount that is per group and without a group ID it could default per element (like vertex, face, etc.), or to one group.

what about Iliya's proposal #112456 ? I think that is a better implementation (or al least a necessary one in addition). most the time I need that (#112456) type of 'for each zone', and it could handle this proposal's behavior aswell, but this proposal's behavior can't replicate Ilya's proposal's behavior. edit: though it is unclear what Ilya meant. for example how would you set the iteration amount? also, us the rest of the geometry accessible, or only what is in the group? I'd propose having a for each zone modeled after the `duplicate elements` node. the iteration amount would be a field tied to the geometry element. Admittedly this for focused on doing data operations more than geometry operation. hmm... so perhaps have it both. you have the group ID and an iteration amount that is per group and without a group ID it could default per element (like vertex, face, etc.), or to one group.
First-time contributor

Any update about this stuff ?

Any update about this stuff ?
This pull request has changes conflicting with the target branch.
  • scripts/startup/bl_operators/geometry_nodes.py
  • scripts/startup/bl_ui/space_node.py
  • source/blender/blenkernel/BKE_compute_contexts.hh
  • source/blender/blenkernel/BKE_node.h
  • source/blender/blenkernel/BKE_viewer_path.h
  • source/blender/blenkernel/intern/compute_contexts.cc
  • source/blender/blenkernel/intern/node.cc
  • source/blender/blenkernel/intern/node_tree_update.cc
  • source/blender/blenloader/intern/versioning_userdef.cc
  • source/blender/makesdna/DNA_node_types.h

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u for-each-zone:JacquesLucke-for-each-zone
git checkout JacquesLucke-for-each-zone
Sign in to join this conversation.
No reviewers
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#112446
No description provided.