Boolean modifier performance issues #86236

New Issue

Dmitry · 2021-03-03T17:35:28+01:00

Dmitry commented

2021-03-03 17:35:28 +01:00

System Information
Operating system: Windows 10
Graphics card: AMD RX 580

Blender Version
Broken: 2.92.0
Worked: 2.83.12
Short description of error
When i use booleans and want to adjust it's position, it causes heavy lags in viewport in 2.9x. But in 2.83.12 it moves smoothly.
Seems like 2.9x versions are CPU heavy

Exact steps for others to reproduce the error
Open default scene, create cylinder, add "array" modifier, use difference boolean on default cube and try to move cylinder in any direction

There is .blend file already with boolean modifier

boolean test.blend

**System Information** Operating system: Windows 10 Graphics card: AMD RX 580 **Blender Version** Broken: 2.92.0 Worked: 2.83.12 **Short description of error** When i use booleans and want to adjust it's position, it causes heavy lags in viewport in 2.9x. But in 2.83.12 it moves smoothly. Seems like 2.9x versions are CPU heavy **Exact steps for others to reproduce the error** Open default scene, create cylinder, add "array" modifier, use difference boolean on default cube and try to move cylinder in any direction There is .blend file already with boolean modifier [boolean test.blend](https://archive.blender.org/developer/F9862792/boolean_test.blend)

Dmitry commented

2021-03-03 17:35:28 +01:00

Added subscriber: @PRAYTHEPO

Dmitry commented

2021-03-04 06:56:21 +01:00

One thing to mention: to replicate this performance bug you need to create scene with boolean individually for each version of blender. If you create boolean scene in 2.83.12 and then open in 2.9x, it works fine. But boolean operation created in 2.9x works bad and laggy by itself and imported to 2.83.12 it also works ugly

Falk David commented

2021-03-04 10:18:39 +01:00

Added subscriber: @filedescriptor

Falk David commented

2021-03-04 10:18:39 +01:00

Changed status from 'Needs Triage' to: 'Archived'

Falk David closed this issue

2021-03-04 10:18:39 +01:00

Falk David commented

2021-03-04 10:18:39 +01:00

Since 2.91 Blender has a new solver for booleans called Exact. This solver can solve trickier cases but is also slower. The old method is still available as the Fast solver. Read more here: https://wiki.blender.org/wiki/Reference/Release_Notes/2.91/Modeling#Boolean.

When you use the boolean modifier in Blender 2.91+ the default is the Exact solver, which will be slower. When you convert a file from 2.83 to 2.91+ the Fast solver will be kept.

So this is all expected. Selecting the Fast solver will bring back the old performance.
Closing. This is not a bug.

Since 2.91 Blender has a new solver for booleans called *Exact*. This solver can solve trickier cases but is also slower. The old method is still available as the *Fast* solver. Read more here: https://wiki.blender.org/wiki/Reference/Release_Notes/2.91/Modeling#Boolean. When you use the boolean modifier in Blender 2.91+ the default is the *Exact* solver, which will be slower. When you convert a file from 2.83 to 2.91+ the *Fast* solver will be kept. ![image.png](https://archive.blender.org/developer/F9865247/image.png) So this is all expected. Selecting the *Fast* solver will bring back the old performance. Closing. This is not a bug.

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 modifier performance issues #86236