[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Home]
Board
Settings Home
/3/ - 3DCG



Thread archived.
You cannot reply anymore.



Havin bool tool issues

use blender they said
its free they said

what the fuck is this shit?
blender version 2.79
>>
moving the cylinders on the axis makes it even worse... jesus
>>
Learn to post questions properly first.
>>
you're not actually supposed to use Booleans in poly modeling tools like Blender.

If you were sculpting or doing parametric modeling it would have been fine though
>>
>>608109
having said that, the dogma that is not using Booleans in poly modeling tools has nothing to do with the problem you're facing now, and it's highly more likely that you yourself are doing something wrong.
>>
>>608104
Dude, check the normals your on bool meshes, make sure that all meshes are closed. Also, you can try changing boolean algorithm from bmesh to carve, it can fix these things sometimes, but it's quite slower.
>>
>>608109
>>608105
>>608104
Booleans can work just fine in Blender if you're not retarded.
>>
>>608112
normals are fine is just a cyliner mesh. as you can see here it works with a cube...
>>
Well, Blender strikes again and it's always the user's fault according to the Blender cultists.
>>
>>608123
Well, it is the user's fault in this case, admit it or not. The same shit happened to me in Modo when I didn't know what I was doing.
>>
>>608124
Yet, somehow, this happens in Blender and you're very quick (and wrong) to blame the user.
>>
>>608132
99% of the time it's a PEBKAC.
>>
File: whatsthedealwithbooleans.png (166 KB, 1920x1920)
166 KB
166 KB PNG
>>608104
Did this in a couple minutes. So, really, what's the deal with booleans?
>>
>>608137
That's a contrieved example.
>>
>>608137
Before you ask what "contrieved" means, you made "a boolean", not "the boolean OP wants and Blender can't perform". Your "a boolean" is meaningless, just like Blender.
>>
>>608139
Intentionally, to show that no problem appears even in such a scenario, which is more complex than OP's (e.g., note the monkey).

>>608144
It's spelled "contrived". You're welcome.
>>
>>608145
You would be welcome to fix at least some of Blender bugs before promoting it.
>>
>>608109

What a fucking idiots. Booleans work fine if you know where to place edge loops and fix ngons.
>>
>>608149
In other words booleans work fine in Blender as long as you don't do anything that doesn't work.
>>
Git gud
>>
>>608150
>In other words, booleans work fine in [INSERT 3D SUITE OF CHOICE] as long as you know what the fuck you are doing.

Fixed that for you.
>>
>>608153
Ha, got eem
>>
>>608153
>>608154
So what's OP doing wrong that makes the fact that nothing works properly in Blender his fault?
>>
>>608156
Well, if he would learn how to use a fucking basic operation then he wouldn't post this shitass thread, so I guess it is his fault
>>
>>608156
>>608150
Oh come on, stop shitposting in every fucking thread. This is really not Blender's fault, end of story.
>>
>>608124
so please explain what has gone wrong here then...enlighten the rest of us oh great one
>>
>>608157
you still havent explained WHAT has been done wrong and how to make it right..
>>
>>608104
Are you doing it like this?:
>create cylinder and position it
>select cylinder, then select a mesh you want to cut
>click CTRL & -
>done, no need to touch any of the settings, just apply the modifier, but before applying you can reposition and edit the geometry of your cutter in realtime
>>
>>608166
You still haven't contributed ANYTHING of value to this thread.
>>
>>608175
Normally I would tell you to learn C++ and go contribute some bug fixes to your precious Blender because it badly needs them but after 10 years or so of "people identifying themselves as women" working on Blender's codebase, it has become like a condemned building. So there's really no point.
>>
>>608137
>>608121
Booleans cannot resolve to closed shapes if both shapes are not closed.
i.e. if you have a hole in your mesh due to unwelded vertices or something like that, you will probably get something like in the OP.
>>
>>608183
>>608109
also, what I meant when I said that "not using Booleans in poly modeling tools is dogma", is that by the time all of these people responded to your thread, you could have just bridged the two edge loops instead of trying to fight around Boolean bullshit.
Booleans are almost never worth the grief they bring you afterwards, unless you take extra special care to use them correctly and never fuck up
>>
>>608185
Can you give a clear definition for:
>take extra special care to use them correctly and never fuck up
What does a Blender user needs to do exactly to satisfy your requirements and enjoy working booleans?
>>
>>608196
Someone mentioned some points earlier
>Booleans work fine if you know where to place edge loops and fix ngons
When you boolean, you end up with fucked up topology that doesn't subdivide or otherwise deform well.
Basically he means that you need to know the silhouette of the object you're making beforehand and plan all of your edge loops with that silhouette as a base. Which you should be doing anyways if you're not a retard.

