Accumulate Node doesn't work with Points node #100945

Open
opened 2022-09-09 14:40:34 +02:00 by Erindale · 11 comments

System Information
Operating system: Windows-10-10.0.18363-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77

Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce
Worked: (newest version of Blender that worked as expected)

Short description of error
The Position socket of Points node doesn't seem to register positions if the vector is coming from an Accumulate field node.

Exact steps for others to reproduce the error
Add accumulate field node to sum a random value node.
Plug this into the Points' Position socket.

image.png

**System Information** Operating system: Windows-10-10.0.18363-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77 **Blender Version** Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: `0759f671ce` Worked: (newest version of Blender that worked as expected) **Short description of error** The Position socket of Points node doesn't seem to register positions if the vector is coming from an Accumulate field node. **Exact steps for others to reproduce the error** Add accumulate field node to sum a random value node. Plug this into the Points' Position socket. ![image.png](https://archive.blender.org/developer/F13472463/image.png)
Author

Added subscriber: @Erindale

Added subscriber: @Erindale

#100944 was marked as duplicate of this issue

#100944 was marked as duplicate of this issue

Added subscriber: @mod_moder

Added subscriber: @mod_moder

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'

Yes, it won't work.
The point node creates a new context that does not match the context of other nodes.
Let's just say that other nodes either get a context (which has a geometry component) or are computed for context values.
The point node and the volume node in the cube will create their own context but without the component (as an optimization). For this reason, you can only compute in them like math or translation, but not process like accumulation, domain interpolation, or smooth attribute

Yes, it won't work. The point node creates a new context that does not match the context of other nodes. Let's just say that other nodes either get a context (which has a geometry component) or are computed for context values. The point node and the volume node in the cube will create their own context but without the component (as an optimization). For this reason, you can only compute in them like math or translation, but not process like accumulation, domain interpolation, or smooth attribute
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Author

In #100945#1414609, @mod_moder wrote:
Yes, it won't work.

Things like this need to have some kind of notice to the artist. Tools can't just not work intentionally 😅
Why not have a backup process for things like this so it behaves as expected even if it's a temporary solution like internalising a set position node after point generation?

> In #100945#1414609, @mod_moder wrote: > Yes, it won't work. Things like this need to have some kind of notice to the artist. Tools can't just not work intentionally 😅 Why not have a backup process for things like this so it behaves as expected even if it's a temporary solution like internalising a set position node after point generation?
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'
Member

Think it's a bit premature to close this without more discussion.
I'm not sure that we would also implement the accumulate node for this field context, but at least we should explicitly decide not to.

For the volume cube I don't think we would, but the points node is a bit different because it still has an order.

Think it's a bit premature to close this without more discussion. I'm not sure that we would also implement the accumulate node for this field context, but at least we should explicitly decide not to. For the volume cube I don't think we would, but the points node is a bit different because it still has an order.

The message system for entering a field is not the appropriate context suitable? #94039

The message system for entering a field is not the appropriate context suitable? #94039
Philipp Oeser removed the
Interest
Nodes & Physics
label 2023-02-10 08:43:45 +01:00
Sign in to join this conversation.
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
5 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#100945
No description provided.