Extremely Long time delay using geometry nodes with simple mesh boolean node 37706ms #98020
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#98020
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-5.13.0-41-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.2.6
Blender Version
Broken: version: 3.2.0 Beta, branch: master, commit date: 2022-05-10 06:30, hash:
11aa237858Worked: (newest version of Blender that worked as expected)
Short description of error
Extremely Long time delay using geometry nodes with simple mesh boolean node and difference (it takes 37706ms for the mesh boolean node to do a cylinder difference)
Exact steps for others to reproduce the error
I've included the blend file which shows the times when you change the item to do a boolean difference 1 cylinder/count to 2 cylinder/count.
When I use the Boolean Modifier this time lag doesn't occur. I've included this in the blend file for testing also.
PS: this time lag also occurs in Blender 3.1.2
prego lid gn.blend.zip
Added subscriber: @Still
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
This looks unreasonable indeed especially when compared to the modifier which I guess do the same thing. But the performance analysis seems normal as far as I can see, so tagging the module for more information.
Added subscriber: @AntonioPuentes
Maybe the boolean is being computed once per instance. Putting a relize instances node is only computed on a single mesh.
@AntonioPuentes But there are only two instances and a boolean modifier with two cylinders is also very fast. So why would the node take orders of magnitude higher execution time?
My fault, it seems that with relize instance node, the boolean is not being calculated correctly.
{F13072093}
Probably the problem is with the geometry connected to the input "Mesh 1". The boolean node is calculating the difference of the geometry connected to the input socket "Mesh 1"
There is ongoing work to implement a faster boolean: #114476
Also the "fast/non-exact" boolean mode should be exposed in the node in 4.2.
But the performance of the current boolean exact mode is expected, it can often be quite bad.