# Ghosted Surface After Boolean

**URL:** <https://discourse.mcneel.com/t/ghosted-surface-after-boolean/111461>\
**Category:** Rhino for Windows\
**Created:** [November 3, 2020, 5:14am UTC](https://discourse.mcneel.com/t/ghosted-surface-after-boolean/111461 "2020-11-03T05:14:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MohsenMohammadvali](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/mohsenmohammadvali/32/476593_2.png) [@MohsenMohammadvali](https://discourse.mcneel.com/u/MohsenMohammadvali)\
**Post date:** [November 3, 2020, 5:14am UTC](https://discourse.mcneel.com/t/ghosted-surface-after-boolean/111461/1 "2020-11-03T05:14:15Z")

</div>

Hi Guys, This Problem Made me Crazy. have you ever encounter this Recently? After Boolean in most of my surfaces I have this issue…Explode and join again doesn’t help. All surfaces are Degree 3 along with enough ControlPoints. Mesh Option is in High Polygon. they are Not Naked Edge. I shared file.

-windows is updated.

-Graphic Card is Updated.

-Rhino is Updated.

Thanks in advance.

 ![Problem](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/6/2/2/6225c48a3cd25c17e59611338cbd68e8b9a05453.jpeg)  

> **[MoMofile.3dm](https://drive.google.com/file/d/1uT2kmQ0w9aTKsh0Cg215Zb9I0teV_bAi/view?usp=sharing)**
>
> Google Drive file.

---

<div class="post-metadata">

**Author:** ![wim](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/wim/32/747482_2.png) [@wim](https://discourse.mcneel.com/u/wim)\
**Post date:** [November 3, 2020, 9:42am UTC](https://discourse.mcneel.com/t/ghosted-surface-after-boolean/111461/2 "2020-11-03T09:42:34Z")

</div>

Hi -

> [@MohsenMohammadvali](#):
>
> have you ever encounter this Recently?

This situation is caused by a trim curve that is somewhat bad and creates a surface that the mesher has problems with.

You didn’t include the original objects that you used to create this object and so it’s difficult to say exactly where it went wrong.

If you extract those surfaces and untrim them with the `KeepTrimObjects=Yes` and `AllSimilar=Yes` options, you will get a shaded untrimmed surface and the trim curve for each of these.  
In Rhino 7, there’s the `IntersectSelf` command that will show you where this curve is bad - there’s a tiny self-intersecting loop somewhere.

It looks like you can fix the surfaces by running `SimplifyCrv` on the curves and then trim the surfaces.

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/5/2/9/5294b1a511a8481a2bed4fe49141ba26512ecb61.jpeg)  
In this picture: a non-fixed surface on the right and a fixed one on the left with a point indicating where the self-intersection occurs.  
-wim

---

<div class="post-metadata">

**Author:** ![MohsenMohammadvali](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/mohsenmohammadvali/32/476593_2.png) [@MohsenMohammadvali](https://discourse.mcneel.com/u/MohsenMohammadvali)\
**Post date:** [November 3, 2020, 11:32am UTC](https://discourse.mcneel.com/t/ghosted-surface-after-boolean/111461/3 "2020-11-03T11:32:42Z")

</div>

Appreciated!  
Thank you so much !