Geometry Node : Added Object attribute nodes #120745

Open
Flo_12344 wants to merge 3 commits from Flo_12344/blender:main into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
First-time contributor

A Geometry node that help accessing data from different object without the need of using drivers, (light/camera/mesh at the moment), by copy the data path of their different options. (the original idea come from Cartesian Caramel)

image

A Geometry node that help accessing data from different object without the need of using drivers, (light/camera/mesh at the moment), by copy the data path of their different options. (the original idea come from Cartesian Caramel) ![image](/attachments/4bcb4dee-c254-442f-b0c5-df56b548044c)
Flo_12344 added 1 commit 2024-04-17 17:02:04 +02:00
Iliya Katushenock added this to the Nodes & Physics project 2024-04-17 17:08:24 +02:00
Iliya Katushenock added the
Interest
Geometry Nodes
label 2024-04-17 17:08:27 +02:00

Thanks for Pull Request. How do you planned to build dependency graph relations for used ID?

Thanks for Pull Request. How do you planned to build dependency graph relations for used ID?
Author
First-time contributor

Sorry, I feel like I'm going to be a bit annoying but what do you mean ?

Sorry, I feel like I'm going to be a bit annoying but what do you mean ?

Blender build graph of object relations to evaluate all modifiers/properties with animations/drivers/load all data/apply constraints/...
Each object is represented as set of components with separate operations to do.
And if you planned to get access to user to any component of any object what is linked to modifier, how do you planned to build relations?

Blender build graph of object relations to evaluate all modifiers/properties with animations/drivers/load all data/apply constraints/... Each object is represented as set of components with separate operations to do. And if you planned to get access to user to any component of any object what is linked to modifier, how do you planned to build relations?
Author
First-time contributor

At the moment the node retrieve the object data using the rna access.

At the moment the node retrieve the object data using the rna access.
Flo_12344 added 1 commit 2024-04-17 18:40:06 +02:00

At the moment the node retrieve the object data using the rna access.

Okay, so, this even not work with animated properties (if this is that you mean).

Current feedback:

  1. There is no way to versioning node groups with this node. In case python API will be changed, there is no way to handle this for geometry nodes. Users never like that they geometry nodes do change result in new version of blender.
  2. Assets. There is no way to handle linking of custom properties in such way.
  3. This increate dependency fishnet.I'd name this like state if we have to increase dependencies for all linked object due to lack of static info about kind of dependency. Even if access if happen to not COW objects, i think, this still require at least access to COW cope of objects in memory racer to real data.
  4. This is overkill for usually geometry nodes. If quote the review from the chat: We should focus on more user friendly ways to expose data to geometry nodes.
  5. There is some issues with raw access to RNA values from geometry nodes, currently we have inconsistency of quaternion normalization.
  6. This can provide access to things that is should not be done as it. For example, with this you can read separate vertex position of the mesh. This is not the thing that should be accepted.
> At the moment the node retrieve the object data using the rna access. Okay, so, this even not work with animated properties (if this is that you mean). Current feedback: 1. There is no way to versioning node groups with this node. In case python API will be changed, there is no way to handle this for geometry nodes. Users never like that they geometry nodes do change result in new version of blender. 2. Assets. There is no way to handle linking of custom properties in such way. 3. This increate dependency fishnet.I'd name this like state if we have to increase dependencies for all linked object due to lack of static info about kind of dependency. Even if access if happen to not COW objects, i think, this still require at least access to COW cope of objects in memory racer to real data. 4. This is overkill for usually geometry nodes. If quote the review from the chat: `We should focus on more user friendly ways to expose data to geometry nodes`. 5. There is some issues with raw access to RNA values from geometry nodes, currently we have inconsistency of quaternion normalization. 6. This can provide access to things that is should not be done as it. For example, with this you can read separate vertex position of the mesh. This is not the thing that should be accepted.
Author
First-time contributor

It worked fine with animated properties in my tests rotation_euler,rotation_quaternion and location or at least those one works fine and the ones that have deps graph issue using driver works the same way with this method.
I didn't though it was overkill I just though of what I needed when working on some of my projects and tried to access the data for wich I needed drivers to make them easier to maintain by just copying the data path of the properties.
With this method I haven't managed to access the vertex position sadly even if it's something that I have tried at first.
It would be interesting if you have an idea of the things that makes it unusable for versioning so I could try to fix them.
If you want, I can provide a build with it for testing.
Thanks for your feedback.

It worked fine with animated properties in my tests rotation_euler,rotation_quaternion and location or at least those one works fine and the ones that have deps graph issue using driver works the same way with this method. I didn't though it was overkill I just though of what I needed when working on some of my projects and tried to access the data for wich I needed drivers to make them easier to maintain by just copying the data path of the properties. With this method I haven't managed to access the vertex position sadly even if it's something that I have tried at first. It would be interesting if you have an idea of the things that makes it unusable for versioning so I could try to fix them. If you want, I can provide a build with it for testing. Thanks for your feedback.
Flo_12344 added 1 commit 2024-04-20 11:43:37 +02:00
This pull request has changes conflicting with the target branch.
  • scripts/startup/bl_ui/node_add_menu_geometry.py
  • source/blender/nodes/geometry/CMakeLists.txt

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u main:Flo_12344-main
git checkout Flo_12344-main
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 Assignees
2 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#120745
No description provided.