I would like to see if I can request for developers to make a small improvement on how Boolean work. The system of Boolean is flawed. I’ll provide a good example.
(LEFT PICTURE) You can see there’s no problem at all. BUT what if I change the height of face @ top and bottom to be at the same height as the other cube is. I remove half of the cube, so you can see it clearly. A full cube is a lot messy. This is what happened:
(MIDDLE PICTURE) So the result of using Boolean (UNION) is what it looks like. It is quite a mess and this shouldn’t be the case.
(RIGHT SIDE) the result should look like this:
As you can see the issue is when there are more than 1 objects that have the same height where the boolean would be useless and it doesn’t remove the unnecessary faces and edges. The result is a little different in 2.79 and 2.80… but It’s still a mess in the end.
I hope this will help developers make some improvement in the future. Thank you for taking the time reading this topic.
this is great news! …and also obvious that sooner or later the god of the Bevel tool would embrace the Boolean tools ^____^
soo … I’m sure you already know what to do, but since I don’t know how to do anything else, let me show you moments of inspiration on Booleans.
I did the wordplay
hahaha. That’s a good video. The video is quite very clear on how to use boolean system. It really give me a clear understand of how the boolean system (difference) basically work.
we’ll have to wait until the day that the boolean system in Blender will become so much better ^_^.
to be honest, I can’t wait for that day and the day for an official release of Blender 2.8
EDIT 1:
Oh I don’t realize that “Moments of Inspiration” is actually a software… I was wondering what is the name of that program you used for a while. “MoI”… hmmm That system look very good… but that’s not only the system. I have used one different 3D software and I did some test on the system of Boolean. it’s a lot powerful and flawless.
yes moi 3d is totally another software …
it is dedicated only to cad modeling, it was created by the same author of rhinoceros … and it is hard to believe that it has such a simple and minimal interface and at the same time manages to be very powerful in its field …
I try to suggest it as a “moment of inspiration” often to blender developers … because it is objectively done well … and I would love to see similar tools in blender … coincidentally blender lacks just those functions where moi excels … almost like if they completed each other …
Are there any plans at all to have booleans automatically create vertex groups of newly created vertices for modifiers lower in the stack to use? (I’m thinking for bevel and the new triangulate modifier.)
I would like to enable things like bevel-after-boolean somehow, eventually. And the ability to flexibly specify what/how triangulation happens afterwards also seems useful. Whether it be by creating vertex groups or some other method – who knows at this point. First order of business is to get Boolean working reliably and well even, especially as regard to coplanar etc geometry.
Thanks for your work, at this moment its give big improve. Testing modifiers in 2.8 -subd, booleans, new bevel and triangulation modifier https://www.youtube.com/watch?v=KNb19P945FI&t
i was just using Blender 2.8 to work on a vehicle. I was creating a fan for the vehicle. I ran in some issue. I’m not sure if it’s a bug or not. So I ran some test. There are 2 objects. I move the main object with boolean modifier up and down to see if the issue is gone. BUT the issue is not resolved.
The shadow you see is at everywhere. I believe it’s a bug. here’s the picture for you to take a look at.
Thanks @Howard_Trickey for your efforts here. I just wanted to add a little to the understanding. Many years ago I worked on a facet modeller similar in representation to Blender. I wrote the code for the Boolean ops. Clean intersections of surfaces which had nice curves of intersection were straightforward and done quite quickly. However, coplanar faces, colinear edges and touching vertices were a big problem. After three years these were not completely resolved. Humans can look at a scene and say how they’d expect the result to look but software has a harder time. Sometimes (in my code) combining clean manifold objects created non-manifold results and that’s no good. We had a thing called “the epsilon factor” where we nudged vertices in different directions to see how the result might change sometimes this improved the result other times it didn’t. A lot of modern software still doesn’t evaluate Boolean operations correctly in all cases. I’m saying all this so that people get a sense of how hard this task is and don’t underestimate the effort required to solve it.
Thanks PaulMcManus for explaining to others why they should not expect a quick fix on this. I’ve been working for months on it already (spare time).
Xelbayria - that bevel result is unrelated to Boolean, right? You can report it as a bug (see help menu in Blender). But first check if normals are OK. I suspect that’s the problem.
