No, they don’t
Okay. Thank you very much for helping.
Dear @rajaa, I wanted to check in and see if you’ve had a chance to work on this, as you mentioned bumping it up your list. This feature remains critically needed, and I was slightly alarmed to see that the YouTrack issue release target is now set to 9.x. Best, Simon
How does one capture an elevation like this for display in a detail on a layout?
When my model has many buildings in it and I need an elevation from an unobstructed point, I can set a 2-point perspective and try to make something work, but then it’s two-point perspective and not an elevation and it’s also never square to the cut plane using this method.
Any ideas?
Hi @Simon_Vorhammer,
Maybe a silly workaround but if you take the Clipping Plane object and then apply a -1 scale on it with the gumball scale handle you will get the clipped drawing as RCP:
- Select clipping plane
- Set X scale to -1:
- Reap the rewards of maintaining the dynamic clipping but now it’s in RCP
@michaelvollrath Ah, yes, of course! That makes sense. Why didn’t I think of this? Thank you!
I spent about 3 hours working on an RCP camera function before one of the devs pointed out it’s simply an inverted transform so happy to pass that on since now. I never would have thought of that haha
@rajaa I wish we could just use section views on details instead of drawings. Have actual print settings in section styles. The ability to vector print a section with thicknesses from a detail on a layout would simplify the architectural drawing workflow massively. Is this something that could be considered in the future?
Hi @brian
thank you for this!
I was wondering if it is being planned (or if somebody asked already) to have more explicit Clipping plane properties:
Currently some properties can be set trough Clipping Plane Properties Tab
while some other can be set only trough _EditClippingDrawings
Why not embed all Clip Plane properties to his tab?
Thanks!
Hi @guido ,
I’m totally in with your vision.
Unfortunately, McNeel Team started implementing such idea too late, as per This post.
Agreed. As soon as the option to include the geometry beyond the section plane as proper 2D vectors was added to the mix (and have it dynamically linked to the source), I’m thinking “well, if it can still do that without the section plane actually cutting through anything, we’re good to go for all 2D stuff”. It is sooooo close to what’s needed in Rhino for 2D.
Hi @luca4 you’re making a good point, but not all clipping-planes have drawings extracted by default. I can see how it would be useful to edit the settings of the drawings from the property panel once a drawings is created. I am not clear how will the UI look in this case. Do you have some detailed thoughts?
Hi Rajaa,
actually I didn’t realized that “missing” properties are the one which control Clipping Plane Drawings.
I think UI could just work by adding Clipping Plane Drawings Properties below CP ones
This is how I would approach this (although I may be the least judicious in this forum):
- Expand section styles into a dedicated settings panel (similar to linetypes)
- Allow users to save and manage multiple section styles.
- Enable assigning section styles in clipping plane properties: by clipping plane or by layer (probably drawings should inherit settings, not have their own).
This feels like the most Rhino-consistent way of applying properties.
Additionally, I’ve noticed that having clipping plane options within display modes can further complicate things.
A significant enhancement would be to highlight in the Properties panel whenever a property is being overridden by a visual style — not just for clipping planes, but for any display mode override.
This would go a long way in making overrides more transparent and predictable.
That is a very neat fix and as you say, Rhino-esque in the application of the logic. A very elegant solution. It would create a user defined palette for controlling and applying the section styles and speed up deployment of changes to section styles no end.
As a complete aside, this same logic should be applied to the palette used for colours when button icon editing. A series of user-defined “pigeon holes” that control everything that has been assigned to use that colour/style.
In both cases, it would make it easy to create and save distinct “style sets” that would cater for the needs of both the user and their customers, if the latter is dictating some sort of corporate style.
Added the request here…
This is supported in the RhinoWIP
I want to make sure I understood you right. ClippingDrawings do inherit section style properties from source or by output layer. Can you please share an example where you cannot set the drawings to the intended properties?
Can you please share an example of what you mean?