Geometry Nodes Crash #86172
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#86172
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: Linux-4.15.0-136-generic-x86_64-with-debian-buster-sid 64 Bits [Ubuntu 18.04.5]
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04
Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash:
02948a2cabWorked: (newest version of Blender that worked as expected)
Short description of error
Exact steps for others to reproduce the error
Open my file and try what I described above.
Screencast-2021-03-02_01.28.08.mp4
Screencast-2021-03-02_01.28.58.mp4
GeoNodes_Crash.blend
GeoNodes_Crash.crash.txt
Added subscriber: @viadvena
Added subscriber: @HooglyBoogly
Changed status from 'Needs Triage' to: 'Confirmed'
Thanks for the report, I can confirm this.
This issue was referenced by
f094b4fa08Changed status from 'Confirmed' to: 'Resolved'
Changed status from 'Resolved' to: 'Confirmed'
The commit above only fixed one of the issues. The copy issue still exist.
Next time, please report bugs separately.
@JacquesLucke Ok, thank you for support. I just thought this way will be more optimized for tracker.
The copy-issue seems to be depsgraph related. The issue is that the collections are disabled. However, we are still using the disabled collections from geometry nodes. I'm not yet sure how to solve this exactly.
Enabling the collections, fixes the crash in this file.
I would think a disabled collection should be empty to geometry nodes.
Issue is, I'm not quite sure what's the correct way to detect if a collection is disabled. Seems like the disabled status is not stored in the collection but in
LayerCollection. Also, a collection instance still works when the collection is disabled, so I don't think that would be the correct fix here.The solution should probably be to create all the depsgraph nodes for the objects in the collection, have to investigate how to do that a bit more.
No. It would break whole workflow. For example, when we using particles with instances it would be strange if we see big source model of instance in the middle of the screen. These meta objects should to have options to hide from all screens and all view layers, and to have way to use them from other scenes but it shouldn't touch their instances. Instances switching always was in the places where their was assigned. Actually how it was always works in Blender concept.
This issue was referenced by
a988099ee4Changed status from 'Confirmed' to: 'Resolved'