I imagine most people stop using Booleans for anything but the simplest operations after sufficient headache, so nobody really knows the true breadth of "using Booleans correctly". In any event, you will know that you are using Booleans wrong when something wrong happens. The results of a bad Boolean operation usually snowball into something egregiously bad and hard to miss.
>>
>>608205
You can also just use a rounded edge shader and bake it down to a low poly, that way you don't need to use subdiv and care so much about topology after fucking it up with booleans.
>>
Enjoying my Modo masterrace booleans that I can actually use in polymodeling AND in subD
>>
>>608205
And how does one know
>the silhouette of the object you're making beforehand
You have complicated rules set up in your head that have no basis in reality or practicality. Those are just there to get around Blender's countless bugs and pretend everything is fine.
>>
Stop replying to trolls.
>>
>>608166
>Watch any video on Boolean modifier, check
>Hey, it's working now
Btw, you check "I'm not a robot", I guess recaptcha didn't think about you
>>608175
+1
>>
>>608225
>And how does one know
>>the silhouette of the object you're making beforehand
It’s called conceptual art, or having a fucking imagination.
>>
>>608242
You need a lot of imagination to pretend that Blender is useable.
>>
>>608226
The only troll here is you calling other people names.
>>
I really don't understand the point of this trolling anymore. Every single thread on /3/ is now full of it. Everyone will leave eventually because of it. It's seriously mind-boggling. I only feel sorry about noobs who will get influenced by all this shit.

The best part is that some people even admitted they are trolling just for fun, even if they are Blender users. How mental do you have to be to find this fun? You're doing it for months, it is insane. Seek help while you can.
>>
>>608257
Blender fanbois, cultists and shills are going to leave and that's a good thing because it'll make room for talent. Noobs not being influenced by anvil and donut tutorials is a good thing also.
>>
>>608225
senpai I don't use Blender.
These are general rules that apply to all poly modeling techniques and software.
>>
>>608259
I haven’t seen any artwork post by any of you trollfags. Show us that amazing talent that supposedly cannot be executed in Blender, or be humiliated.
>>
>>608259
Talent?
Like you?
Post something of value not the same dead arguments.
>>
>>608284
Ok. I'm a bad person, my arguments are dead and Blender is still bad, crumbling software that wastes your time.
>>
>>608287
Can you tell me why are you doing this? Why do you purposely want to ruin every thread on this board, the board where you spend time as well? I know it's always you, it comes in waves and you constantly samefag. Why do you care so much about what other people do?
>>
>>608291
At this point, I’m guessing it’s a mental disorder. But it’s fine, every board can have its own pet.
>>
>>608291
Blender killed his mommy and raped his daddy, now he is on an epic revenge trip. He wont stop until every Blender user is denouncing this satanic software and every cult member of the BF is dead or crippled.
>>
>>608104
Clean up your geometry before doing new boolean operations.

If you keep added them on together you amass a deadly amount of construction history. It'll spass out bigtime.
>>
>>608287
No, you're just an incompetent that is seemingly unwilling to learn. Not that this cesspool is much of a place for that anyway.
>>
>>608308
Hello grandpa. Tor Frick and me are laughing at you.
>>
>>608318
I don't see how that's funny or how he's related.
>>
>>608320
Because why would you need to cleanup if you use a rounded edge shader and the piece doesn't deform? If I had to cleanup after every single boolean operation, it would be so slow that I wouldn't even use it in the first place. Just apply bools everywhere and bake the shader down and everything just works.
>>
>>608325
Nigga, okay man, but it really depends highly on what the fuck you're trying to achieve.

Also, depending on software, if you don't at least "clean up" by using triangulation and deleting construction history, your mesh/scene will fuck up and/or you will get crashes.
>>
>>608327
I know, that's exactly what I'm saying. Depends on the software, depends on what you're doing, so don't generalize. In some cases it can be perfectly fine. Nigga.
>>
>>608328
Well in OP's case, it wasn't fine.
>>
>>608342
??? Why not? I don't see that he's trying to subdivide it and he's using booleans on a perfectly flat surface... The problem he had has nothing to do with bad boolean usage, he was just doing it the wrong way and fucked up.
>>
>>608112
>>608124
>>608137
>>608149
>>608152
>>608157
>>608158
>>608342
Op here motherfuckers

Its blenders fault, if you try to make too many booleans at once it starts spazzing out.

after applying a few booleans first it worked as it supposed to work.

you fuckers have no idea what you are talking about this was the first and last time looking for help on /3/ fucking autistic faggots
>>
>>608997

What did you expect from delusional blendies?
>>
>>608997
Like we said, so, you didn't know how to use the software - your fault.
>>
>>608997
i-its not my fault boys!

if you keep saying that, maybe you'll eventually believe it. Also, what made you think /3/ was your personal support?
>>
>>608997
It seems you finally learned how to use booleans in Blender. Congratulations!

Now, quit bitching and post some dope ass renders, faggot.
>>
>>609003
kek




Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.