Any way to integrate section styles with Make2D output?

Rhino Rhino for Windows
,
1

I’d like the hatches that are formed from the section styles in Rhino 8 to be included in the output of my Make2D, so that when I am exporting geometry like walls that are cut with a section plane, I don’t have to manually go and add a poche fill. Is there any vector data to these section styles that can be included in Make2D? Or is it just a raster image being applied to the cut element, and I can’t integrate it automatically with the vector data formed by Make2D?

1 Like
2

Hi Noah -

We have that request on the list: RH-80884 Add hatches to clipping plane intersections

If you are exporting to PDF, you could put the viewport in a technical display mode and export as vector, thus bypassing the Make2D step.
-wim

3

Are hatches for objects that are not sectioned, but seen in the section, also on the list?

To expand the concept of section styles: they could also contain a color parameter, or better even, a hatch param., for the elevation (not section) of objects.

‘Elevation’ colors / hatches / textures even, are equally important as section colors when the goal is a feature complete vector output of the scene.
Thanks!

4

Hi @wim,
I have also asked for that functionality (hatches on the Make2D), but ideally Make2D would be rendered obsolete by the dynamic sections.
Here are the two reasons why Make2D is still preferable to Dynamic Sections:

  1. Maintain Source Layers - If you are exporting vectorial drawings it is useful to maintain the source layers. This makes reading and use the of the files easier. The exporting of vectorial files is still a common way of exchanging information and a well structured model will produce a well structured vectorial file, where you can click the lines as see to which element they belong. The fact that Dynamic sections collapses this essential information into a handful of layers makes the export of those drawings close to useless. Make2d drawing is by no measure a perfect tool and could be improved, in complex models lines are too fragmented and chaotic… but better than nothing.
  2. Select drawing position - When exchanging information (vectorial files) between parties, it is essential to have a common shared reference point that relates plans an sections across users and teams. Make2D allows you to control where the resulting geometry is placed in relation to the model. Besides the sharing of files, having a more direct relation to the model makes cross checking the result much easier, and allows, with some coordination, to simply duplicate the Detail view to create a rendered background for your drawing. The fact that Dynamic Sections only places the drawings in the world CPlane and that it chooses the model centroid as the insertion point still bemuses me and makes all this either not possible or extremely cumbersome and complex.

This is a long way to say that one wish may be to have the Dynamic Section hatches integrated in the Make2D, but the biggest wish is to have some Make2D options integrated in the Dynamic Sections.

Regarding your suggestion to use the technical display mode to export as vector, I had (moderated) high hopes for that, especially to use detail views to crop unnecessary parts of a model. However, with that process we run into issues regarding scale and layers. If I remember correctly although you could see the layers in the PDF, when importing it to Illustrator (as a path to AutoCad) the layers were gone. A useful tool may be to develop a way of exporting the layout/technical view to other formats than PDF.

Thanks, N
@rajaa I promised on another post (quite a while ago) to explain the importance of keeping layers and origin points. This is a start.

1 Like