Maniphest T71889

The Boolean Modifier has it's settings mixed up when compared to their functions.
Closed, Archived
Actions

Assigned To
Anthony Edlin (krash)
Authored By
Junaid Hossain Efaj (Phil_Violated)
Nov 25 2019, 2:48 PM
Tags
  • BF Blender
  • Modeling
Subscribers
Anthony Edlin (krash)
Junaid Hossain Efaj (Phil_Violated)

Description

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.

Event Timeline

Junaid Hossain Efaj (Phil_Violated) created this task.Nov 25 2019, 2:48 PM
Anthony Edlin (krash) added a subscriber: Anthony Edlin (krash).Nov 25 2019, 5:07 PM

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.

Maciej Jutrzenka (Kramon) added a project: Modeling.Nov 25 2019, 8:46 PM
Junaid Hossain Efaj (Phil_Violated) added a comment.Nov 26 2019, 5:48 PM
In T71889#817220, @Anthony Edlin (krash) 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.

Anthony Edlin (krash) changed the task status from Unknown Status to Unknown Status.Nov 26 2019, 10:06 PM
Anthony Edlin (krash) claimed this task.

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:

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.