"Object Info" node forces entire modifier stack to be reevaluated on any transform. #107227
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#107227
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: Hydrurga Australis Snack Pack (Linux, Arch-based)
Graphics card: Intel
Blender Version
Broken: At least 3.4.1, 3.5.0.
Worked: Unknown. Presumably never.
Short description of error
If you have an "Object Info" node in any geometry nodetree on an object, then the all of the object's entire nodetrees and modifiers are reevaluated whenever you move the object, even if the Object Info node isn't connected to anything and isn't ever used, even if the Geometry Nodes modifier the "Object Info" node is on is disabled, and even for nodetrees/modifiers that are earlier in the modifier stack than the Object Info node.
Exact steps for others to reproduce the error
Reevaluation of preceding geometry nodes:
Reevaluation of preceding modfiers:
The "Expensive Nodetree" nodegroup contains a variety of different inputs in order to illustrate that object transform usually does not trigger modifier reevaluations for other geometry node input types.
Hello, thanks for the report, but it's not a bug the way it works now.
It seems like an error in the way the depsgraph is handled— Isn't it somewhat cyclical, since modifiers early in the stack are affected by something that should come after them in the depsgraph?
If you created a node and specified an object in it, there should always be a dependency.
We can't tell if a node is being used without doing a full calculation of the entire node tree. This is a related issue (it needs some editing): #102881
The requirement for a complete calculation applies not only to the geometry, but also to the position of object.
And while the modifier is there, it dependencies are created. This means that the object itself has these dependencies, and will be re-evaluated with their tag.
I understand. Thank you a lot for the in-depth explanation— I was under the mistaken impression that the object was cached in between modifiers, which in retrospect is clearly not the case.