> The example is just 2 pipes, created on plane using your pipe script.(attached)

Thanks, yup definitely a bug, the intersector appears to be having difficulty getting one piece of the intersection curve, you can see this if you select them and run Construct / Curve / Isect to create the surface/surface intersection curves.


> I am actually now seeing quite a few problems with booleans, usually
> when a boolean crosses a previous cut.

Yeah definitely the amount of calculations get more complex when there are more edges and pieces running into each other, particularly if you end up having small fragments involved.

Definitely send these on over when you run into them. Probably for many of them I will have to collect them up and send them to the people that make my geometry library and wait for them to fix them which will take some time. But eventually progress can be made on them.

- Michael

Hi Michael,

>>>Thanks, yup definitely a bug, the intersector appears to be having difficulty getting one piece of the intersection curve, you can see this if you select them and run Construct / Curve / Isect to create the surface/surface intersection curves.

But the problem is only after a sweep. If I use "solid cylinder", or "extrude a circle", then no problem. Is the problem with the boolean, or with the sweep?

I can of course put together some examples of the problems, but I would prefer to find simple fully repeatable examples, then e-mail them to you. I could always leave that until after you release 2 beta, then just send any bug reports based on that (if that would be better?)



- Steve

Hi Steve,

> Is the problem with the boolean, or with the sweep?

The problem is with the surface/surface intersection part of the boolean, the sweep is fine.

The cylinder / extrude happens to work in this case because either one of those gets created as an analytic surface subclass. Analytic surfaces can have some special case processing run for them during surface/surface intersection calculations in certain cases.


> I could always leave that until after you release 2 beta, then just
> send any bug reports based on that (if that would be better?)

This is a good idea. I am planning on incorporating the geometry library update into the first v2 beta.

- Michael