Apologies if this question has been answered in the forum already. I have seen others about line weight management but not this particular issue and/or question.
I am an architect who is trying to create construction drawings from my 3D model. I am having trouble managing layers, hatches and line weights with the new dynamic drawings from clipping planes. I have created a simplified diagram of a “building” with 3 modeled solid volumes representing materials in a wall assembly (Image1). If I use the old Make2d function I am able to maintain the existing layer management (Image2). This allows me to control, line color, line weight, and hatch independently (Image3). It also allows one to model with “rainbow colors” for easy layer identification while printing a different color. Obviously, this method does not dynamically update drawings as one updates the model.
The new dynamic drawing from clipping plane feature in Rhino 8 is great, but I cannot get it to maintain the model layers (Image4).
If I change the print width, line type, line thickness in the modeled layers it does not change the print output (Image 5 is with color outputs that match the layer and Image6 is with the desired outputs changed). The other option is to override these layers through the new drawing layers, but this only features Curves, Solids and Hatches.
I am hoping that I am just missing some toggle that enables this feature. If this is not available yet in Rhino8 I would strongly advocate for this feature to be added in the future.
Why does this matter? The ability to model a building, as one would assemble it, and then dynamically produce drawings, with material specific hatches (insulation, siding, etc…) would be a workflow game changer for architects. That functionality would make Rhino very competitive (and hands down my preference) against other software offerings from Autodesk or others for construction drawing delivery. In my personal experience, the program is rarely used for this function beyond school.
I am a big fan of Rhino and I appreciate your efforts to keep making it better with each iteration.
I’ll probably need your 3dm file and hand-holding to understand what’s missing here.
In a quick test here, the line type and width seem to be updated in the ClippingDrawing?
I created unique print widths and print colors (separate from display color) for each layer in the model I uploaded. I also uploaded a PDF with the print results. The dynamic drawing does not seem to “recognize” the print or layout aspect of the layer.
Where you able to take a look at the file? I am still not able to have the print dialogue recognize layer specific “print width” and “print color”. “Display color” and “Default Width” seem to override these selections.
I’m currently experiencing exactly the same problem.
I would like that my clipping drawings maintain the layer structure that I have in my 3d drawing while still being nested under the main clipping layer.
Here are couple of screens…
This is a view of a clipping plane of a 3d object with the highlighted layers:
Thanks for resurfacing this issue. I was never able to get a solution from McNeel on this item or I was never able to communicate the issue clearly enough to them. I have spent a good deal of time investigating this topic and I do not think the functionality is in the program yet. You can change color between the original display color and the clipping plane sub layer but that is it. Unlike the Make2D command, one does not have specificity of print color, print width and line type come through the clipping drawing.
Given that that functionality is in the Make2D command one hopes that it wouldn’t be too difficult for them to include it in the clipping drawing command. It will be a huge game changer in documentation workflow when it is a feature in rhino.
I agree with you Neal!
I believe McNeel had good intent with creating those commands but it still needs some polishing to make it more user friendly.
I’ve spent good deal of time editing drawings, copying, creating backups, creating alternate views, custom display modes and print settings to get the layouts right and after a year I can’t say that I’ve created the system that suits me. On top of all that, this layer inconsistency makes things even harder. Right now I’m doing a lot of architecture and these are essential for my workflow. Here’s a layout I’ve exported just a couple of days ago. Selecting and editing the struts from the 2d clipping drawing was a real pain here.
I’m always thinking that I’ve made things too complicated for myself as I refuse to use photoshop, illustrator or any other 3rd party software to post process the drawings.
Perhaps a good tutorial, or a case study where these commands are regularly used in arch studio would be a good thing to share/create.
Hopefully McNeal do make some progress improving the workflow and commands.
I think you are on the right track keeping drawing production in Rhino. Multi-program workflows often pile up hours of processing work.
Until the “clipping planes” offer the same level of printer functionality that “make2d” does the best workflow that I have come up with is this:
-Set all clipping plane content to “hairline” or another very fine line weight. This becomes the detail in the drawings (particularly important in construction documents where wall assemblies need to be described. I live update these from the model.
-For the wall or section cut outline I draw a heavier line weight over the live line work. You can also “make2d” or get editable lines from the clipping plane and remove the excess information to make the outline.
It’s not ideal, but the most efficient way I have come up with at the moment.
-Lastly, I am a fan of Enscape (now under the Chaos umbrella) for rendered content. It is not cheap, but it integrates well with the modelling workflow, is pretty fast to get good results from and clients respond very positively toward the output. I find it better to go to the dedicated pros for anything more photo realistic is required.
Hopefully McNeel can integrate the requested clipping plane functionality into the program soon. It would be a huge win for the architects that use the program! If anyone at McNeel is still confused by the request I am happy to get on the phone to walk through the issue - I am also located in Seattle.
