Prototype: Clone/Copy Clipping-Drawings In Source Layers

[Screamer]

Hello @rajaa and @wim ,

New finding. Latest WIP.

I believe I have the same result with ClippingDrawings as I already saw from someone on this forum.

I’m talking about artefacts. Please try to reproduce it based on video below.

Also, my vision of AddSilhoette parameter is a bit different. Currently the ClippingDrawings command makes a single silhoette line of multiple objects in projection.

I would prefer to have a separate line for each object.

[MattE]

+1 for the Silhouette outline request. An option to add a mask to the outside of the outline would be great, too. That would automatically stop the outlines (and other lines, in fact) short of the over-lying object, in classic technical illustration style.

[wim (Wim Dekeyser)]

Hi Screamer -

@Screamer

The hidden tangent edges are not fully built.

Thanks. → RH-90441 ClippingDrawings: Hidden Tangents

@rajaa

I ran a test, and this is what I get when place ClippingDrawings on XY-Plane, which seems to be correct.

Rajaa, in that image, you are pointing to the wrong edges:

@Screamer

Is it possible to include Text objects to the consideration?

I’ve added that request as RH-90443 ClippingDrawings: Include Annotations

@Screamer

Please try to reproduce it based on video below.

I’m afraid both this video and the previous one that you posted cause an indefinite spinning wheel on both my Windows and macOS machines…

@Screamer

Also, my vision of AddSilhoette parameter is a bit different.

@MattE

+1 for the Silhouette outline request.

Thanks for the reminder. I have that “on my list somewhere” to look more closely into silhouettes. Currently, we are creating those differently in different workflows and that should probably be aligned or more options added.

@MattE

An option to add a mask to the outside of the outline would be great, too.

Yikes…
Can you post an illustration of such?
-wim

[Screamer]

@wim

I’m afraid both this video and the previous one that you posted cause an indefinite spinning wheel on both my Windows and macOS machines…

Could you download these videos and try to playback locally?

Both are played perfectly in Chrome from my side.

[wim (Wim Dekeyser)]

Hi Screamer -

@Screamer

I believe I have the same result with ClippingDrawings as I already saw from someone on this forum.

I’m talking about artefacts.

Thanks.
→ RH-90463 ClippingDrawings: Erroneous Output
-wim

[brian (Brian Gillespie)]

RH-90463 is fixed in Rhino WIP

[Screamer]

Hello @rajaa ,

I found a new idea to expand ClippingDrawings functionality. This could be useful for some users.

Is it possible to have some objects, which are in the plane of ClippingPlane, not included in clipping process, but still be present in the ClippingDrawings result?

So, technically, you are not slicing it, but want to see it in the section. And it’s not a background because it’s intersected by ClippingPlane. But can we force some separate set of objects behave as background?

I would slightly reorganized this dialog to have an extra button like “Objects forced as background“ or “Objects included, but not sliced“…

This will work for mechanical development mostly (maybe somwhere else) with fasteners, shafts, axis, gears and so on in sections.

Looking even thurther I see possibility to have some objects sliced in half only alone the ClippingPlane’s line.

Sorry for keeping you buzy, but there is still room for growth for this functionality.

[kubadrozdowski]

Hello Everybody. Really nice command. It definitely improves the drawing-creation workflow. I tested it in Rhino 8 and Rhino 9 WIP, and I’m seeing the same issues in both.

1. The parts that are sectioned by the clipping plane inherit the original object name and are joined (which is great). However, the parts that are visible in the view are exploded and don’t inherit the object name (and in my opinion, they should). Please see the images below.

   
   

2. After creating the ClippingDrawing, all visible (non-sectioned) parts in the view are shifted by the same offset. It looks like the projection is not accurate. Please see the image below.

   

Also, regarding “Live update” for ClippingDrawing: if the FlattenLayout command is improved, wouldn’t there be less need to maintain a memory-consuming connection between the 3D model and the 2D representation via ClippingDrawings? Layout Details already show the current model state, so they’re effectively live-updating. If FlattenLayout becomes robust and supports reliable updating, wouldn’t a live-updating ClippingDrawing become redundant?

New FlattenLayout command (work in progress). Feedback requested

Hello. It’s great to see you working on this command. I’ve been waiting for something like this for a long time. I just tested the command in Rhino 9 WIP. This is how the original layout looks: [obraz] This is what I obtained from the command: [obraz] I have a few remarks: Detail clipping planes are ignored. The entire model is shown on the flattened layout, instead of only the clipped geometry. [obraz] The Detail Display Mode is ignored. I set it to Technical and expected a tech…

[wim (Wim Dekeyser)]

Hi Kubadrozdowski -

@kubadrozdowski

1. […] However, the parts that are visible in the view are exploded and don’t inherit the object name (and in my opinion, they should). Please see the images below.

In a quick test here, that’s not the case - but the image possibly doesn’t tell me enough about how the scene is set up… Please always provide a 3dm file.

@kubadrozdowski

2. After creating the ClippingDrawing, all visible (non-sectioned) parts in the view are shifted by the same offset. It looks like the projection is not accurate. Please see the image below.

Same here.
Also provide the output from the Rhino SystemInfo command.

@kubadrozdowski

If FlattenLayout becomes robust and supports reliable updating, wouldn’t a live-updating ClippingDrawing become redundant?

If both FlattenLayout and Fake2D become robust, then, yes, of course.
I take it that the “but…” is obvious?
-wim

[kubadrozdowski]

@wim

In a quick test here, that’s not the case - but the image possibly doesn’t tell me enough about how the scene is set up… Please always provide a 3dm file.

ClippingDrawingTest.3dm (316.0 KB)

I’ve attached a small section of the test model.

@wim

Same here.
Also provide the output from the Rhino SystemInfo command.

I can’t share the full model due to confidentiality. When I tested the small section I attached, the problem didn’t occur. However, when I repeat the test on the full model, a gap appears.

SystemInfo
Rhino 8 SR26 2025-12-15 (Rhino 8, 8.26.25349.19001
Windows 11 (10.0.26200 SR0.0)