Sorry for being an extra pain lately but I’ve been working on Rhino A LOT these days so I’m seeing more things still a bit broken, and they are affecting by productivity more. So unlucky you that you get to hear me complain more these days.
Now let’s talk Clipping Pains:
I need to have clipping planes that are not extra objects to manage in my scene. I need them as a way to view stuff and take screenshots. So here’s what’s broken IMO:
1. ONE click way to enable/disable all clipped geometry on my viewport.
Dale oroginally had created this plugin in V5: Clipping plane tool/script/plugin/nuggets out there? - #11 by dale
2. better way to know which viewport is using a clipping plane:
When you have more than one ‘Pesrpective’ viewport this approach is not useful
3. Cap geometry regardless of open closed polysurface. I think that cap if open, do not cap is close it’s a nice default. It’s also a good way to know (in case you didn’t) that your object is not a closed polysurface. The problem is that most times I’m looking for interference is actually on interference/collisions between my model and imported components from all kinds of places:
- imported engineering assemblies (and we all know how bad RHino Step importer can be to bring solid geometry here)
- McMaster Carr/DigiKey or other supplier models (not always closed solids)
- Grabcad (the 3D version of the Craiglists free section)
Example: here is hard to see if I have collisions with this imported component in green (it did not import as solid & I or my client have no need/interest/time to doctor that model to make it a solid):
In needs to look like this regardless of the object is solid or not:
4. Easy way to set section appearance, including making a hatch on sections.
I need to set appearances on sections without going on a wild chase of options or hunting for layers. I’m aware of the existence of the SetLayerHatchData command in the SectionPlane command (Prototype: SectionPlane (ClippingPlane Enhancements)) …but I don’t understand it and it seems way more complicated than just having a clipping plane property. in the only plane I want to go: the clipping planes properties panel:
I know you have a sinkhole there and your are very afraid to go near, but I think it’s OK, we can use that space!
5. Clipping Object, not just plane.
You had in V5 this useful plugin called DinamicDisplay, and had a command called _ddClippingobject
I don’t even use it in V5 either, because even though I own it it’s a total pain in the ass to figure out its licensing. I think you have to send a message in a bottle and wait until it arrives to Spain, and then maybe they email you back… The thing costs $25 I think? …well my billing rate costs more than that so I can’t afford to deal with its nonsense licensing. Also it’s useless unless everyone I work with also has it. This needs to be inside Rhino, and stop this madness.
6. A simple X, Y or Z sliding/dragable section.
Even Adobe PDF has this. And every shitty iPad 3D modeling app. And every El Cheapo 3D printing slicing software. Come on guys, that’s a basic functionality of section tools.