Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!pikes!mercury.cair.du.edu!mnemosyne.cs.du.edu!isis!uunet!tronsbox!chsdip!groo
From: groo@chsdip (Bill Squier)
Newsgroups: comp.sys.amiga
Subject: Re: Imagine raves (long)
Message-ID: <663171231-comp.sys.amiga@chsdip.UUCP>
Date: 7 Jan 91 09:41:19 GMT
References: <6653@crash.cts.com>
Lines: 29

In message <6653@crash.cts.com> bobl@pro-graphics.cts.com (Bob Lindabury, SysAdmin), writes:
>
>As for the auto-trace and slice...forget it.  I've tried it several times with
>a very complex object (the continents of the world) and Imagine will just not
>slice them.  I finally got enough ram to do the operation (7 megs) but now I
>keep getting the frustrating "an edge is too close to an edge or a face is too
>close to a face" message.  Yeah, great.  After about 35 of those messages I
>gave up.  This is after about 10 minutes of processing on a 68030/88882
>machine!  It give you no indication of where this edge might be or how far
>into this "slice" you are so you have absolutely no idea where this error may
>be coming from.  

The message "And Edge is too close to an edge or a face" is more
frustrating than it appears, since it's not always what the program
means to say.  Apparently it produces that message no matter WHAT goes
wrong with the slice operation.  I had an object I was slicing (a box
being sliced by a tube) which produced that error message, even though
none of the conditions it mentioned were true.

The solution?  LESS POINTS.  After cutting the box down to 10 x 10 x 1
(from 30 x 30 x 10) the slice operation worked perfectly, without having
to move either of the two objects.

If you can possibly do it, see if cutting out points doesn't help.


-----
Bill Squier (groo)	Amiga :  uunet!tronsbox!dsoft!chsdip!groo (best)
`Only Amiga!'	        VAX   :  uunet!vaxb.stevens-tech.edu!u93_wsquier