Very Computer

Why once does and once doesn't the boolean2 work? Is there a logical answer
or is it just an error occured by bad programming?

: Why once does and once doesn't the boolean2 work? Is there a logical answer
: or is it just an error occured by bad programming?

It works every time for me....
You probably changed something between the first and second
times.

--
______________________________________________________________________________

University of Pennsylvania                          
Department of Biology                                                        
------------------------------------------------------------------------------

Translation = shit booleans.  Don't trust Max for booleans unless you want
to be very disappointed...

A.

hi api
try the STL-Check Modifier before you do the boolean2 operation: if there is
a problem with the mesh, boolean2 will not work!

Quote:> Why once does and once doesn't the boolean2 work? Is there a logical
answer
> or is it just an error occured by bad programming?

I have noticed that occasionally when a boolean wont work moving an operand
in relation to the other operand sometimes allows an operation.  Most times
a third generation boolean wont work, and Ive NEVER gotten a fourth
generation boolean to work, even after collapsing it.  In case like that I
hand-edit the mesh.  Not surprisingly this can be a bit tedious.  I
personally think that it is because my machine does not have the memory to
figure it out.  Try using less points, and ALWAYS make sure both meshes are
closed objects.  One single face missing anywhere on either of the operands
will mean it wont work.  Im sure there is much more to it than that, but
that is how I get by....

:)

Maibe/Squidslayr.

Scale...scale your objects up really big......the calculations are easier
when the objects are big....