MoI discussion forum
MoI discussion forum

Full Version: boolean problem

Show messages: All  1-8  9-18

From: Tree (TREELOY)
19 Jan 2010   [#9]
Ah....having similar problems here with a boolean failing, but not sure if it's the same. I don't wanna steal your thread, thought it would be good to keep with the subject of boolean problems. I'm trying to cut the gear shape with the box, with no result.


Image Attachments:
BooleanProblem.jpg 


From: Tree (TREELOY)
19 Jan 2010   [#10]
After importing into v1 and trying it, all went well. I just had to then reimport into v2 beta to continue working with it (cause v2 is so saucey good).

Just hope this will be resolved b4 the final V2 is released.
From: Frenchy Pilou (PILOU)
19 Jan 2010   [#11] In reply to [#9]
@ Tree
Maybe you must post the 3dm file (zipped)
From: Michael Gibson
19 Jan 2010   [#12] In reply to [#9]
Hi Tree, could you please post (or mail to me at moi@moi3d.com) the 3DM file with your gear and box in them so I can test it over here?

It sounds like it could be the same problem but I can't be sure without testing it.


If it is a different issue, it would be very helpful to have the model so I could work on fixing it up in v2.

- Michael
From: Tree (TREELOY)
19 Jan 2010   [#13] In reply to [#12]
Hi Michael,

I mailed you the file. Hope it helps.
From: Michael Gibson
19 Jan 2010   [#14] In reply to [#13]
Thanks Tree - some initial tests seem to indicate that it is actually a different problem than the one mentioned here, so I'm glad you sent it to me.

I will be digging into it to try and figure out what change in v2 broke this case.

- Michael
From: Michael Gibson
27 Jan 2010   [#15] In reply to [#9]
Hi Tree, I was able to track down this boolean problem with the gear and the box that you posted previously here.

It behaved differently in v2 versus v1 due to a small change in the surface/surface intersection tolerance. I've got it tuned up for the next v2 release.

Thanks for reporting the problem.

- Michael
From: Tree (TREELOY)
29 Jan 2010   [#16] In reply to [#15]
Great! Is the surface/surface intersection tolerance something that can be or will be able to be controlled by the user? In the cases where booleans do fail and no result is given or pieces just vanish, would it make sense to give the user control somehow to adjust how it performs the boolean? Sometimes any result would be better than none. Although the opposite can also be said to be true.
From: Michael Gibson
29 Jan 2010   [#17] In reply to [#16]
Hi Tree,

> Is the surface/surface intersection tolerance something that
> can be or will be able to be controlled by the user?

That's theoretically possible, but it's a rather arcane esoteric value for people to adjust, and it is easy to adjust it improperly if you do not fully understand what it is controlling.

Things tend to behave really strangely if it is too loose, you end up with kind of saggy intersections.


> In the cases where booleans do fail and no result is given or pieces
> just vanish, would it make sense to give the user control somehow
> to adjust how it performs the boolean?

Well, part of the update is that if it failed or if there are naked edges in the result when there were none in the inputs, it will repeat the boolean again with an automatically tightened tolerance. It will go through that cycle a few times.

- Michael
From: NightCabbage
2 Feb 2010   [#18]
Almost looks like a PBW (Earthsiege / Starsiege) :)

http://www.angelfire.com/sd2/nightcabbage/Stuff/3dsmax/pbw2.jpg

Show messages: All  1-8  9-18