Michael, In my video, I can boolean when there is no fillet, but after filleting I can not, these intersecting surface apear after fillet? Loks a bit strange. And in my video I trying to trim this surface and it gives me hole in the end of the video. What I made wrong?

I tream a bit diffrent way.. and get that hole hm.. What is the case?

I made mutal trim in my video... And it does not work as good as select cuting objects when trim.

Hi Andrei,

> I tream a bit diffrent way.. and get that hole hm.. What is the case?

If you are trying to trim with the entire object as the cutting object, MoI will likely be trying to do some surface/surface intersections as part of the cutting operation, and like I was mentioning before in this kind of situation with "barely skimming" surfaces you don't want to do surface/surface intersections.

So instead select edge curves as the cutting object, rather than selecting the full object as the cutter. That should avoid any surface/surface intersections from being done at all.

That's how I did that previously attached file - for the cutting objects I selected all the naked edges (by using the select naked edges script), not the entire object and not both objects as a "mutual trim" either.

- Michael

Another way you can see if there are intersection problems is to select the objects you're trying to boolean and do a Construct > Curve > Isect , which generates all the intersection curves between 2 objects.

If you do that in this case here, you'll see that because the surfaces just very slightly wiggle through each other there are complex intersections in those shallowly intersecting areas:




It's then very difficult for proper final trim boundaries to be created from this type of messy intersection results.

- Michael

Here's a way to get past it:

Michael, thank you! I understand, Idea with intersect is GREAT! Now everything is clear for me. Also Idea to select all edges in this case using naked esge script also is great!
BurrMan, good soltion too! Thanx)