Geometry Nodegroup stopped updating the viewport #85511
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#85511
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.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71
Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-02-08 23:42, hash:
eab9165c25Hello, suddenly, for no reasons, my .blend stopped updating my viewport when I change values in my geometry node set up
it's really strange, the viewports seems to update independently from each others
Exact steps for others to reproduce the error
see gif,
in the file below,
play with values,
workflow.blend
Added subscriber: @dodododorian
#86651 was marked as duplicate of this issue
Added subscriber: @HooglyBoogly
~~It seem that unpinning the and re-pinning solved the issue, ~~
(currently pinned geonode stored in "Scatter Object" sorry for the ton of empties in the scene)
edit1*No it didn't, this is still happening and I'm stuck with this .blend
I guess I'll have to move everything in a non-broken .blendedit2*Moving the node set up elsewhere didn't work too. so the geonode set up may be faulty? why would it be the case?
Geometry node stopped updating the viewport in specific .blendto Geometry Nodegroup stopped updating the viewportAfter deleting nodes one by one
The phenomenon is still occurring
Let me know if you guys need more "simple" node set up to identify the problem, but it seems that one node in particular is not creating this issue (?)
Additional video footage of the problem
ezgif.com-gif-maker.mp4
Added subscriber: @JacquesLucke
Changed status from 'Needs Triage' to: 'Confirmed'
Looks like
node_connected_to_outputis returning the wrong result. Making it always return true seems to solve the issue.For some reason your Group Output node is not tagged as "the output" anymore. Do you have any idea of how that might have happened? Maybe you deleted the original group output node, or copied it or something else?
Fixing the issue in your file is quite straight forward. You just have to select the Group Output node once (make it active) and then you can proceed working as normal.
Added subscriber: @randum
Added subscriber: @Robotica
FYI, I just ran into this problem on 2.9.3 and wasn't sure what the issue was. The only way I could see the update was to reconnect the group outputs input, but your suggestion fixed it for me. In my case I deleted the original group output by accident and rather than undoing I just added a new one.
This issue was referenced by
58818cba40Changed status from 'Confirmed' to: 'Resolved'