Geometry nodes executes superfluously when the compositor node tree change #99695
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#99695
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40
Blender Version
Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash:
a2d59b2dacWorked: unkown, propably never.
Short description of error
Geometry nodes executes superfluously when the compositor node tree change,
Exact steps for others to reproduce the error
Open the Blend file, go the compositor.
Compositor will freeze for a few seconds.
Whenever a node is changed (e.g. connected or disconnected) the compositor will freeze again for a few seconds.
This only happens when the mesh is very high dense. With low meshes performance of the compositor is not affacted.
In a real world scenario this issue may freeze my compositor up to 60 sec, which makes the compositing pretty impossible.
Thank you @BD3D for simplifying the example file.
slow com.blend
blender_lR6vm6l3QC.mp4
Added subscribers: @BD3D, @Rincewind3D-1
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
The freeze is just Blender computing the Geometry Nodes modifier. So I guess the issue is the fact that Geometry Nodes executes superfluously when the compositor change. All node systems seems to call the same update mechanism, and the updates are likely not granular enough, so this might just be a know limitation. Tagging the module for more information.
ObjectInfo/CollectionInfo nodes creates dependencies freeze in the compositor previewto Geometry nodes executes superfluously when the compositor node tree changeYeah, this is what I also guessed.
But the geometry nodes itself are not affacted by the freeze, only the compositor nodes (but caused by the geometry nodes).
Added subscriber: @JacquesLucke
Looks like this has been fixed by
0dcee6a386, although I'm not quite sure how.Can you try again?
Hello,
just checked the latest Blender Alpha ( July 23, 02:37:47 -
82467e5dcf).First it looked like as it was fixed. The test file I uploaded had a fast compositor in 3.3 Alpha.
But than I checked a real world file and the compositor was still extremly slow (sadly I can't share this real world project file).
Than I checked in the 3.3 Alpha the geo nodes and regocnized that in the geo node itself is an error now, which was not in 3.2.
I guess that it's not fixed. I think 3.3 added a regression bug, which broke the geo node in my test file I uploaded here and that's why my test file is fast in the current 3.3 alpha.
The bug in the Store Named Attribute node is from yesterday. I comitted a fix for that today already.
ok, I will check the build tomorrow.
Ok, checked it with todays build.
The demo file is still fast and the Stored Named Attribtute regression bug is fixed.
My original real-world blender file has still a super slow compositor.
Conclusion: This specific bug is fixed, but there seems to be more mysterious circumstances where geometry nodes can slow down the compositor.
If I delete in my original blender file (which I can't sadly not share here) all geometry nodes, the compositor is fast again.
Changed status from 'Needs Developer To Reproduce' to: 'Needs Triage'
Changed status from 'Needs Triage' to: 'Needs User Info'
Without a way to reproduce it, it's not something we can fix unfortunately.
Can only recommend you to remove all unrelated stuff from the file and to replace the remaining stuff with dummy objects. Otherwise there is nothing we can do here.
Changed status from 'Needs User Info' to: 'Archived'
Since the original issue is fixed, I will archive this for now. As for the other issue, can you submit a new report with the remaining issue after simplifying the file as much as possible as suggested?