Boolean modifier still processed when bypassed (when using Animated Booleans) #53942
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#53942
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
Windows 8.1 Home 64 bit
Nvidia Geforce GTX 970
Intel Core i7-5930K CPU @ 3.5 GHz
32 GB RAM
Blender Version
Broken: (2.79
5bd8ac9
)Short description of error
So this might be a known issue/limitation that will be fixed in 2.8, but in 2.79, I've noticed that having a boolean modifier completely disabled (no render, no preview) still runs in the background when its target is an animated object. This actually more than halves the playback framerate of the 3D window. If the modifier has no target, or the object is non-animated, framerate is fine.
Thanks for your time in reading this. Please let me know if there's a known workaround for this, or if this is already something of the past with the new dependency graph of 2.8 (I have not tried the 2.8 builds yet).
Added subscriber: @AdamJanz
Added subscriber: @zeauro
Please share maximum pieces of information.
How did you notice that ? Can you share measures of the issue ? Does it happen when blender is launched with --enable-new-depsgraph comand ?
Please upload a simple .blend demonstrating problematic behaviour.
Thanks Ronan;
Interestingly, in the test project I wasn't able to trigger the excessively slow behavior from the animated boolean object until after I added two 16 vertex circles into the plane object. There is very poor playback even with no Boolean modifier on the object. In my original project, though, removing the boolean modifier made things run smoothly even with those 2 circles (however there was only 1515 items in the array vs 1800). It seems as the array decreases, framerate increases, so it must be the array modifier that is making the biggest hit, and in the original project the bypassed boolean modifier was just pushing it over the edge. It seems strange considering the system specs it's running on (6 core, 32 GB ram, GTX 970). Here is the test file:
BooleanTEST.blend
Thanks for your time.
Changed status from 'Open' to: 'Archived'
This is no more an issue with boolean modifier but it turns into a feature request about array modifier performances.
We could resume it as "At a count above 1000 duplicates, array modifier becomes slow."
Of course, better performances of viewport and modifiers are a target for 2.8 release.
But it is not necessary to keep a reminder about a threshold value to expect developers to try to repel it.
So, I am closing the report.
Array modifier was not initially designed to handle as many duplicates as particles.
Here, it generates an heavy mesh of almost 120 000 virtual faces. At this amount, it is generally welcomed to apply modifier.
You can make an incremental save of your .blend file before applying modifier or copy your object, disable its modifiers and move duplicate to an unused layer.
If array modifier is applied and boolean modifier disabled, frame rate is at its maximum with current master.
If you absolutely need to see animation of gap in path, you can also be more efficient by using beveled/taper curves rather than this Array+Curve+Boolean solution.
https://docs.blender.org/manual/en/dev/modeling/curves/properties/geometry.html#bevel
The better workflow to handle modifiers limitations is a general support issue and not a software error we can investigate.
For general issues, check on support sites such as:
If you still think you have found a bug, please give exact steps to redo the error.
Thanks Ronan for the info and the link about curves.
The test file I submitted was in an attempt to recreate the slowdown as I had first encountered it in my original project. However, in my original project, I am now using an animated material rather than a Boolean modifier to accomplish the effect I need, which works great. The report about the bypassed boolean modifier reducing the frame rate by 50% with 1515 duplicates but when it has no target the frame rate is 100% (even with 1515 duplicates) still stands true in my original project. So yes, the array modifier is generating many faces but the boolean modifier is still incorrectly contributing even when bypassed. It is unfortunate the smaller scale test project I submitted did not reveal this issue.
However, in the future, should I ever need to use a boolean specifically in this way, I will apply the array modifier if it slowing things down.
Thank you again.