Thanks for the tips. So use higher detailed models when using boolean, correct?

---

[Link to www.3dprevis.com]

So instead of just using boolean to punch holes in a large flat poly, you first make edges in the shape where the booleans will be.

This is a really good tip. Its going Sticky.

---

Please support us and post a [Link to www.digitalartsfront.com] on your website.

--Matt

+Steve Martin:

Not necessarily 'high detailed models'. It helps when there are many polygons on a model. But, there may be some instances where you are creating a laptop (as in my case) where most of the polyons are flat and meshsmooth is not needed. You can't just cut through a flat polygon without any reinforcing edges. My model is highly detailed, but still don't need lots of unnecessary edges, not even for boolean . This is because (from my finding) boolean only needs them during the cutting process.

+VarnishedOtter: You are correct, but this doesn't mean you need to keep ALL of the edges afterwards. As I said to +Steve Martin. Boolean only needs them during the cutting process.

The information I have given isn't to guarantee the successful cutting of every boolean cutting process (although I would be very surprised if it wasn't guaranteed lol). However, the results turned out perfect during my use of boolean as you can see from the following images :

Image 1: Arrows depict where boolean has been used.
Image 2: A successful operation of boolean.
Image 3: Edges removed after the boolean process with the original shape still intact.

One thing to remember, you CANNOT use meshsmooth if you take the edges away after the boolean process. I don't know if meshsmooth works with the edges intact as I've not tested it due to the fact that you don't need meshsmooth on a flat poly anyway.

BTW, thanks for making this a sticky. Glad to have helped.

---

---

The images certainly look good. You've obviously done a bit of boolean work. I have to admit it scares me a bit because it can mess up your topology, but I can see from your images that that's not always the case.

---

[Link to www.3dprevis.com]

thats so good but what i can do on a non flat boly like if i make amodel of my phone and need to make the numbers keys on it

---

Can you be more specific?

---

[Link to www.3dprevis.com]

hmmmm how about with great more segment stuff....... i ever create some modeling which has more segment there (because i used meshsmooth) and i will cut it wit some bolean..... the result is ....... my computer going slow....... do you have any trick with this situation?

---

It'd say try and avoid collapsing a meshsmooth when you can, but obviously it too late in this case. If your computer's running too slow try hiding absolutly everything you can, even if it means half your mesh that you're not working on.

---

[Link to www.3dprevis.com]

Is there a way of optimizing the mesh only in the viewport? Like have the viewport display lowpoly but the render uses the full res.

---

Please support us and post a [Link to www.digitalartsfront.com] on your website.

--Matt

Right click the lightbulb next to your mesh/turbosmooth modifier and select off in viewport. It will still have an effect in the render.

---

[Link to www.3dprevis.com]

Yeah I know that one, but if its just a high-poly non-smoothed model?

---

Please support us and post a [Link to www.digitalartsfront.com] on your website.

--Matt

Ah. Not sure. I never collapse my smoothing modifiers so I've never needed to find out.

---

[Link to www.3dprevis.com]

thought id chime in here too

at least with max 2008 and newer, Boolean received allot of overhalls, for multiple operations you should use pro Boolean, which fixes the multiple cutt error, i should add that with regular bolean it will stop cutting base don number of mesh elements so adding shapes together wont matter to much.

So the trick with boolean is that you can actually detect if an object is going to fail the operation(even tho sometimes stl failed object do work, its not guarantied) by using stl check. stl check was developed for rapid prototyping not dirrectly Boolean related, but a Boolean require closed manifolds, which stl check will insure you have. if your objects pass stl check they should Boolean. and if an object fails stl check, just collapse your stack and go into the sub object mode and any geometry which failed your check will be highlighted(if not check your plug in settings).

another Boolean trick that most people miss, is to work with splines. you can add and subtract splines seamlessly before they are turned into polys (an editable spline function), and then extrude them to build most your complex shapes with out dealing with poly Boolean issues. you just have to know your going to need to Boolean before you start working.

---