# Clipping plane fill errors

**URL:** <https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011>\
**Category:** Rhino for Windows\
**Created:** [August 18, 2014, 10:23pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011 "2014-08-18T22:23:45Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![FlynnAD](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/flynnad/32/507116_2.png) [@FlynnAD](https://discourse.mcneel.com/u/FlynnAD)\
**Post date:** [August 18, 2014, 10:23pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/1 "2014-08-18T22:23:45Z")

</div>

Hi McNeel,

There have been a few posts about the bugginess of Display Mode’s Clipping Plane Fill ability (topic 1222, 10009, 2065).

Do you have any solutions or workarounds yet?

What I usually get is clipping planes that do not fill a solid object at all. This happens more often than anything.

Next, Rhino will display a partial fill on a clipped object, stopping the clipped fill in some random middle of the object.

Lastly, and only in a few very simple tests, will the fill fully work.

1. While trying to make a file to send to you, I had a situation where 3 clipping planes were on. This resulted in a partial fill of only one of the clipping planes. The other two were open/ empty.

2. When I unhid all the objects (as I had hidden some to focus on this issue), the clipping plane fill properly filled the solid objects on all three clipping planes. So I thought this might have to do with hidden objects.

3. So I undid the show command, grouped the objects that were partially filled, then unhid everything. Typed Invert to flip the selection, deleted everything else (so there are no hidden objects and nothing else in the file). Rhino went back to the partially clipped fill as in step 1. Really odd.

Some of this seems to be issues with hidden objects or layers that are off (perhaps groups), but I cannot make sense of it.

Thank you,  
Matt

![](https://sea3.discourse-cdn.com/mcneel/uploads/default/11501/697936c933c5af38.jpg)  
 ![](https://sea3.discourse-cdn.com/mcneel/uploads/default/11502/b569e2ea920c32b5.jpg)  
 ![](https://sea3.discourse-cdn.com/mcneel/uploads/default/11503/3ef561f4d081171c.jpg)

---

<div class="post-metadata">

**Author:** ![pascal](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/pascal/32/479395_2.png) [@pascal](https://discourse.mcneel.com/u/pascal)\
**Post date:** [August 18, 2014, 10:41pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/2 "2014-08-18T22:41:14Z")

</div>

Hi FlynnAD- in the last scenario - does any of the other clipping planes correspond to the location partial solid fill above?

-Pascal

---

<div class="post-metadata">

**Author:** ![FlynnAD](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/flynnad/32/507116_2.png) [@FlynnAD](https://discourse.mcneel.com/u/FlynnAD)\
**Post date:** [August 19, 2014, 12:51am UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/3 "2014-08-19T00:51:19Z")

</div>

Hi Pascal,

No. All the other clipping planes that are shown in image #3 are parallel to or perpendicular to the clipped-fill-object-edge, but those clipping planes are not in the location (or extension) where the partial fill was clipped.

Matt

---

<div class="post-metadata">

**Author:** ![moosejuicezeus](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/moosejuicezeus/32/55011_2.png) [@moosejuicezeus](https://discourse.mcneel.com/u/moosejuicezeus)\
**Post date:** [June 16, 2017, 9:17pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/4 "2017-06-16T21:17:14Z")

</div>

I’ve encountered similar problems today with intermittent fill of clipped objects. At first there seemed to be no pattern, but I did some experimentation and think I may have uncovered a workaround (and perhaps a clue that could help track down the bug): it seems that having visible geometry at/near the origin remedies any clipping fill errors.

 ![](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/a/a/aab30aad3914234a47a67db78a680ec773812719.png)  
 ![](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/a/8/a8ec27af6e33ec2ac1dbc74713ff697ef31bb2cb.png)

This seems to work regardless of object type (I tested a point, curve, surface, extrusion, and brep). And it seems to work regardless of if the origin object is being clipped or not. (In this example, I can flip the clipping plane; the point is no longer visible but the clipping fill still works).

I tested a bit further in a simple model and found some weird behavior relative to clipping plane orientation:

Any thoughts on addressing this bug? Something that’s coming to 5? Or something that will get addressed in 6?  
FYI: I’m using Version 5 SR14 64-bit (5.14.522.8390, 5/22/2017)

---

<div class="post-metadata">

**Author:** ![John\_Brock](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/john_brock/32/476283_2.png) [@John\_Brock](https://discourse.mcneel.com/u/John_Brock)\
**Post date:** [June 16, 2017, 9:21pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/5 "2017-06-16T21:21:46Z")

</div>

I think this has been fixed in V6.  
Please give it a go and let us know if it’s better.

---

<div class="post-metadata">

**Author:** ![djhg](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/djhg/32/762280_2.png) [@djhg](https://discourse.mcneel.com/u/djhg)\
**Post date:** [June 30, 2018, 4:21am UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/6 "2018-06-30T04:21:24Z")

</div>

Clipped plane fills aren’t reliable for me. (Three images below from Rhino 6 SR6):

**Model Space** (Sometimes the fill colour shows, sometimes it doesn’t. The view with the missing fill lost it when it was converted to a Front view and back again to perspective.)

 ![Model](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/e/5/e5b55263c112c65e826605e4bd24c3cfbd10432c.PNG)

Layout Space (This is what they should always look like, but those green fills come and go in the display as I work on the project. When they go, the clipped planes become the object colour.)

 ![Layout](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/4/0/40fa356a32ddc7230b41cd950484b93950257e1a.PNG)

The Print (They never print.)

 ![Print](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/a/1/a14e3904f5fe39a515a63625f70646d383b68954.PNG)

---

<div class="post-metadata">

**Author:** ![djhg](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/djhg/32/762280_2.png) [@djhg](https://discourse.mcneel.com/u/djhg)\
**Post date:** [September 16, 2018, 3:53am UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/7 "2018-09-16T03:53:00Z")

</div>

Hping for news on this. Sectional perspectives are a great tool but unreliability of fill is a significant handicap.

---

<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:** [September 17, 2018, 10:40am UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/8 "2018-09-17T10:40:18Z")

</div>

I can reproduce the issue with the PDF export not printing the clipping color - [RH-48472](https://mcneel.myjetbrains.com/youtrack/issue/RH-48472).

I haven’t been able to reproduce the other issues that you mention. Can you post a simple file that shows this behavior?

---

<div class="post-metadata">

**Author:** ![alr](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/alr/32/116224_2.png) [@alr](https://discourse.mcneel.com/u/alr)\
**Post date:** [September 17, 2018, 12:48pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/9 "2018-09-17T12:48:44Z")

</div>

I can’t get any fill other than the default to show up. ever

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/d/9/d990fb3913464f1adf5b992d82036e54c6372301.png)  
[Copy of Shaded.ini](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/5/6/564a391467718b8b31470c35f1a50a9f15366038.ini) (12.5 KB)  
[fill bug.3dm](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/3/c/3cb76d6ea7addca0dbe854dcf964efa6d497a22f.3dm) (432.9 KB)

here are my files if it helps!

---

<div class="post-metadata">

**Author:** ![djhg](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/djhg/32/762280_2.png) [@djhg](https://discourse.mcneel.com/u/djhg)\
**Post date:** [September 17, 2018, 1:58pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/10 "2018-09-17T13:58:52Z")

</div>

As you can see in the print in my project a post above, the thick lines at the clipped edges don’t print either. I’ll upload this file via the upload link.

I tried moosejuice’s point-at-origin solution but it doesn’t fix the absence of fill display in the perspective view.

Sectional perspectives are a powerful architectural illustration tool.

---

<div class="post-metadata">

**Author:** ![pascal](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/pascal/32/479395_2.png) [@pascal](https://discourse.mcneel.com/u/pascal)\
**Post date:** [September 18, 2018, 3:10am UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/11 "2018-09-18T03:10:11Z")

</div>

Hello @alr - I get the green clipped plane here - can you please run the `SystemInfo` command in Rhino and paste the results here?

thanks,

-Pascal

---

<div class="post-metadata">

**Author:** ![alr](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/alr/32/116224_2.png) [@alr](https://discourse.mcneel.com/u/alr)\
**Post date:** [September 18, 2018, 9:37am UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/12 "2018-09-18T09:37:05Z")

</div>

Rhino 6 SR9 2018-9-10 (Rhino 6, 6.9.18253.21101, Git hash:master @ f7cbad0c040a5ec317eace6ef2e7e57756bfc855)  
Licence type: Commercial, build 2018-09-10  
License details: LAN Zoo Network Node

Windows 10.0 SR0.0 or greater (Physical RAM: 16Gb)  
Machine name: PC-BXL-13

Quadro M4000/PCIe/SSE2 (OpenGL ver:4.5.0 NVIDIA 361.91)

OpenGL Settings  
Safe mode: Off  
Use accelerated hardware modes: On  
Redraw scene when viewports are exposed: On

Anti-alias mode: 4x  
Mip Map Filtering: Linear  
Anisotropic Filtering Mode: Height

Vendor Name: NVIDIA Corporation  
Render version: 4.5  
Shading Language: 4.50 NVIDIA  
Driver Date: 2-8-2016  
Driver Version: 10.18.13.6191  
Maximum Texture size: 16384 x 16384  
Z-Buffer depth: 24 bits  
Maximum Viewport size: 16384 x 16384  
Total Video Memory: 8 GB

C:\Program Files\Rhino 6\Plug-ins\Commands.rhp “Commands” 6.9.18253.21101  
C:\Program Files\Rhino 6\Plug-ins\RhinoScriptEditor.rhp “RhinoScript Editor” 6.9.18253.21101  
C:\Program Files\Rhino 6\Plug-ins\WebBrowser.rhp “WebBrowser”   
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp “Renderer Development Kit”   
C:\Program Files\Rhino 6\Plug-ins\RhinoScript.rhp “RhinoScript”   
C:\Program Files\Rhino 6\Plug-ins\RhinoBonusTools.rhp “Rhino Bonus Tools”   
C:\Program Files\Rhino 6\Plug-ins\IdleProcessor.rhp “IdleProcessor”   
C:\Users\alr\Downloads\elefront400\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0  
C:\Program Files\Rhino 6\Plug-ins\rdk\_etoui.rhp “RDK\_EtoUI” 6.9.18253.21101  
C:\Program Files\Rhino 6\Plug-ins\rdk\_ui.rhp “Renderer Development Kit UI”   
C:\Program Files\Rhino 6\Plug-ins\NamedSnapshots.rhp “Snapshots”   
C:\Program Files\Rhino 6\Plug-ins\Alerter.rhp “Alerter”   
C:\Program Files\Rhino 6\Plug-ins\IronPython\RhinoDLR\_Python.rhp “IronPython” 6.9.18253.21101  
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp “RhinoCycles” 6.9.18253.21101  
C:\Program Files\Rhino 6\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 6.9.18253.21101  
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 6.9.18253.21101  
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”   
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros 6\VRayForRhino.rhp “V-Ray for Rhino”   
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp “Displacement”   
C:\Users\alr\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\SectionTools (fbdb1d7f-8cfb-42c1-9858-87cb6315932c)\2018.8.24.259\SectionTools.rhp “SectionTools”

---

<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:** [September 19, 2018, 10:56am UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/13 "2018-09-19T10:56:58Z")

</div>

@djhg, I got your file. In the layout all details are set to use the `Wireframe` display mode. Which display mode are you using to get this issue? Also, that’s a pretty big scene, I don’t suppose you have a simple file with just one or 2 solids and a clipping plane that causes this?

@alr,

> Driver Date: 2-8-2016

I would start by updating that driver to the current version.

---

<div class="post-metadata">

**Author:** ![alr](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/alr/32/116224_2.png) [@alr](https://discourse.mcneel.com/u/alr)\
**Post date:** [September 19, 2018, 12:09pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/14 "2018-09-19T12:09:31Z")

</div>

> [@wim](#):
>
> I would start by updating that driver to the current version.

fair enough! but unfortunately it didn’t solve my issue

updated info below:

Vendor Name: NVIDIA Corporation  
Render version: 4.6  
Shading Language: 4.60 NVIDIA  
Driver Date: 6-4-2018  
Driver Version: 23.21.13.9174  
Maximum Texture size: 16384 x 16384  
Z-Buffer depth: 24 bits  
Maximum Viewport size: 16384 x 16384  
Total Video Memory: 8 GB

---

<div class="post-metadata">

**Author:** ![djhg](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/djhg/32/762280_2.png) [@djhg](https://discourse.mcneel.com/u/djhg)\
**Post date:** [September 19, 2018, 4:58pm UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/15 "2018-09-19T16:58:35Z")

</div>

> [@wim](#):
>
> Which display mode are you using to get this issue?

The three details containing the two elevations and the sectional perspective on the 24x36 layout should be already set to rendered view mode.

Re: smaller project:  
I suppose we could use this one and just delete everything but one (or all) of the few clipped objects. Maybe the ground object.

---

<div class="post-metadata">

**Author:** ![djhg](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/djhg/32/762280_2.png) [@djhg](https://discourse.mcneel.com/u/djhg)\
**Post date:** [September 26, 2018, 5:56am UTC](https://discourse.mcneel.com/t/clipping-plane-fill-errors/11011/16 "2018-09-26T05:56:33Z")

</div>

By way of follow-up, I hope it’s worth mentioning that this is may be an important thing to clear up.

Also, I am finding that I can’t count on consistency with respect to the fill’s behaviour. In only a few places will it display in the colour desired. In some cases it will fill in with the surface colour of the object cut. In others it will fill with shadow colour, as if the wall is hollow and full of shadow. Of all the clipping plane aberrations, this inconsistency is the worst, as cut objects will in some places read as dark/solid where the error is to produce a shadow, and in others read as light/open where the error is to use the colour of a light-coloured object.