The Boolean Modifier has it's settings mixed up when compared to their functions. #71889

New Issue

Junaid Hossain Efaj · 2019-11-25T14:48:42+01:00

2019-11-25 14:48:42 +01:00

System Information
Operating system: Windows 10
Graphics card: Nvidia Geforce 940mx

Blender Version
Broken: 2.80

Short description of error
When using the boolean operation, in some of my recent projects, I've noticed that the settings provided by the boolean operation is all messed up. For example, I wanted to use the difference operation, but blender decided to use Union operation.
And when I set the operation to Union, it performed the Difference Operation. I'm still not sure about the intersection operation yet.
Bonus: If you decide to perform boolean with an object with more than one "sub-object" (as in an object consisting of 2 cubes or such),
then blender would apply the boolean operation to one of the sub-object and won't do the same for the other unless you connect their vertices in edit mode.

**System Information** Operating system: Windows 10 Graphics card: Nvidia Geforce 940mx **Blender Version** Broken: 2.80 **Short description of error** When using the boolean operation, in some of my recent projects, I've noticed that the settings provided by the boolean operation is all messed up. For example, I wanted to use the difference operation, but blender decided to use Union operation. And when I set the operation to Union, it performed the Difference Operation. I'm still not sure about the intersection operation yet. Bonus: If you decide to perform boolean with an object with more than one "sub-object" (as in an object consisting of 2 cubes or such), then blender would apply the boolean operation to one of the sub-object and won't do the same for the other unless you connect their vertices in edit mode. ![image.png](https://archive.blender.org/developer/F8165428/image.png)

Junaid Hossain Efaj commented

2019-11-25 14:48:42 +01:00

Added subscriber: @Phil_Violated

Anthony Edlin commented

2019-11-25 17:07:46 +01:00

Added subscriber: @AnthonyEdlin

Anthony Edlin commented

2019-11-25 17:07:46 +01:00

Hi, thanks for the report.

I can't reproduce what you describe wrong with booleans on a simple file. Can you share as simple file as possible that demonstrates the issue you are having? Also you can check with 2.81 and a nightly build here and see if it works.

Hi, thanks for the report. I can't reproduce what you describe wrong with booleans on a simple file. Can you share as simple file as possible that demonstrates the issue you are having? Also you can check with 2.81 and a nightly build [here ](https://builder.blender.org/download/) and see if it works.

Junaid Hossain Efaj commented

2019-11-26 17:48:16 +01:00

In #71889#817220, @AnthonyEdlin wrote:
Hi, thanks for the report.

I can't reproduce what you describe wrong with booleans on a simple file. Can you share as simple file as possible that demonstrates the issue you are having? Also you can check with 2.81 and a nightly build here and see if it works.

Well sorry if my bug description was too vague, but I'll send both a screenshot and a project file. And yes, I was working on 2.81.
This screenshot is just an example of one instance of the bug where it happened on its own.

File link: https://drive.google.com/open?id=1nDC_SBzJqW8xet3eIZACvgyXuEznzJdW

And as for that one "bonus" bug, I don't seem to be able to recreate it like I could yesterday.
But I'll keep you informed if I manage to bump into it again.

> In #71889#817220, @AnthonyEdlin wrote: > Hi, thanks for the report. > > I can't reproduce what you describe wrong with booleans on a simple file. Can you share as simple file as possible that demonstrates the issue you are having? Also you can check with 2.81 and a nightly build [here ](https://builder.blender.org/download/) and see if it works. Well sorry if my bug description was too vague, but I'll send both a screenshot and a project file. And yes, I was working on 2.81. This screenshot is just an example of one instance of the bug where it happened on its own. ![image.png](https://archive.blender.org/developer/F8169137/image.png) File link: https://drive.google.com/open?id=1nDC_SBzJqW8xet3eIZACvgyXuEznzJdW And as for that one "bonus" bug, I don't seem to be able to recreate it like I could yesterday. But I'll keep you informed if I manage to bump into it again.

Anthony Edlin commented

2019-11-26 22:06:31 +01:00

Changed status from 'Open' to: 'Archived'

Anthony Edlin closed this issue

2019-11-26 22:06:31 +01:00

Anthony Edlin self-assigned this 2019-11-26 22:06:31 +01:00

Anthony Edlin commented

2019-11-26 22:06:31 +01:00

Thanks for the file. When I check your file you can see that the wall section you are trying to boolean is not solid. It seems maybe there was already a boolean applied or intersected on inside half of wall mesh. If I fix this and make the section just a plain wall face, and I also make it more manifold by added a face to the bottom, then this is the result I get:

fixedboolean.mp4

There are real issues with booleans in blender given the implementation, but in this case I think it's responding reasonably.
Going to archive this for now.

Thanks for the file. When I check your file you can see that the wall section you are trying to boolean is not solid. It seems maybe there was already a boolean applied or intersected on inside half of wall mesh. If I fix this and make the section just a plain wall face, and I also make it more manifold by added a face to the bottom, then this is the result I get: [fixedboolean.mp4](https://archive.blender.org/developer/F8169905/fixedboolean.mp4) There are real issues with booleans in blender given the implementation, but in this case I think it's responding reasonably. Going to archive this for now.

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

The Boolean Modifier has it's settings mixed up when compared to their functions. #71889