RE: Boolean engine did not cope. Result becomes first polygon mesh input

[Michaël Bentitou <michaelb(at)hybride.com>]

I kinda of agree with u, but if you had any experience with Booleans in Softimage 3.x, the Booleans in XSi are sooo much better lol!!

 

-=mb.

 

 

-----Original Message-----
From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Eric Lampi
Sent: Thursday, March 16, 2006 12:46 PM
To: XSI(at)Softimage.COM
Subject: Re: Boolean engine did not cope. Result becomes first polygon mesh input

 

Can someone explain to me why XSI has such **horrible** booleans?  For crying out loud, Lightwave V 1.0 had kick-ass booleans, that was over 15 years ago!

 

/rant off

 

E
 

Freelance 3-D Animator, F/X Artist

----- Original Message ----
From: olivier amrein <oenvoyage(at)gmail.com>
To: xsi(at)Softimage.COM
Sent: Thursday, March 16, 2006 12:15:33 PM
Subject: Boolean engine did not cope. Result becomes first polygon mesh input

hello,
i try to boolean difference 2 fairly simple shapes. a stylised house (not more than 50 faces and a cutting cube)
both are freezed before...they are on same layer... still i got an error message : "Boolean engine did not cope. Result becomes first polygon mesh input"
did anyone see it ? couldn't google something nor find by searching list.
i managed to get some difference boolean when my "cutting-cube" by moving around my cube... but at one point i get that message and it stops booleaning ...
the current project can go on as i separated my object in 2 and then got 2 boolean.,..but still i was wondering what this "boolean did not cope means"?
thanks for any infos
     o

--
-----
china.skol.ch/o