Boolean Operation is slowing down objects transformations even it it's disabled in the Modifier Panel #40426

New Issue

Vitor Balbio · 2014-05-29T17:25:28+02:00

Vitor Balbio commented

2014-05-29 17:25:28 +02:00

System Information
Win7 x64

Blender Version
f5055d8

Short description of error
if you have a boolean modifier applyied between high poly objects it's ok that it is slow to update so when you move/rotate/scale it we got some lag, but it happens too even if the object is disabled for the realtime 3dview and the render in the modifier panel. We should't have a check for that for true disable this object in the Boolean Operator?

Exact steps for others to reproduce the error
In this demo we have a result object , a high poly sphere and a low poly cube both applyied as a boolean modifier difference.
The sphere is turning the result a high poly and is slow to move it in the viewport, it's ok since it is a hgh poly mesh applying a boolean operation.
But the modifier that apply the boolean operation for the Cube is disabled for the viewport and the render, but even with this it's slow to move too as if it's applying the boolean operation, but it's not.

There's no change if the Boolean of the cube is in the top of in the bottom of the stack too. It's lag at the same way.
Bug.blend

**System Information** Win7 x64 **Blender Version** f5055d8 **Short description of error** if you have a boolean modifier applyied between high poly objects it's ok that it is slow to update so when you move/rotate/scale it we got some lag, but it happens too even if the object is disabled for the realtime 3dview and the render in the modifier panel. We should't have a check for that for true disable this object in the Boolean Operator? **Exact steps for others to reproduce the error** In this demo we have a result object , a high poly sphere and a low poly cube both applyied as a boolean modifier difference. The sphere is turning the result a high poly and is slow to move it in the viewport, it's ok since it is a hgh poly mesh applying a boolean operation. But the modifier that apply the boolean operation for the Cube is disabled for the viewport and the render, but even with this it's slow to move too as if it's applying the boolean operation, but it's not. There's no change if the Boolean of the cube is in the top of in the bottom of the stack too. It's lag at the same way. [Bug.blend](https://archive.blender.org/developer/F91850/Bug.blend)

Vitor Balbio commented

2014-05-29 17:25:28 +02:00

Changed status to: 'Open'

Vitor Balbio commented

2014-05-29 17:25:28 +02:00

Added subscriber: @vitorbalbio-3

Sergey Sharybin commented

2014-05-30 10:55:25 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2014-05-30 10:55:25 +02:00

Sergey Sharybin self-assigned this 2014-05-30 10:55:25 +02:00

Sergey Sharybin commented

2014-05-30 10:55:25 +02:00

Added subscriber: @LukasTonne

Sergey Sharybin commented

2014-05-30 10:55:25 +02:00

This is a design limitation of dependency graph, which doesn't check on whether modifier is enabled or disabled when building the dependencies. Perhaps could be solved as a major dependency graph re-work project.

@LukasTonne, think you would want to keep your radar here :)

Thanks for the report, but not considered a bug.

This is a design limitation of dependency graph, which doesn't check on whether modifier is enabled or disabled when building the dependencies. Perhaps could be solved as a major dependency graph re-work project. @LukasTonne, think you would want to keep your radar here :) Thanks for the report, but not considered a bug.

Lukas Tönne commented

2014-05-30 11:12:15 +02:00

It seems that in this case the unnecessary updates by the depsgraph could well be avoided in principle. When the modifier is disabled the depsgraph should treat it as if it didn't exist, i.e. not call the updateDepgraph callbacks in such modifiers at all:

https://developer.blender.org/diffusion/B/browse/master/source/blender/blenkernel/intern/depsgraph.c$574

We have to be a bit careful with this though, there are lots of hacks that can make the depsgraph react to such a change in unexpected ways.

Also note that it is quite easy to produce only slightly more complicated cases where the data->data dependency of the boolean modifier is still created, due to lack of granularity in the depsgraph (e.g. a later modifier that is much simpler but also uses the cube's geometry would force the boolean modifier to update too). These issues would only be solved with the depsgraph refactoring.

Overall this is not strictly speaking a bug, but worth investigating, since there is a straightforward solution at least in theory.

It seems that in this case the unnecessary updates by the depsgraph could well be avoided in principle. When the modifier is disabled the depsgraph should treat it as if it didn't exist, i.e. not call the `updateDepgraph` callbacks in such modifiers at all: https://developer.blender.org/diffusion/B/browse/master/source/blender/blenkernel/intern/depsgraph.c$574 We have to be a bit careful with this though, there are lots of hacks that can make the depsgraph react to such a change in unexpected ways. Also note that it is quite easy to produce only slightly more complicated cases where the data->data dependency of the boolean modifier is still created, due to lack of granularity in the depsgraph (e.g. a later modifier that is much simpler but also uses the cube's geometry would force the boolean modifier to update too). These issues would only be solved with the depsgraph refactoring. Overall this is not strictly speaking a bug, but worth investigating, since there is a straightforward solution at least in theory.

Lukas Tönne commented

2014-05-30 11:18:40 +02:00

Added subscriber: @Sergey

Lukas Tönne commented

2014-05-30 11:18:40 +02:00

Correction: @Sergey noted that we don't have a distinction in the depsgraph of render/viewport/preview/baking context etc. yet, so unfortunately we can't selectively disable these dependencies :S

Has to stay a todo until depsgraph refactor ...

Correction: @Sergey noted that we don't have a distinction in the depsgraph of render/viewport/preview/baking context etc. yet, so unfortunately we can't selectively disable these dependencies :S Has to stay a todo until depsgraph refactor ...

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Boolean Operation is slowing down objects transformations even it it's disabled in the Modifier Panel #40426