Maniphest T67260

Booleans still process even while hidden
Closed, Archived
Actions

Assigned To
Brecht Van Lommel (brecht)
Authored By
Youssef Abusamra (DoofusPoopface)
Jul 19 2019, 10:01 PM
Tags
  • BF Blender
Subscribers
Brecht Van Lommel (brecht)
ronan ducluzeau (zeauro)
Youssef Abusamra (DoofusPoopface)

Description

System Information
Operating system: Windows 10
Graphics card: AMD R7 250

Blender Version
Broken: blender-2.80rc2-windows64
Worked: (optional)

When an object1 has boolean modifier that is difference with object2, if the modifier visibility is disabled for performance reasons, it still lags while editing object 2, in my case the modifier has to be removed and added again.

add cube1 and add a subdivision modifier
add another cube2, add boolean to cube 1 difference set to cube 2
increasing subdivision on cube 1 and 2 until editing cube 2 becomes extremely laggy because of the boolean modifier
hide the boolean modifier and it'll still be extremely laggy, modifier has to be completely removed.

bug.blend603 KBDownload

Event Timeline

Youssef Abusamra (DoofusPoopface) created this task.Jul 19 2019, 10:01 PM
ronan ducluzeau (zeauro) added a subscriber: ronan ducluzeau (zeauro).Jul 20 2019, 7:07 PM

To me, it looks like problem is rather relative to polycount.
Your .blend file is laggy but scene info indicates a polycount that reach 1 242 762 tris.
If I disable use of second subdivision modifier on Cube object, only 79 410 tris are displayed and editing Cube.001 is a lot faster.

Youssef Abusamra (DoofusPoopface) added a comment.Jul 22 2019, 12:20 AM
In T67260#728752, @ronan ducluzeau (zeauro) wrote:

To me, it looks like problem is rather relative to polycount.
Your .blend file is laggy but scene info indicates a polycount that reach 1 242 762 tris.
If I disable use of second subdivision modifier on Cube object, only 79 410 tris are displayed and editing Cube.001 is a lot faster.

Try removing the boolean modifier and it works fast
I just tried in 2.79b and this wasn't an issue, disabling the boolean fixed it without having to remove the whole modifier

Brecht Van Lommel (brecht) changed the task status from Unknown Status to Unknown Status.Jul 22 2019, 4:37 PM
Brecht Van Lommel (brecht) claimed this task.
Brecht Van Lommel (brecht) added a subscriber: Brecht Van Lommel (brecht).

This is a known limitation of visibility settings for now, use other ones to speed up scene evaluation.
https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Layers#Visibility